Check Attraction Availability by Date
View all Booking.com Hotel & Travel Data endpoints →Inspect documented availability with a selected product_id and required date in YYYY-MM-DD format, plus optional currency_code/language_code. Documentation identifies product_id as the attraction-search product id, not its slug or the city_ufi. The live availability response, timeslots, prices, and capacity were not validated. Treat any returned choices as informational candidates, not purchased admission or held capacity.
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-detail-get-availability API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/attraction-detail-get-availability?key=<API_KEY>&date=<date>&product_id=<product_id>'
Query Result
Use Cases
- Evaluate a selected excursion for a traveler-chosen visit date.
- Recheck a product candidate after an itinerary moves to another day.
- Inspect actual availability fields before implementing timeslot choices.
- Compare dated activity candidates without presenting a search result as purchased admission.
Frequently asked questions
Can product_id contain the attraction slug?
No equivalence is documented. Use the product id from attraction search; slug belongs to the detail endpoint.
Will this request reserve tickets?
No. It is a read-only availability request. Actual availability fields, prices, and capacity were not live-validated, and no purchase or reservation is created.