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
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-get-filters 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'
Query Result
Use Cases
- Populate a hotel facility-filter panel for a confirmed destination.
- Discover property-type identifiers before offering apartment-only searches.
- Initialize a travel budget slider using returned destination-specific limits.
- Refresh hotel facets after a date or occupancy change invalidates earlier choices.
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.