Discover Attraction Search Filters
View all Booking.com Hotel & Travel Data endpoints →Inspect documented attraction facets using city_ufi with the same optional start/end dates, currency, language, and selected filter context as the activity search. Documentation references typeFilters, ufiFilters, labelFilters, and priceFilters tagname values in filterOptions. The live response and facet coverage were not validated. Refresh choices when the destination or visit window changes rather than assuming tokens are universal.
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/attraction-get-filters API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/attraction-get-filters?key=<API_KEY>&city_ufi=<city_ufi>'
Query Result
Use Cases
- Initialize category and price controls for a destination activity search.
- Check whether a cancellation-related label exists before offering it in a tour filter.
- Refresh excursion facets after a traveler changes the visit window.
- Validate saved attraction-filter values against the current destination context.
Frequently asked questions
Where are attraction filter values documented?
The documentation points to tagname values within filterOptions typeFilters, ufiFilters, labelFilters, and priceFilters. Validate the actual response before use.
Can filters from one city be reused in another?
Do not assume that. Refresh the metadata for the selected city and visit window; live cross-city compatibility was not validated.