Stay up to date with the latest enhancements to the Demand API.
This release focuses on Demand API version 3.2 and 3.2 Beta, with updates across accommodations, car rentals and orders:
- 3.2 Beta
- Accommodation
- /accommodation/smart-search – New Beta endpoint for AI-powered accommodation search experiences.
- Orders (Car rentals)
booker.language– Now required in car rental booking creation requests.payment.card– Validation is now enforced for car rental card payments in /orders/create.
- Common
- /common/autocomplete – New Beta endpoint for real-time autocomplete suggestions based on a free-text query.
- v3.2
- Car rentals
estimated_commission– New field available in /cars/search responses for eligible partners.likeliness_rent_again– Deprecated in /cars/depots/reviews/scores and scheduled for removal in v3.3.
| 3.2 Beta | New endpoint: /accommodations/smart-search |
A new Beta endpoint is available to support AI-powered accommodation discovery and flexible search experiences.
Supports more dynamic traveller search journeys by:
- Enabling intent-based accommodation discovery.
- Supporting flexible and conversational search flows.
- Returning accommodation recommendations based on traveller input.
This endpoint is currently available in Beta and may evolve before general availability.
Available in:
| v3.2 | New field: estimated_commission |
A new
estimated_commissionobject is now available in /cars/search responses for eligible partners.Provides an estimated commission amount that the partner may earn if the traveller books the selected car rental.
The field:
- Uses predictive modelling at search time.
- Is only returned when the predicted commission feature is enabled.
- Is omitted when a reliable estimate cannot be produced.
Example:
"estimated_commission": {
"amount": 12.50,
"currency": "GBP"
}Use this field for indicative commission visibility during search flows. Values are estimates and may differ from final earned commission.
| v3.2 3.2 Beta | Deprecated field: likeliness_rent_again |
The
likeliness_rent_againfield in /cars/depots/reviews/scores responses is now deprecated. Aligns API responses with the scores currently surfaced on Booking.com websites and apps. The field:
- Is considered legacy.
- Will remain available in v3.2 for backwards compatibility.
- Will be fully removed in v3.3.
Update integrations to stop relying on likeliness_rent_again before upgrading to v3.3.
| 3.2 Beta | Mandatory field: booker.language |
The
booker.languagefield is now required in /orders/create requests for car rental bookings. Purpose – Ensures the traveller’s preferred language is consistently available throughout the booking flow, including the legal terms.
Example:
"car_booker": {
"address": {
"...": "..."
},
"email": "john.doe@example.com",
"language": "en-gb",
"name": {
"...": "..."
},
"telephone": "+44123456789"
}| 3.2 Beta | Mandatory field: payment.card |
Validation is now enforced for card payment in /orders/create requests for car rental bookings. Purpose – Ensures payment is validated consistently against the partner’s configured payment methods and prevents invalid or incomplete payment requests. The update:
- Requires
payment.cardobjects to be present for car rental order payments.- Aligns car rental payment validation with accommodation online payment flows.
| 3.2 Beta | New endpoint: /common/autocomplete |
A new endpoint is available to retrieve real-time autocomplete suggestions based on a free-text query.
Purpose – Enables fast, relevant destination suggestions as users type.
- Supports low-latency, “as-you-type” autocomplete interactions.
- Helps users discover destinations with partial input and basic typo tolerance.
- Enables more guided and efficient search flows.
Example request:
{
"query": "ams",
"language": "en-gb",
"country": "nl",
"filters": {
"types": ["city"]
}
}Requests with a query shorter than 3 characters or invalid filters.types values will return a 400 error.
