Enable travellers to search for transfers, compare vehicle options and complete their booking on Booking.com.
The Transfers API collection is currently available in Beta to selected partners as part of an early access pilot.
- Pilot phase - The API is under active development and subject to change.
- Available flow
- Search and redirect is currently available through the /transfers/search endpoint.
- Access - Only approved partners can use this API collection.
- Contact your Partnership Manager to request access.
- Frequent updates - Documentation and API specifications may be updated regularly during the pilot.
- Check the Changelog periodically for the latest updates.
The Transfers API collection enables you to offer transfers from airports, cities and other locations within your application.
Search for available transfers based on:
- The traveller's pick-up and drop-off locations.
- The journey date and time.
- The number of passengers.
- The requested currency.
- The booker's country.
You can display the returned journey details, vehicle options, prices and cancellation policies in your application.
Travellers can then select an option and continue to Booking.com to complete their booking.
With the Transfers API collection, you can:
- Offer one-way and return transfers.
- Search using airports, Google Place IDs or geographic coordinates.
- Find vehicle options with sufficient capacity for the requested number of passengers.
- Display maximum passenger and luggage capacity.
- Show prices in the traveller's requested currency.
- Display resolved pick-up and drop-off locations.
- Show the estimated journey duration and distance for each journey leg.
- Display the cancellation policy for each available vehicle option.
- Redirect travellers to Booking.com to complete their booking.
Use the Transfers API collection to power experiences such as:
| Use case | Description |
|---|---|
| Airport transfer search | Let travellers search for transfers between an airport and their accommodation or another destination. |
| Travel itinerary add-ons | Offer transfers as an optional service alongside accommodation, flights or other travel services. |
| Comparison experiences | Display available vehicle options, prices and capacities so travellers can compare transfer options. |
| Branded travel journeys | Build a transfers search experience using your own branding and user interface, then redirect travellers to Booking.com to complete the booking. |
| Pre-trip planning | Help travellers arrange transport for upcoming one-way or return journeys. |
The Transfers API collection is recommended for existing Demand API Affiliate Partners who want to:
- Extend their travel services offering with airport and local transfers.
- Improve the traveller journey by offering transport options alongside other travel services.
- Help travellers compare vehicle capacity, prices and cancellation conditions.
- Drive additional revenue through relevant travel add-ons.
- Offer a branded search experience while relying on Booking.com to complete the booking.
The Transfers API collection supports the Search, look and redirect flow in Beta. Transfers order reporting is available through the Orders API in v3.2.
Beta | Search, look & redirect
- Search for transfers and display vehicle options.
- Redirect travellers to Booking.com to complete their order.
- Beta – special permission required.
v3.2 | Reporting and reconciliation
- Retrieve order information for reporting, reconciliation and operational workflows.
- Use the /orders/details endpoint.
- Available in production in v3.2.
Search for transfers using the traveller's journey details and passenger requirements.
Display the returned route, vehicle options, prices, journey details and cancellation policy, then redirect the traveller to Booking.com to complete the order.
See the Search for transfers integration guide for request requirements, search criteria, response fields and implementation examples.
Use the /orders/details endpoint to retrieve transfers order data for reporting, reconciliation and operational workflows.
A transfer order may contain multiple journey legs:
- The order-level price, start, end and status are aggregated across all legs.
- Each leg has its own reservation, leg identifier and lifecycle.
For accurate reporting and tracking, inspect both the order-level information and the individual transfer legs.
See the Run order reports guide for request examples and reporting use cases.
Try the transfers API collection:
- Read the Search for transfers integration guide for request requirements, response fields and examples.
- Read the Reporting and reconciliation integration guide to learn how to use order data in back-office workflows.
- Explore the /transfers/search API reference.
- Review the Changelog for the latest Beta updates.