Destination mapping: one hierarchy from country to resort

Every hotel in the right place.

Suppliers describe the same area with different names and at different levels. Destination Mapping standardises the country → city → region → resort hierarchy, so your filters and landing pages show the right hotels.

match accuracy
99.9%
hotels worldwide
3.5 million
to map a new supplier
1 day
ready-made integrations
14

How we do it

How we map destinations

  1. 1

    We take supplier destinations

    Suppliers’ region and city lists come in with their codes; the same place can be a city for one supplier and a region for another.

  2. 2

    We place them in one hierarchy

    Each record links to the right node of the country → city → region → resort tree: Antalya → Serik → Belek.

  3. 3

    We verify against locations

    Records are checked against hotel locations and IATA codes; our data team verifies uncertain matches.

  4. 4

    We keep it current

    New supplier codes attach to the same hierarchy, and changes arrive by API, bulk file and webhook.

Why traveldata

What sets our destination mapping apart

  • Resort areas defined separately

    Resort areas such as Belek, Kemer, Side and Bodrum are destinations of their own, so holiday filters work.

  • Worldwide coverage

    Every country and city that holds our 3.5 million mapped hotels sits in the same hierarchy.

  • A bridge between codes

    Supplier destination codes and IATA codes live on the same record, so you send each supplier its own code in search requests.

  • Aligned with hotel mapping

    Every TravelData ID links to the right destination; hotels, rooms, boards and destinations are mapped with the same logic.

Features

Destination Mapping features

  • 01

    Four-level hierarchy

    Country, city, region and resort: Antalya → Serik → Belek.

  • 02

    Supplier codes

    Supplier destination codes and IATA airport/city codes on the same record.

  • 03

    Resort areas

    Resort areas such as Belek, Kemer, Side and Bodrum are defined as destinations of their own.

  • 04

    API and bulk files

    Query the hierarchy by API or take all of it as a file.

Sample request and response

Request

GET /v1/destinations/belek

Response

{
  "id": "belek",
  "name": "Belek",
  "level": "resort",
  "path": ["TR", "Antalya", "Serik", "Belek"],
  "iata": ["AYT"],
  "supplier_codes": {
    "supplier_a": "BLK",
    "supplier_b": "7731"
  }
}

Hotel and supplier names are examples.

Use cases

Where destination mapping is used

  • Destination search and filters

    A search for “hotels in Belek” returns the right hotels, whatever name each supplier uses for the area.

  • Destination landing pages

    The region pages you build for search engines are fed by one consistent hierarchy.

  • Sending searches to suppliers

    The area a user picks is translated into each supplier’s own destination code.

FAQ

Destination mapping FAQ

What is destination mapping?

Destination mapping merges the countries, cities and regions that suppliers describe with different names and at different levels into a single hierarchy.

How many levels does the hierarchy have?

Four: country, city, region and resort. For example: Türkiye → Antalya → Serik → Belek.

Are IATA codes included?

Yes. IATA airport and city codes are kept on the same record as supplier destination codes.

See it on your own inventory

Send us your supplier list; we map it within one day and review the result and data quality report with you.

Get a quote