Mapping behavior

Request shapes

Use POST /v1/room-mappings with one hotel's complete inventory. Send the Plexe hotelId when known, or the hotel name with city and ISO two-letter country code. Supplier room IDs are not interchangeable with catalogue IDs.

Keep roomName exactly as received. Send every offer, including repeated names, with supplier details where available. Both shapes accept include and contentPreference. Do not mix policy fields between shapes: a body containing roomRates uses the original shape and ignores unknown fields. The alternative shape rejects unknown fields and folds equivalent name spellings before the model call, so changing shapes can change results.

Mapping policies

In the alternative shape, placementPolicy is lenient, guarded (default) or strict; doubtfulHotelPolicy is place (default) or hold. It always uses standard mode.

Account policy can enable guards on standard calls or preserve a previously evaluated policy. Check policyVersion; additional supplier fields alone do not enable checks that the account's policy disables. A policy version describes rules, not a frozen model or catalogue snapshot.

There is no numeric mapping-threshold request parameter. Similarity is not a calibrated correctness probability. Strict mode does not mean every offer receives an LLM check: confident encoder matches can still use the fast path.

Evidence and reanchoring

The model proposes categories from room names. Enabled guards check recognized beds, views, wings and affirmative room-specific descriptions for conflicts, including offers with identical names. Missing values remain unknown. occupancy is the requested party size; it can rule out a room only against known maximum capacity.

Reviewed property records can recover a category or reanchor an offer to a different category. This uses exact names or explicitly reviewed variants within the resolved property. It preserves qualifiers rather than guessing equivalence from generic room names. Records supplement the catalogue and are not a complete supplier-code crosswalk.

A recovered placement remains tier: "inferred". placement.evidence carries category sources, review date, revision and match method. If the target changes, placement.similarity is null because the previous score measured a different target. Category changes or offer separation can change room IDs; keep rate IDs to reconcile updates.

Unsupported aliases can remain unresolved with reason room_ambiguous. Keep those offers visible. Repeating the same request does not supply missing evidence. Whole-hotel holds, active feedback and applicable offer-conflict checks still take precedence.

reason: "evidence_match" requires an acknowledged evidence-based picker result. Failed or invalid picker decisions can remain unresolved with reason: "undecided". An inferred match or a high similarity score is not a booking confirmation.

Content and prices

rooms[].name is the proposed category heading, not confirmation of every offer's benefits. For example, “Golf View” or “Lounge Access” in an inferred heading must not become a guaranteed badge on every rate. Keep the original roomName visible and use that offer's supplier details for booking attributes.

rooms[].supplierContent collects images, descriptions, amenities, beds and views from the supplied offers. Source rateIds identify where details came from. contentPreference controls supplier ordering for content; it does not establish room identity. The optional include: ["attributes"] returns extracted attributes where a reader is configured; it does not change grouping.

Send smokingAllowed: true or false only when explicitly known. Omit it otherwise. Room summaries return a smoking value only when every offer supplies the same boolean. Display labels omit smoking qualifiers without changing original supplier names or implying non-smoking.

nightlyPrice and currency order offers within a room cheapest first when priced offers share a currency. Prices are not converted. Check dates, occupancy, meals, taxes and cancellation terms before treating prices as comparable, and refresh prices and availability at shopping time. Aggregated occupancy is not maximum room capacity.

Correcting a mapping

Use POST /v1/feedback with the returned hotel ID and original supplier room names. Feedback is scoped to your API key.

• not_in_room: supply the room ID that those names must leave.
• different_rooms: prevent the reported names from sharing a group.
• same_room: records your report; it does not currently merge rooms.

Applied separations return the affected offers on their own. List reports with GET /v1/feedback?hotelId=…, or withdraw one with DELETE /v1/feedback/{feedbackId}. Limits are 2,000 reports per key, including withdrawn reports, and 200 active reports per hotel. Repeated active reports return the existing report.

Compatibility

Build new displays on rooms[], per-rate placement, hotel.resolution and notices[]. Legacy groups[], matchedRoom, catalogued, decidedBy, encoderScore, warnings, timingsMs and usage remain available. Any removal date will be announced at least 30 days ahead.

Display-only label cleanup preserves IDs. Corrections to category identity can change them. A stored response is the result at submission time; submit a fresh complete inventory to evaluate current rules and evidence.