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
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-auto-complete API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/attraction-auto-complete?key=<API_KEY>&query=new+yor'
Query Result
Use Cases
- Evaluate a localized destination selector for a tours-and-activities prototype.
- Resolve an activity destination before requesting a visit date window.
- Check similarly named attraction cities before selecting a cityUfi.
- Audit destination identity handoff between attraction discovery and search.
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.