Hotel mapping solutions
A persistent HM ID for every property; supplier codes and cross-IDs in a single record.
Destination mapping links the locations that suppliers send at different levels and with different codes into a single hierarchy: country → province → district → resort area (Turkey → Antalya → Serik → Belek). Each node has a persistent ID (e.g. TR-07-SERIK-BELEK), linked supplier destination codes and the IATA codes of the nearest airports.
{
"hm_id": "HM-1048213",
"destination_id": "TR-07-SERIK-BELEK",
"path": [
{ "level": "country", "id": "TR", "name": "Türkiye" },
{ "level": "province", "id": "TR-07", "name": "Antalya" },
{ "level": "district", "id": "TR-07-SERIK", "name": "Serik" },
{ "level": "resort", "id": "TR-07-SERIK-BELEK", "name": "Belek" }
],
"airports": ["AYT"],
"supplier_destinations": {
"A": { "code": "AYT-BLK", "level": "resort" },
"B": { "code": "1452", "level": "district" },
"C": { "code": "ANT", "level": "province" }
}
} Even if one supplier sends a hotel under Belek, another under Serik and a third only under Antalya, the hotel appears in the correct resort area.
The hierarchy combines a country's province and district administrative structure with the resort areas used in tourism. For example, relationships such as Kadriye being in the Belek area and Side being in the Manavgat district are recorded.
Each supplier's destination code is linked to a node in the hierarchy, together with information on which level it corresponds to.
Each resort area is associated with the IATA codes of the nearest airports; flight + hotel package searches can use the same data.
Destination information from three suppliers for the same hotel
supplier,hotel_code,dest_code,dest_name,country,airport
A,HTL-88213,AYT-BLK,Belek,TR,AYT
B,40917,1452,Serik,Turkey,
C,TR-ANT-551,ANT,Antalya Region,TR,AYT Location in a single hierarchy
{
"hm_id": "HM-1048213",
"destination_id": "TR-07-SERIK-BELEK",
"path": [
{ "level": "country", "id": "TR", "name": "Türkiye" },
{ "level": "province", "id": "TR-07", "name": "Antalya" },
{ "level": "district", "id": "TR-07-SERIK", "name": "Serik" },
{ "level": "resort", "id": "TR-07-SERIK-BELEK", "name": "Belek" }
],
"airports": ["AYT"],
"supplier_destinations": {
"A": { "code": "AYT-BLK", "level": "resort" },
"B": { "code": "1452", "level": "district" },
"C": { "code": "ANT", "level": "province" }
}
} Sample data; the hotel and supplier codes are fictional. The area and airport names are real.
Each supplier's destination list and the location fields in hotel records are collected; the raw form is stored.
We determine which level each supplier code corresponds to: country, province, district or resort area. "Antalya Region" is at province level, "Belek" at resort level.
The code is linked to a node in the hierarchy using name similarity, multilingual spellings and parent-level information. Uncertain links go to specialist review.
Even if the supplier sends only a province or district, the lowest level, the resort area, is determined using the hotel's coordinates selected from supplier records (coordinate validation planned).
The hierarchy and code mappings are delivered via API and daily dump. Hotel records return the destination ID and the full path together.
Suppliers send locations at different levels. One lists a hotel in Belek under “Belek”, another under “Serik”, another only under “Antalya”. Some use an airport code directly as the destination. Without mapping, a search for “Belek” misses some of the hotels, area filters work incompletely and the same hotel appears in different areas.
Destination mapping links all these codes into a single hierarchy and gives each hotel a single destination ID. For the general framework, see the hotel mapping guide.
| Level | Example | ID | Note |
|---|---|---|---|
| Country | Turkey | TR | ISO 3166-1 country code |
| Province | Antalya | TR-07 | ISO 3166-2 province code (license plate number) |
| District | Serik | TR-07-SERIK | Administrative district |
| Resort area | Belek | TR-07-SERIK-BELEK | Region name used in tourism |
| Case | Example | How it is resolved |
|---|---|---|
| Resort name differs from district name | Side is in the Manavgat district | The resort area is linked under the correct district |
| Sub-locality within an area | Kadriye is in the Belek area | The supplier’s “Kadriye” code is linked to the Belek node |
| District and resort share the same name | Kemer; includes Beldibi, Göynük, Tekirova | Kemer is kept as both a district and an area, and sub-areas are separated |
| Multiple airports for one area | Alanya: AYT and GZP | The area is associated with both IATA codes |
| Code only at province level | “Antalya Region” | The lower level is determined from the hotel’s coordinates |
The destination ID is part of the hotel record; that is why it works together with hotel mapping. To find an HM ID from a name and coordinates, the Find Match API uses the same hierarchy. The countries where the hierarchy is complete down to district and resort level are published on the coverage page. For terminology, see the HM ID, supplier code and geocoding glossary pages.
Request
curl https://api.hotelmapping.org/v1/destinations/TR-07-SERIK-BELEK \
-H "X-API-Key: $HM_API_KEY" Response
{
"id": "TR-07-SERIK-BELEK",
"name": "Belek",
"level": "resort",
"parent": "TR-07-SERIK",
"path": ["TR", "TR-07", "TR-07-SERIK", "TR-07-SERIK-BELEK"],
"names": { "tr": "Belek", "en": "Belek", "ru": "Белек" },
"airports": ["AYT"],
"supplier_codes": [
{ "supplier": "A", "code": "AYT-BLK", "level": "resort" },
{ "supplier": "D", "code": "BELEK-01", "level": "resort" }
]
} Code samples are illustrative; field names may change in the v1 release.
A district is an administrative unit; a resort area is a region name used in tourism. Belek is a resort area in the Serik district; Side is in the Manavgat district. Guests search for "Belek" or "Side", while suppliers often send a district or province.
The hotel is first linked to an HM ID through hotel mapping. Then the district and resort area it belongs to are determined using the coordinates selected from supplier records; coordinate validation is planned. The supplier's province code is also stored separately in the record.
Flight + hotel package searches start with the arrival airport. More than one airport can serve a resort area; for example, both AYT and GZP can be used for Alanya. This link lets a search reach the hotels in that area from the airport.
District and resort area level is planned to be completed first for Turkey (Antalya, Muğla, Istanbul), the UAE and Egypt. Which countries have this detail completed is kept up to date on the coverage page.
Request a quote
Send your request in three steps; we will email the quote to your work address. The request is non-binding.