Concepts
Locations & geocoding
The four ways to tell the Direct Travel API where to search — address, coordinates, bounding box, or hotel IDs.
Every search needs a location, supplied as one of four inputs. Provide at least one, or the request fails with LOCATION_REQUIRED.
| Input | Parameters | When to use | Notes |
|---|---|---|---|
| Address | address | A city, region, or place name you have as text | Geocoded server-side; less precise than coordinates |
| Coordinates | lat + lng (+ radius) | You already have a point and want the most precise, fastest search | Skips geocoding |
| Bounding box | nelat, nelng, swlat, swlng | Map UIs searching the visible viewport | All four corners are required together |
| Hotel IDs | hotelids | Looking up specific known stays | Can be Stay22 hotel IDs or Hotel IDs from the providers |
Points of interest
For a landmark or venue (e.g. "Eiffel Tower", "Bell Centre"), geocode the point of interest to coordinates first, then search with lat/lng + radius. This is faster and more precise than passing the name as address.
Priority
When both address and lat/lng are present, coordinates win; the address is used only as a fallback and for display context.
What to read next
- Response & supplier model — the shape of a result
- Pricing & quotes — add dates to get live prices
- Search Accommodation — every location parameter, with a live playground