Search Hotels by Location Text
View all Booking.com Hotel & Travel Data endpoints →Search with a user-confirmed location string plus explicit check-in/check-out dates, guests, rooms, and currency. Optional price bounds, category identifiers, bed count, page, and sort refine the documented request. This text-oriented route was not live-validated and is not a proven replacement for unavailable accommodation autocomplete. Verify returned property geography and actual response fields before displaying matches for ambiguous location names.
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/search-by-location API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/search-by-location?key=<API_KEY>&location=<location>'
Query Result
Use Cases
- Evaluate a text-first hotel finder for a clearly named city and country.
- Check whether a conference neighborhood string resolves to the intended accommodation area.
- Compare results for expanded and abbreviated place labels in a controlled integration test.
- Apply traveler-selected budget bounds to a confirmed location search.
Frequently asked questions
Is this a verified fallback for broken accommodation autocomplete?
No. The route is documented but was not live-validated. Do not assume that it bypasses destination-discovery failures; verify actual results and geography first.
Which location string should I send?
Use a user-confirmed location with enough geographic context, such as the documented Berlin, Berlin Federal State, Germany example. Similar names can refer to different places.