Skip to content
Last updated

About attractions Attractions

Enable travellers to discover, compare, and book unforgettable experiences.

v3.2 v3.3


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 caseDescription
Comparison websitesDisplay Booking.com Attractions results alongside multiple suppliers for seamless comparison.
Post-booking cross-sellOffer personalised attraction suggestions after a traveller books a car rental or accommodation.
Branded experiencesBuild a seamless end-to-end experience with your own branding and UX.
In-path integrationsOffer 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, Search, look and redirect and Reporting are available in stable versions.

Integration flows

The Attractions API follows integration patterns similar to those used for the accommodation and car APIs.

Content, Search, look and redirect, and Reporting are available in stable versions 3.2 and 3.3.

v3.2 | v3.3 | Content flow

  • Store and retrieve static attraction data, such as names, locations, reviews and categories.
  • Use attraction content for display and comparison.
  • Support catalogue-based experiences and pre-populated results pages.

v3.2 | v3.3 | Search, look & redirect

  • Display attraction search results for a city or region, including reviews, supported languages and traveller scores.
  • Redirect travellers to Booking.com to complete their booking.

v3.2 | v3.3 | Reporting and reconciliation

  • Retrieve attraction order details for reporting and analytics, including commission and tracking information.

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.

Best practice

See the Look attraction details guide 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:

ActionEndpointResult
Search for attractions/attractions/searchRetrieve a list of attractions with pricing and essential information based on user input.
Display details/attractions/details and //attractions/reviewsAccess extended content such as reviews, photos, and cancellation details.
Redirect to Booking.comRedirect URL from the /search responseSends users to Booking.com to complete their booking.

Reporting

Use /orders/details to retrieve attraction order data including:

  • Attraction name and location.
  • Reservation ID.
  • Booking and commission details.

See the Order details guide for complete response examples and reporting use cases.


Next steps

Try it out!