Room mapping solutions
Breaks room names into type, class, view, bed and capacity; groups the same room under one room ID.
Hotel mapping merges the different names, codes and addresses that suppliers send for the same hotel into a single persistent identifier (HM ID). Supplier codes, Google Place ID and coordinates are linked to this ID, and the hotel IDs from your existing mapping provider or your own system are stored as cross-references. As a result, every hotel appears only once in your listings.
{
"hm_id": "HM-1048213",
"name": "Sunset Bay Resort & Spa",
"destination_id": "TR-07-SERIK-BELEK",
"destination": ["TR", "Antalya", "Serik", "Belek"],
"geo": { "lat": 36.8541, "lng": 31.0552 },
"supplier_codes": {
"A": "HTL-88213",
"B": "40917",
"C": "TR-ANT-551"
},
"external_ids": { "client": "OTL-2231" },
"status": "active"
} Records for the same hotel from different suppliers are grouped on a single card, so the best offer shows up in one place.
An HM ID is never reassigned to another hotel. When hotels merge, the old ID redirects to the new one.
We store the hotel IDs from your existing mapping provider or your own system as cross-references, so the mapping work you have done so far is not lost.
A new supplier file goes through normalization and scoring and is linked to HM IDs within a short time.
Raw records from three suppliers
supplier,code,name,city,lat,lng
A,HTL-88213,Sunset Bay Resort & Spa,Belek,36.8541,31.0552
B,40917,SUNSET BAY RESORT SPA,Serik,36.8543,31.0549
C,TR-ANT-551,Sunset Bay Rsrt. & Spa - Adults,Antalya,36.8539,31.0556 A standard record under a single HM ID
{
"hm_id": "HM-1048213",
"name": "Sunset Bay Resort & Spa",
"destination_id": "TR-07-SERIK-BELEK",
"destination": ["TR", "Antalya", "Serik", "Belek"],
"geo": { "lat": 36.8541, "lng": 31.0552 },
"supplier_codes": {
"A": "HTL-88213",
"B": "40917",
"C": "TR-ANT-551"
},
"external_ids": { "client": "OTL-2231" },
"status": "active"
} Sample data; the hotel name and codes do not belong to a real property.
We receive supplier static data via API, CSV or FTP. Every record is stored in its raw form and changes are versioned.
Suffixes such as "Hotel" and "Resort & Spa" are split off the hotel name; Russian and Arabic names are transliterated to Latin script; addresses, phone numbers and web addresses are converted to a standard format.
Each record is compared only with nearby hotels. Name similarity, multilingual embeddings, distance, and phone and website matches combine into a probability score between 0 and 1.
A score of 0.97 or higher is matched automatically; records between 0.80 and 0.97 go to a specialist on a map-based review screen; below 0.80 opens a new HM ID.
Results reach you via REST API and daily full and delta dumps (CSV, JSON, Parquet); webhooks are planned.
An agency typically works with several suppliers, and each supplier sends the same hotel with its own name, its own code and its own coordinates. Without mapping, the same hotel appears more than once in the list, price comparison breaks down and customers cannot tell which card is correct.
hotelmapping.org works with 3.5 million hotels worldwide and merges these records into a single persistent identifier, the HM ID. You work only with the HM ID; we keep track of which supplier uses which code.
| Field | Description |
|---|---|
| Supplier codes | Each supplier’s hotel code, linked to the HM ID |
| External hotel IDs | IDs from your existing mapping provider or your own system; stored as cross-references where available |
| Google Place ID | Additional reference for location and identity |
| Coordinates | Latitude and longitude selected from supplier records (coordinate validation planned) |
| Destination | Country → province → district → resort area hierarchy |
Mapping quality is measured with every release against a manually labeled test set. We publish only figures verified by this measurement on the site; current values are on the coverage page.
Request
curl https://api.hotelmapping.org/v1/suppliers/B/codes/40917 \
-H "X-API-Key: $HM_API_KEY" Response
{
"supplier": "B",
"code": "40917",
"hm_id": "HM-1048213",
"confidence": 0.998,
"matched_at": "2026-11-02T08:14:00Z"
} Code samples are illustrative; field names may change in the v1 release.
A supplier code is valid only in that supplier's system and differs from supplier to supplier. An HM ID is the persistent identifier we assign that brings together all supplier codes of the same hotel.
Uncertain scores are not matched automatically; they go to human review. If you still report an error, the record is corrected and that decision is added to the model as training data.
An HM ID is never given to another hotel. The status of a closed hotel becomes "closed". When hotels merge, the old ID's status becomes "merged" and the merged_into field points to the new ID.
Yes. We store the hotel IDs from your existing mapping provider or your own system as cross-references; they are returned alongside the HM ID in the external_ids field of the API response. This lets you move to HM ID without abandoning your existing mapping.
Request a quote
Send your request in three steps; we will email the quote to your work address. The request is non-binding.