Find Attraction Destinations

View all Booking.com Hotel & Travel Data endpoints →

Resolve an attraction destination with query and optional currency_code/language_code. Documentation identifies cityUfi as the destination value used by attraction-search and attraction-get-filters. This suggestion route was not live-validated; inspect returned city identities, geography, and actual field structure before constructing a visit search. Keep attraction destination identity separate from hotel and flight identifiers.

API Features

Attraction destination text entry Evaluate suggestions for a traveler-entered activity destination.
Documented cityUfi handoff Inspect the destination value before setting city_ufi in attraction search.
Localized attraction discovery input Choose a supported language preference for destination suggestions.
Attraction identity namespace Do not substitute hotel IDs or airport codes for the destination selected here.

Live API Demo

GET /api/project/booking/attraction-auto-complete

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-auto-complete?key=<API_KEY>&query=new+yor'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What value is used for attraction-search city_ufi?

Documentation points to cityUfi from attraction destination suggestions. Inspect the actual response before extracting it; the route was not live-validated.

Is this accommodation autocomplete?

No. It is the documented attraction-destination workflow. The failed accommodation autocomplete routes are not included in this project.

Related operations

Guides

View Subscription Plans →