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

Selected product and visit date Pair a known attraction product ID with one explicit YYYY-MM-DD date.
Product ID distinct from slug Use the documented search product id rather than a title or detail slug.
Availability locale and currency context Keep display preferences aligned with the activity shortlist.
Capacity not reserved by retrieval Inspect actual returned availability without implying admission is held.

Live API Demo

GET /api/project/booking/attraction-detail-get-availability

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-detail-get-availability?key=<API_KEY>&date=<date>&product_id=<product_id>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →