# About attractions 3.2 Beta **Enable travellers to discover, compare, and book unforgettable experiences.** Attractions API – Beta access The Attractions API is currently **available to selected partners** as part of an early access pilot. - **Pilot phase** - The API is under active development and subject to change. - **Available flows** - Search and Content flows are currently [test-ready in Beta](/demand/docs/open-api/3.2-beta/demand-api/attractions). - Reporting is available in production via orders/details v3.2. See [guide](/demand/docs/orders-api/order-details). - **Access** - Only approved partners can use this API collection. - Contact your Partnership Manager to request access. - **Frequent updates** - Documentation and API specs will be updated regularly during the pilot. - Check the [Changelog](/demand/docs/whats-new/changelog) periodically for the latest updates. ## Demand API for Attractions Expand your offering with the Demand API for Attractions, giving travellers access to a **global catalogue of tours, activities, and tickets**. * Seamlessly integrate real-time content, pricing, and availability from trusted providers worldwide. * Deliver experiences that increase engagement, conversion, and post-booking value. **Attraction categories include:** * Museums & culture * Nature & outdoor * Food & drinks * Entertainment & tickets * Workshops & classes * Travel services & rentals. ### Key benefits - **Global reach** - Tap into a worldwide catalog of attractions available in 95 countries, from museums and tours to amusement parks. - **Real-Time availability** - Access instantly latest prices and availability. - **Increased language coverage** - We offer a wide range of activities in more than 27 languages. - **Enhanced latency** - Allow your travellers faster data access through content caching. - **Efficient pagination** - Retrieve large datasets reliably with pagination, giving you predictable and performant responses. ### What you can build Use the Attractions API to power experiences such as: | Use case | Description | | --- | --- | | **Comparison websites** | Display Booking.com Attractions results alongside multiple suppliers for seamless comparison. | | **Post-booking cross-sell** | Offer personalised attraction suggestions after a traveller books a car rental or accommodation. | | **Branded experiences** | Build a seamless end-to-end experience with your own branding and UX. | | **In-path integrations** | Offer attractions as optional add-ons during the accommodation booking flow. | ## Who is this for? The Attractions API collection is recommended for **existing Demand API Affiliate Partners** who want to: ✓ Extend their product offering beyond accommodation and transport. ✓ Increase engagement with personalised, contextual activity recommendations. ✓ Drive additional revenue through post-booking offers. ## Integration flows The Attractions API follows the same integration logic as the accommodation and cars. Currently, Content and Search flows are supported in 3.2 Beta version, while Reporting is stable in production. div div h4 span 3.2 Beta Content ul li Store and retrieve attraction static data such as names, locations, reviews and categories. li Content for display/comparison. li For catalogue-based experiences or pre-populated results pages. a Learn more → div h4 span 3.2 Beta Search ul li Display attractions results by city or region, with reviews, supported languages, and traveller scores. li strong Redirect users to complete the booking . li For testing and early feedback. a Learn more → div h4 span 3.2 Stable Reporting ul li Retrieve attraction order details for reporting and analytics (e.g., commissions, tracking). li Stable version. a Learn more → ### Content flow Allow travellers to browse Booking.com’s attraction catalogue directly within your app. Redirect them to Booking.com for pricing, availability, and booking completion. * Endpoint: /attractions/details * Data type: [static content](#static-data-and-caching)t — updated infrequently (e.g., descriptions, photos, coordinates). Best practice See the [Look attraction details guide](/demand/docs/attractions/retrieve-attraction-details#best-practice---store-attraction-details) for best practices on static data. ### Search flow Enable travellers to find and explore attractions by search criteria. #### Main actions and endpoints These are the main actions and involved endpoints: | Action | Endpoint | Result | | --- | --- | --- | | Search for attractions | [attractions/search] | Retrieve a list of attractions with pricing and essential information based on user input. | | Display details | [/attractions/details] and [attractions/reviews] | Access extended content such as reviews, photos, and cancellation details. | | Redirect to Booking.com | Redirect URL from the /search response | Sends users to Booking.com to complete their booking. | Beta Version – v3.2 This version is currently in **Beta** and subject to changes. Use it for early integration or testing purposes only. **Special permission from Booking.com is required** to access it, contact your Account Manager for access. ### Reporting Use /orders/details v3.2 to retrieve attraction order data including: * Attraction name and location. * Reservation ID. * Booking and commission details. See the [Orders details guide](/demand/docs/orders-api/order-details) for complete response examples and reporting use cases. ## Next steps Try it out! * Start with the [Attractions API Quick Guide](/demand/docs/attractions/attractions-quick-guide). * Explore the [Search for attractions guide](/demand/docs/attractions/search-attractions). * Learn how to [Store and display attraction details](/demand/docs/attractions/retrieve-attraction-details). * Planning a migration to v3.2? See the [Migration guide](/demand/docs/migration-guide/overview).