Discover Hotel Destination Filters

View all Booking.com Hotel & Travel Data endpoints →

Request filter metadata for a known dest_id/dest_type and the same dates, occupancy, rooms, and currency as the hotel search. Documentation identifies data.filters.options.genericId for category tokens and price sliderOptions.min/max for budget controls. These are documented handoffs, not live-validated response fields. Leave categories_filter blank initially, inspect the returned options, then reuse only identifiers supported by that destination and stay.

API Features

Destination-context facet discovery Obtain filter choices for one confirmed destination and stay.
Documented genericId handoff Inspect category identifiers before composing categories_filter for hotel search.
Currency-aware price-slider bounds Read documented price min/max in the selected currency instead of guessing a global range.
Unfiltered first metadata request Start without categories_filter so the initial choice set is not narrowed accidentally.

Live API Demo

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

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-get-filters?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

Where do category identifiers come from?

Documentation points to data.filters.options.genericId. Inspect the actual response and pass supported identifiers as comma-separated categories_filter values.

Can I hard-code one budget range for every city?

No. Request filter metadata with the same destination, stay, and currency, then inspect the documented price slider bounds. This route was not live-validated.

Related operations

Guides

View Subscription Plans →