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

Text-to-coordinate candidate lookup Evaluate geographic candidates for a user-confirmed location string.
Documented centroid handoff Inspect centroid.lat and centroid.lon before mapping them to hotel coordinates.
Optional geocoder limit preference Use limit as a documented input without assuming it is an enforced result cap.
Ambiguous place confirmation Keep similarly named geographic candidates separate until a traveler confirms one.

Live API Demo

GET /api/project/booking/get-coordinates-from-location

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/booking/get-coordinates-from-location?key=<API_KEY>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →