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

Destination ID and type pair Preserve both fields because the number alone does not describe the destination kind.
Unprefixed destination input Send dest_id separately from dest_type rather than using city:20088325 as a single value.
Destination-level budget controls Combine the documented destination identity with date-specific price limits.
Hotel selection after destination search Verify selected property IDs before switching to numeric hotel-detail requests.

Live API Demo

GET /api/project/booking/search-by-dest

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/search-by-dest?key=<API_KEY>&dest_id=20088325&dest_type=city'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →