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

Search-selected product slug Retain the exact slug returned for the chosen attraction product.
Attraction detail language preference Request a supported language for evaluating product content.
Description and conditions inspection Validate the actual detail sections before designing an excursion page.
Detail separated from availability Use a product ID and visit date for the dedicated availability step.

Live API Demo

GET /api/project/booking/attraction-detail

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

Use Cases

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.

Related operations

Guides

View Subscription Plans →