Changelog
Stay up to date with our latest technical enhancements.
Changelog - December 2024
Welcome to the final changelog of 2024.
This month we've focused on order improvements in Demand API V3.1! Some of the key highlights include:
Orders/preview
| New field | chargeable online price | orders/preview | Available to all partners |
We have introduced
chargeable online price
object in orders/preview endpoint response:
- This object specifies the amount that will be charged online by Booking.com.
- This amount will always be less than or equal to the total price.
Example:
{
"chargeable_online": {
"accommodation_currency": 121.03,
"booker_currency": 121.03
}
}
- You can find this field in two places:
- Order level: Located at accommodation.price.chargeable_online.
- Product level: Located at accommodation.products[i].price.chargeable_online.
The chargeable_online field is linked to the existing boolean flags:
- accommodation.price.extra_charges.non_conditional[i].chargeable_online.
- accommodation.products[i].price.extra_charges.non_conditional[i].chargeable_online.
These flags indicate which charges contribute to the total chargeable amount represented by the chargeable_online field.
Example with both boolean and price object:
{
"price": {
"base": {
"accommodation_currency": 110.03,
"booker_currency": 110.03
},
"extra_charges": {
"conditional": [],
"non_conditional": [
{
"charge": 21,
"chargeable_online": true,
"mode": "percentage",
"percentage": 10.00,
"total_amount": {
"accommodation_currency": 11.00,
"booker_currency": 11.00
},
"unit_amount": {
"accommodation_currency": null,
"booker_currency": null
}
}
]
},
"chargeable_online": {
"accommodation_currency": 121.03,
"booker_currency": 121.03
},
"total": {
"accommodation_currency": 125.53,
"booker_currency": 125.53
}
},
"room": 438312701
}
If you use pay_at_the_property
payment timing, please disregard any chargeable_online
field present in the response, as charges are handled directly by the property and not by Booking.com.
Orders/create
| New error messages | payment failures | orders/create | Available to all partners |
When making a reservation using Payments through the orders/create endpoint, and the payment fails, the response no longer returns the generic error
payment_refused
( message: Payment collection failed).Instead, if available, a more specific error message is provided, offering greater clarity about the cause of the failure.
For a complete list of error codes and descriptions, please refer to the payment error handling section.
Orders/details
| Flights orders inclusion | order/details | Available to all partners |
You can now check the flight details of an order via the order/details endpoint.
You just need to pass "flights" as service when calling this endpoint:
{
"created": {
"from": "2024-09-25T00:00:00+00:00",
"to": "2024-09-30T23:00:00+00:00"
},
"services": [
"flights"
],
"sort": {
"by": "created",
"direction": "ascending"
},
"maximum_results": 100,
"currency": "EUR"
}
Refer to the orders/details guide for more details and examples.
Orders/details/accommodations
| New fields | /orders/details/accommodations | all partners if enabled |
We have introduced the
External account id
field under thebooker
object, in this endpoint response:
- This is a unique identifier that represents the account provided by the partner in Booking.com settings.
- This field is used to link a specific accommodation order to the corresponding external account.
This field is not displayed if partner does not have a PII agreement or has not enabled the setting.
Example:
{
"booker": {
"external_account": 13610217,
"platform": "mobile"
}
}
Refer to the Order/details guide for more details.
Order/details/cars and flights
| New endpoints | order/details/car | order/details/flights | Available to all partners |
You can use now check details of cars or flight orders, via these new endpoints. They follow a similar pattern to that used for accommodations.:
Refer to the order/details/cars and order/details/flights guidelines for examples and best practices.
Other improvements
In addition to all these new features, we have made general improvements to the rate calculation, aiming to reduce discrepancies between the pricing returned in the orders/preview endpoint and that in the accommodations/availability endpoint.
Changelog archive
Documentation