Get Attraction Details by Slug
View all Booking.com Hotel & Travel Data endpoints →Request documented attraction details with a product slug from attraction search and optional currency_code/language_code. A display title is not a substitute for the returned slug. This detail response was not live-validated; inspect actual descriptions, conditions, product identity, and any price fields before presentation. Use the separate product_id-based operations for date availability rather than inferring it from detail text.
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 API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/booking/attraction-detail?key=<API_KEY>&slug=<slug>'
Query Result
Use Cases
- Evaluate an excursion detail page for a selected activity search result.
- Compare documented conditions for two shortlisted attraction products.
- Inspect localized product descriptions before a permitted itinerary-content use.
- Check slug provenance when importing a traveler-selected activity.
Frequently asked questions
Can I derive slug from a product title?
Use the slug supplied by attraction search rather than inventing one from text. The dedicated detail response was not live-validated.
Does detail lookup prove an attraction is available on my date?
No. This request has no date input. Inspect a selected product's date-specific availability separately, without assuming a booking guarantee.