Search Hotels by Destination ID
View all Booking.com Hotel & Travel Data endpoints →Search with an existing dest_id and its matching dest_type, plus stay dates, guest counts, rooms, and currency. The documented New York pair is dest_id=20088325 with dest_type=city; it is not the prefixed query used by stays-search. Accommodation autocomplete is unavailable, so obtain a known destination pair independently. This destination-ID route was not live-validated. Inspect its response and property IDs before handing a selected hotel to detail operations.
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-dest API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/search-by-dest?key=<API_KEY>&dest_id=20088325&dest_type=city'
Query Result
Use Cases
- Reuse a confirmed city/type pair for repeated hotel-price comparison runs.
- Test a saved destination identity without relying on unavailable autocomplete.
- Create a destination-specific shortlist with consistent room and guest counts.
- Separate city identity records from property identity records in a travel catalog.
Frequently asked questions
Is dest_id the same input as stays-search query?
No. This route accepts the separate dest_id and dest_type fields. The documented New York pair is 20088325 and city, while stays-search uses a query such as city:20088325.
Can this route discover my destination ID?
No. It requires a known pair. The accommodation autocomplete routes are unavailable, and this search response has not been live-validated.