Skip to main content
After a mapping job reaches COMPLETED status, you can search the individual hotel match results. Filter by hotel name, location, your partner IDs, the matched reference hotel, or specific supplier IDs. Results are paginated and include match confidence scores, match methods, and supplier external IDs.

Search endpoint

All filters in the request body are optional. Omit any filter you don’t need; null values are ignored.

Request fields

Only the fields listed above are accepted. Any unknown field in the request body is rejected with 400 Bad Request, so watch for typos in filter names.
1

Run a search

Send a POST request with your desired filters. This example finds all hotels named “Hilton” in Paris that have Expedia or Booking.com external IDs:
2

Read the response

The response wraps results in a paginated envelope:
3

Paginate through results

Use page and size to walk through large result sets. Pages are 0-indexed.
Continue incrementing page until page >= totalPages - 1.

Understanding match fields

matchMethod

The matchMethod field tells you how a hotel was matched: Hotels with matchMethod: null have a null matchedReferenceHotelId and matchedReferenceHotelName.

matchConfidence

A decimal score from 0 to 100 representing how confident the fuzzy pipeline is in the match. A score of 100 means an exact match. ID_TO_ID matches do not produce a confidence score.

supplierExternalIds

A map of supplier UUID to that supplier’s external hotel ID. Only suppliers with a known external ID for the matched reference hotel are included. If you filtered by supplierExternalIds in the request, the response only contains results whose matched reference hotel has the requested external IDs.
Use these IDs to cross-reference the matched hotel in your own supplier systems.

Filter reference

hotelName is a partial, case-insensitive search. It matches any hotel whose name contains the string.
This returns results like “The Grand Budapest”, “Grand Hyatt”, and “Le Grand Hotel”.

Error responses