Hotel mapping solutions
A persistent HM ID for every property; supplier codes and cross-IDs in a single record.
We merge hotel records from BookingAgora with the same hotels at your other suppliers under a single permanent HM ID. Hotel code, room name, board type and destination are standardized; a BookingAgora offer appears as one offer for the same hotel, not as a separate hotel card in your list.
BookingAgora is a B2B travel platform of Turkish origin that offers travel agencies domestic and international hotel inventory.
When an agency uses BookingAgora together with other bedbank suppliers, the same hotel arrives from each source with a different name and a different supplier code. Without mapping, the hotel appears two or three times in the list and prices cannot be compared side by side. Hotel mapping gathers these records under a single HM ID. We cover the basics of the topic in the hotel mapping guide.
| Supplier data | Standard output |
|---|---|
| Hotel code | HM ID |
| Room name | Room type, view, bed (room mapping) |
| Board description | RO, BB, HB, FB, AI, UAI |
| City and zone | Country → province → district → resort area |
In the example below, the hotel name and codes are fictional.
When inventory is collected from different sources, the same hotel can appear with two separate codes even in the supplier's own list. When two codes from the same supplier land on the same hotel, the record goes to the conflict queue and is checked separately.
"Dbl Room Sea View" and "Double Sea View Promo" can describe the same room. If campaign and price wording is not separated from the room type, the same room is listed as two different rooms.
In wholesaler data, the destination sometimes arrives as a city name only; a hotel in Kemer may be marked as "Antalya". We place it in the correct resort area using coordinates and address.
{
"supplier": "bookingagora",
"supplier_code": "BA-204118",
"supplier_name": "KEMER PINE GARDEN HTL",
"supplier_city": "Antalya",
"match": {
"hm_id": "HM-1061590",
"name": "Kemer Pine Garden",
"destination_id": "TR-07-KEMER-GOYNUK",
"confidence": 0.981,
"decision": "auto_match"
}
} Code samples are illustrative; field names may change in the v1 release.
A persistent HM ID for every property; supplier codes and cross-IDs in a single record.
Breaks room names into type, class, view, bed and capacity; groups the same room under one room ID.
Links supplier destination codes to a country → province → district → resort area hierarchy and to IATA codes.
For single lookups, use the REST API: a GET /v1/suppliers/bookingagora/codes/{code} call returns the corresponding HM ID and confidence score. For bulk use, you can get a daily full and delta dump (CSV, JSON, Parquet).
No. The new code is rescored and linked to the same hotel; the HM ID stays fixed. Offering code change history as a separate product is planned.
Records with a score of 0.97 or higher match automatically. Records between 0.80 and 0.97 go to an expert for review, and anything below 0.80 creates a new HM ID.
Request a quote
Send your request in three steps; we will email the quote to your work address. The request is non-binding.