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

Activity facet context by city Request filters for the attraction destination actually selected by the traveler.
Visit-window filter alignment Keep start_date and end_date matched to the intended activity search.
Documented tagname values Inspect returned category, label, city, and price tokens before composing filters.
Destination-change facet refresh Recheck activity choices instead of reusing stale tokens from another city.

Live API Demo

GET /api/project/booking/attraction-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/attraction-get-filters?key=<API_KEY>&city_ufi=<city_ufi>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →