Display Booking.com travel content on your platform and redirect travellers to Booking.com to complete their booking.
A Content only integration lets you use Demand API travel content without implementing live search, pricing or booking capabilities:
- Retrieve descriptive and reference data from the Demand API and use it to build travel discovery experiences on your platform.
- Redirect travellers to Booking.com when they are ready to continue their journey.
- Use Content only as a standalone integration or extend your application later with search and booking capabilities.
It does not provide live prices or availability. To display live prices and availability, use a Search, look and redirect integration.
Choose this integration if you want to:
- Display descriptive travel content in your application.
- Build destination or travel-product discovery experiences.
- Redirect travellers to Booking.com to complete their booking.
- Provide travel content without implementing live search, pricing or booking.
You can use Content only as a standalone integration or extend your application later with search and booking capabilities.
Before implementing this integration, complete the Demand API prerequisites.
Your application retrieves descriptive and reference data from the Demand API and stores the data required by your experience locally.
- Travellers browse this content on your platform without requiring a live Demand API request for every page view.
- When a traveller chooses to continue, redirect them to the appropriate Booking.com experience.
A typical Content only integration follows these steps:
| Step | Description |
|---|---|
| Retrieve descriptive travel content from the endpoints for the travel services you support. |
| Store content that changes infrequently and refresh it according to the requirements of each travel service. |
| Use the stored content to build travel discovery experiences in your application. |
| Redirect travellers to Booking.com when they are ready to continue their journey. |
Travel content describes the products and locations that travellers see in your application. Depending on the travel service, this can include:
- Names and descriptions.
- Addresses and locations.
- Facilities and amenities.
- Photos.
- Car rental locations and depot information.
Retrieve the content you need using the endpoints available for each travel service.
Use /accommodations/details to retrieve descriptive information about accommodations.
Use:
- /cars/details to retrieve descriptive car rental content.
- /cars/depots to retrieve car rental depot information.
Available content and endpoints vary by travel service. Refer to the API reference for the travel service you are integrating.
Reference data contains identifiers, codes and other values used across Demand API requests and responses.
Depending on your integration, reference data can include:
- Locations.
- Languages.
- Currencies.
- Payment card types.
- Accommodation chains.
- Travel-service-specific constants.
Retrieve shared reference data from the relevant:
- Common endpoints
For travel-service-specific reference data, use endpoints such as:
Reference data generally changes infrequently. Store the reference data required by your integration locally and reuse it across API requests where appropriate.
Store content that changes infrequently locally instead of retrieving it each time a traveller views a page.
This helps you:
- Reduce unnecessary API requests.
- Reduce latency in traveller-facing experiences.
- Avoid retrieving the same content repeatedly.
- Build pages using data that is already available to your application.
Store only the content required by your application.
- The content available and how frequently it should be refreshed can vary by travel service.
- Refresh your stored content regularly so that changes to the source data are reflected in your application.
- Follow any travel-service-specific recommendations for retrieving and refreshing content.
Prices and availability can change frequently. Do not use stored content to represent current prices or availability.
To retrieve current prices and availability, use the relevant Search and Availability APIs as part of a Search, look and redirect integration.
Use the content stored by your application to build the traveller-facing experience.
For example, you can use Demand API content to:
- Display accommodation information and photos.
- Show facilities and amenities.
- Build destination or travel-product discovery pages.
- Display car rental locations and depot information.
Only display data that is relevant to the travel services and products supported by your integration.
A Content only integration does not complete the booking within your application.
When a traveller decides to continue, redirect them to the appropriate Booking.com experience to continue their journey and complete the booking.
If you want travellers to see current prices and availability on your platform before being redirected, implement a Search, look and redirect integration.
Before considering your Content only integration complete, verify that:
Checklist | |
|---|---|
| ☑ | You retrieve the descriptive content required by your application. |
| ☑ | You retrieve and store the required reference data. |
| ☑ | Content that changes infrequently is served from your stored data where appropriate. |
| ☑ | Stored data is not used to represent current prices or availability. |
| ☑ | Travellers are redirected to the appropriate Booking.com experience when they choose to continue. |
| ☑ | Redirect and attribution requirements are implemented for each supported travel service. |
After implementing Content only:
- Test your content retrieval and storage strategy.
- Verify that stored content is refreshed appropriately.
- Verify your Booking.com redirect flow.
- Review the API reference and error handling recommendations for the endpoints you use.
To add live prices and availability to your traveller experience, continue with the Search, look and redirect integration.