FAQ

This FAQ consolidates the questions Vervotech customers most frequently ask about Room Mapping, grouped by audience.

ℹ️ Note: If your question isn't answered here reach out to customersuccess@vervotech.com.

Q: What problem does Room Mapping solve at a product level?

A: Travel platforms aggregate inventory from many suppliers, and each supplier describes the same physical room differently. Without a unifying layer, search results show duplicates, comparing prices is unreliable, and travelers get confused. Room Mapping groups equivalent rooms across suppliers into a single standardized record so your platform can show one room per type with the best available rate — improving conversion and trust.

Q: What does a "successful" Room Mapping outcome look like?

A: Two signals indicate Room Mapping is working as intended:

Reduced duplicates — fewer near-identical rows in search and shopping results for the same hotel.

Higher confidence on matched rates — most mapped rates carry a MatchScore more than 90, meaning the system is highly confident the supplier's room belongs to a known standardized room group.

Q: Will any rooms be silently dropped from the response?

A: No. Every room in the input is processed and represented in the response. Rooms that match a known standardized group are mapped to that group; rooms with insufficient signal to map confidently are returned separately rather than discarded. This means your downstream systems can trust that input volume equals output volume.

Q: How do we control which suppliers' content is used for mapped rooms?

A: Two configuration levers govern content assembly:

ProviderContentType — Merged combines fields from multiple providers in the order you specify; PreferredProvider uses the first provider in your list that has matching content for the room.

ProviderContentPreference — an ordered list of provider names. The system walks this list to find content (such as images and descriptions).

This lets you balance richness (Merged) against editorial control or commercial preference (PreferredProvider).

Q: What inputs improve mapping quality the most?

A: Beyond the mandatory RoomName, RoomCode, Provider, and ProviderHotelId, the highest-leverage optional fields are:

Bed — bedding configuration (e.g., "1 King", "2 Doubles")

View — view designation (e.g., "City View", "Ocean View")

Description — supplier room description

Attributes — room attributes

Q: Which endpoint should I use — sync or async?

A: Use the synchronous Map Rooms endpoint for real-time shopping flows where latency matters and your batch fits within the per-request payload limit. Use the asynchronous Map Large Rooms Async endpoint for large batches: submit the job, then poll Get Async Room Mapping API Response for the result. For bulk historical mapping or scheduled backfills, use the file-based offline workflow.

Q: What fields are mandatory in a Map Rooms request?

A: Per room rate, the following are required:

Field	Purpose
`Index`	Unique index for this room rate within the request
`Provider`	Supplier name (must match Vervotech's master provider names)
`ProviderHotelId`	Supplier's hotel identifier
`RoomName`	Supplier's room name string
`RoomCode`	Supplier's room code (in case room content is required)

roomRates (the array itself) and a valid accountId / token are also required at the request level. All other room attributes (Bed, View, Description, Refundability, BoardBasis) are optional.

Q: What is the `MatchScore` (confidence score) and how should I use it?

A: The MatchScore is a numeric indicator of how strongly an input rate matches its assigned standardized room group. It is computed from attributes such as room category, bed type, view, and other features. Higher values (closer to 100) indicate stronger matches. Typical usage:

High scores — display the mapped grouping confidently in production.

Low scores — optionally route through a quality-review queue or fall back to a per-supplier display until confidence improves.

The exact threshold is up to your product, but most teams pick a value during validation and tune it from there.

Q: What's the difference between `Merged` and `PreferredProvider` content types?

Mode	Behavior
`Merged`	Combines content (e.g., images, descriptions) from multiple providers in the order specified in `ProviderContentPreference`, filling in fields where any provider has data — producing a richer, more complete result.
`PreferredProvider`	Uses content from the first provider in `ProviderContentPreference` that has matching room codes for that group. If that provider lacks content, the system falls through to the next provider in the list — but it does not merge across providers.

Choose Merged for maximum richness. Choose PreferredProvider when you want a single, editorially consistent voice per room.

Q: How do I get room images in the response?

A: Two request fields drive image inclusion:

ProviderContentType — set to Merged or PreferredProvider (see above).

ProviderContentPreference — ordered list of provider names whose content (including images) should be considered.

Images are returned only when a matching room code is found in one of the listed providers' content. If none of the listed providers has matching content for that room, no images will be returned for it.

Q: What's the recommended way to handle a `1011` (Unauthorized providers) error?

A: First, call Get Provider Names to confirm exactly which providers your account is authorized to map. Compare the names you're sending in the Provider field — they are case-sensitive and must match Vervotech's master list exactly. If a provider you expect isn't in the list, contact Vervotech to enable it for your account before retrying.

Q: Which languages are supported in the response?

A: Vervotech supports the following BCP-47 codes today: en-US, es-ES, tr-TR, fr-FR, it-IT, ar-SA. More may be added in future. Supply the desired language code in the appropriate request field (refer to the API reference for the exact parameter name in the endpoint you are calling).

Q: What problem does Room Mapping solve at a product level?#

Q: What does a "successful" Room Mapping outcome look like?#

Q: Will any rooms be silently dropped from the response?#

Q: How do we control which suppliers' content is used for mapped rooms?#

Q: What inputs improve mapping quality the most?#

Q: Which endpoint should I use — sync or async?#

Q: What fields are mandatory in a Map Rooms request?#

Q: What is the MatchScore (confidence score) and how should I use it?#

Q: What's the difference between Merged and PreferredProvider content types?#

Q: How do I get room images in the response?#

Q: What's the recommended way to handle a 1011 (Unauthorized providers) error?#

Q: Which languages are supported in the response?#