Get Location Details API

Pass a location id from Get Suggestions and receive the full geographic boundary of that location — the set of coordinates that define its polygon or multi-polygon shape. This boundary is what you pass into Search Init to perform a city-level search.

GET{baseEndpoint}/api/location/{id}

Only call this for city-type results. If the Autosuggest type is hotel, airport, pointOfInterest, or trainStation, skip this API entirely — those types already provide the coordinates you need directly in the Get Suggestions response.

Where it fits in the flow

Step 1Get Suggestions
type = city

→

Step 2Get Location Details
pass the id

→

Step 3Search Init
pass the polygon

What the response gives you

boundaries

An array of lat/long coordinate pairs that trace the full outline of the location. This is the polygon (or multi-polygon) you pass into Search Init.

type

Confirms whether this is a polygon (one connected area) or multiPolygon (multiple separate areas, e.g. a city with a geographically distant airport zone).

Polygon vs multi-polygon

The type in the response tells you what to expect in the boundaries array.

Polygon — one continuous enclosed area. Most cities return this. Pass all the coordinates as a single polygon boundary in Search Init.

Multi-polygon — two or more separate enclosed areas. Common for large cities where different zones (city centre, airport area, new developments) are geographically fragmented. Pass all areas — the engine will search within each and return hotels from all of them.