COMMON ASSETS

Api Services

Section	Description
Suggestions	Provide autocomplete suggestions based on a search hint and locale.
Geography	Provide country/continent/region catalogs and related geo structures for content and rules.

HOTEL CONTENT: This section contains the descriptive content and catalog information associated with hotels, such as amenities, meal plans, and fee types

Section	Description
Hotel-Inventory	This service returns the list of hotels available for each partner.
Hotel-Information	Returns static information about hotels including photos, rooms, amenities, etc.
Meal-Plans	This section contains the available meal plan options that may be associated with a hotel or room.
Fee-Types	This section defines the different fee types that may apply to a reservation, such as mandatory or optional charges.
Amenities	This section lists the available amenities that describe the services and facilities offered by the hotel.
Reviews Summary	Returns aggregated review summaries for one or more hotels, including overall ratings, qualification breakdowns, traveler profile distribution, and an AI-generated review when available.

Hotel Mapping

How to Build the Mapping

The most efficient approach is to start from the hotel inventory and complement it with geographic data.

Download the hotel inventory: Call the inventory endpoint. It returns all available hotels, each with its city_id. Store this response in a way that suits your systems (e.g. could be a local snapshot)
1. hotel_inventory
2. Store the snapshot and refresh it periodically. The inventory does not change in real time, so there is no need to call this endpoint on every search.
Map cities to countries: Call the countries endpoint to retrieve the full list. Then, for each country, call the cities endpoint using the country_id. The response is paginated, which allows handling countries with many cities efficiently.
1. countries
2. cities/{country_id}
Cross-reference the data: Use the location.city.id from the inventory snapshot to match against the city id retrieved from the geography endpoints. This gives you the exact list of hotels that belong to each city and the country they are in.

Example

Call hotel_inventory and store the response as a local snapshot. Each hotel includes a location.city.id

[ { "id": "H001", "hotel_name": "Hotel A", "location": { "city": { "id": "0001" }, "address": "Av. Corrientes 1234" } }, { "id": "H002", "hotel_name": "Hotel B", "location": { "city": { "id": "0001" }, "address": "Av. Santa Fe 567" } }, { "id": "H003", "hotel_name": "Hotel C", "location": { "city": { "id": "0099" }, // different city "address": "Calle Falsa 123" } }, { "id": "H004", "hotel_name": "Hotel D", "location": { "city": { "id": "0001" }, "address": "Av. de Mayo 890" } } ]

Call countries to get the full country list, then call cities/{country_id} for each country. The response includes the city id and country_id, which are the keys used for the cross-reference.

{ "items": [ { "id": "0001", "country_id": "AR001", "descriptions": { "en": "Buenos Aires", "es": "Buenos Aires" }, "administrative_division_id": "00001" }, { "id": "0002", "country_id": "AR001", "descriptions": { "en": "Cordoba", "es": "Córdoba" }, "administrative_division_id": "00002" } ] }

Cross-reference both datasets using location.city.id (inventory) against id (cities). Hotels where both values match belong to that city.

Hotels-inventory  ──→  cross-reference  ──→  Cities (/v3/cities)
(location.city.id)      (city.id = id)        (id, country_id)

Geography Structure

Geography

The Geography service provides access to the geographical hierarchy used across the platform.

Continent
└── Country
    └── Administrative Division
        └── City
            └── Zone

Where:

Continent represents the highest geographical level.
Country belongs to a continent.
Administrative Division represents subdivisions such as states, provinces, or departments.
City belongs to an administrative division.
Zone represents a neighborhood, district, area of interest, or other sub-city location.

Regions: Are managed separately from the geographical hierarchy and may represent:

A predefined group of cities.
A custom geographical area that spans multiple cities, administrative divisions, countries, or other geographical entities.