Choose the integration type that best fits your business model. Whether you want to display travel content, redirect travellers to Booking.com, build a complete booking experience, or manage bookings after confirmation, the Demand API provides a flexible set of APIs that you can adopt progressively.
The Demand API supports multiple integration types that build on one another. You can start with a simple content integration and gradually expand your implementation to include booking, post-booking management, and reporting.
While some capabilities are currently available only for specific travel services, the overall integration patterns are consistent across accommodations, cars, and future travel services.
Content only
Display travel content on your platform and redirect travellers to Booking.com to complete their booking.
Search, look and redirect
Let travellers search and view travel options on your platform before redirecting them to Booking.com to complete their booking.
Search, look and book
Build a fully integrated booking experience where travellers can search, view details and complete bookings without leaving your platform.
Post-booking management
Extend your integration with post-booking capabilities, including order management, insurance and loyalty rewards.
Reporting and reconciliation
Access reporting, reconciliation and financial data for existing orders across supported travel services.
Each integration type builds on the previous one, allowing you to expand your implementation over time without redesigning your architecture.
Display Booking.com travel content one your platform and redirect travellers to Booking.com to complete their booking.
This is the simplest integration and is suitable when you want to enrich your application with travel content without implementing search or booking functionality.
Content-only integrations are supported across all travel services.
✓ Retrieve static travel content relevant to your business.
✓ Store frequently used content locally.
✓ Display destinations, properties, cars, or attractions.
✓ Redirect travellers to Booking.com when they choose to continue.
Static data changes infrequently and should be stored locally to reduce API calls and improve response times.
Static data falls into two categories:
Descriptive information about travel products, such as:
- addresses
- facilities
- photos
- descriptions
Retrieve this information using endpoints such as:
Reference data contains identifiers and codes used throughout the API.
It is available through:
- locations
- currencies
- languages
- payment cards
Travel-service constants:
Using local storage avoids repeated requests and improves overall application performance.
Store all static data used by your application.
Without local storage, your application may need to make multiple API requests to retrieve information required to display a single search result.
Prices and availability change frequently.
Always retrieve current prices and availability using the relevant Search and Availability endpoints.
Allow travellers to search for travel products, view live pricing and availability, and complete their booking on Booking.com.
This integration is available across supported travel services.
| Step | Endpoint | Purpose |
|---|---|---|
| Search | /search | Find travel products matching traveller preferences. |
| Look | /availability | Retrieve live prices, availability and product details. |
| Enrich | Local storage | Display additional travel static content such as photos and descriptions. |
| Book | Booking URL | Redirect travellers to Booking.com to complete the booking. |
Build a complete booking experience directly on your platform.
Travellers can search, review live availability and complete their booking without leaving your application.
This integration is currently available for accommodations.
Car rental booking flow is currently available only in Beta. Support for additional travel services will be introduced in future releases.
| Step | Endpoint | Purpose |
|---|---|---|
| Search | /search | Find products matching traveller preferences. |
| Look | /availability | Retrieve live pricing and availability. |
| Preview | /orders/preview | Validate pricing, payment requirements and booking details before confirmation. |
| Book | /orders/create | Create and confirm the booking. |
Manage bookings after they have been confirmed.
Post-booking APIs allow you to retrieve booking information, update orders, cancel reservations, retrieve insurance information and integrate loyalty programmes.
| Capability | Endpoint | Purpose |
|---|---|---|
| View order details | /orders/details/accommodations | Retrieve full booking details for confirmed accommodation orders. |
| Live order information | /orders/details/cars/live (Beta) | Retrieve real-time information for active car bookings, including purchased insurance documents. |
| Modify bookings | /orders/modify | Update supported booking information. |
| Cancel bookings | /orders/cancel | Cancel eligible bookings. |
Typical use cases include:
- Display booking confirmations.
- Show traveller itineraries.
- Retrieve insurance and legal information.
- Access loyalty rewards.
- Manage cancellations and modifications.
Retrieve financial and reconciliation data for bookings across supported travel services.
Unlike post-booking management, reporting integration are designed for systems that process bookings after they have been confirmed, such as finance platforms, reporting tools or reconciliation systems.
The /orders/details endpoint provides a unified interface for retrieving detailed order information regardless of the travel service.
| Endpoint | Purpose |
|---|---|
| /orders/details | Retrieve detailed financial and booking information for one or more orders across supported travel services. |
Typical reporting use cases include:
- Reconciling completed bookings.
- Generating financial reports.
- Validating commission payments.
- Retrieving payment information.
- Exporting booking data into internal systems.
- Supporting finance and accounting processes.
The /orders/details endpoint returns a consistent order schema across supported travel services.
This allows you to build a single reporting and reconciliation integration instead of implementing separate reporting workflows for accommodations, cars, and future travel services.
| If you want to... | Choose |
|---|---|
| Display travel content | Content only |
| Let travellers search before redirecting to Booking.com | Search, look and redirect |
| Complete bookings in your platform | Search, look and book |
| Manage confirmed bookings | Post-booking management |
| Retrieve financial and reconciliation data | Reporting and reconciliation |
After choosing your integration type:
Explore the relevant endpoints in the OpenAPI reference.
Set up your sandbox environment and make your first API calls. Follow the Quick guide for initial calls.
Implement best practices for storing static data and handling errors.
Expand your integration to additional travel services as they become available.
Validate your implementation before moving to production.
Need help deciding which integration type is right for your business? Contact your Booking.com Account Manager.