Booking Search Attractions for a Visit Window API

Search documented attraction products using a known city_ufi with optional start_date/end_date, currency, language, page, page_size, and returned category, label, city, or price-filter tokens. Documentation references data.products[].slug/id for detail and availability handoffs and filterOptions groups for refinements. These fields were not live-observed: attraction search and downstream availability were not validated. Check actual products, dates, and conditions before presenting excursion choices.

API Features

City-scoped activity candidates Search a confirmed attraction city_ufi for a chosen visit window.

Documented product slug and ID handoffs Inspect product slug for detail and product ID for availability requests.

Returned activity filter tokens Use actual categories, labels, cities, and price identifiers rather than invented values.

Date-window attraction comparisons Keep start and end dates aligned when comparing candidate excursions.

Live API Demo

GET /api/project/booking/attraction-search

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/booking/attraction-search?key=<API_KEY>&city_ufi=<city_ufi>'

curl -X GET 'https://api.opendata-api.com/api/project/booking/attraction-search?key=<API_KEY>&city_ufi=<city_ufi>'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Evaluate a city activity shortlist for a traveler's visit window.
Inspect free-cancellation label support before building an excursion filter.
Carry a selected product slug into a read-only attraction detail page.
Retain a selected product ID for a separate date-specific availability inspection.

Frequently asked questions

Which identifier goes to detail versus availability?

Documentation points to a product slug for attraction-detail and a product id for the availability and calendar operations. Preserve those distinct values.

Can I invent category or price labels?

Use supported identifiers from the actual filter metadata. Documentation references filterOptions groups; attraction responses were not live-validated.

Related operations

Guides

View Subscription Plans →