Resolve a Location to Coordinates
View all Booking.com Hotel & Travel Data endpoints →Inspect the documented location-coordinate lookup with location and optional limit. Accommodation search documentation references centroid.lat and centroid.lon from this lookup as candidate search coordinates. The live geocoder response, ambiguity handling, and limit enforcement were not validated. Confirm the place and geography before using a selected coordinate in radius-based hotel search.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/booking/get-coordinates-from-location API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/get-coordinates-from-location?key=<API_KEY>'
Query Result
Use Cases
- Evaluate a venue centroid before a nearby-hotel radius search.
- Compare coordinate candidates for an ambiguous city or conference location.
- Inspect whether actual geocoder output supports a traveler confirmation step.
- Validate place geography before reusing coordinates in a hotel research run.
Frequently asked questions
Can the first coordinate candidate be selected automatically?
Confirm the place and geography first, especially for ambiguous names. No live geocoder response or ranking behavior was validated.
Which coordinate fields are documented for hotel search?
Hotel-search documentation references centroid.lat and centroid.lon from this lookup. Inspect actual response structure before extracting them.