A changelog records and lists notable changes to products or projects with links to the relevant documentation. This changelog also includes changes to the documentation. The logs are chronological, with the newest date on top. Every two weeks you can find an overview of:
- What is new?
Refers to new API products or features. - What is going to change?
Refers to upcoming changes or updates to existing API products or features. - What has changed?
Refers to minor changes or updates to existing API products or features. - What was fixed?
Refers to bug fixes.
In this release cycle, we are excited to introduce Payments API v1.1. Additionally, we want to bring your attention to two bug fixes. Read on for more information.
- Payments API New version v1.1 for multiple endpoints
Why?
To provide a more detailed breakdown of partner payouts, commissions, charges, and reservation payment information while remaining backward compatible.
What?- As of June 1st 2026, the Payments API uses
1.1as the latest version by default when theaccept-versionheader is not provided. - Providers can keep the v1.0 behavior by passing the
accept-version: 1.0request header. - The
partner_payout.commissions_and_charges.breakdownobject separatestotal_commissionsandtotal_charges. - Charge items in
price_breakdown[].charges[]includeapplicable_ratewhen a base rate is available. - Charge items in
price_breakdown[].charges[]includeapplicable_typeto show how a charge applies to a reservation, for examplePER_PERSONorPER_NIGHT. - The response includes
payment_tagsto indicate the payment type and collection method for a reservation. - Bank transfer payout details include
bank_transfer_referenceto help identify and track a payout.
To learn more, see the Managing payment and payout details documentation.
- As of June 1st 2026, the Payments API uses
[Office] Incorrect "fewer than usual ACKs" alerts (ACI-4588)
The system now correctly sends ACK alert emails again.
Authentication Valid JWTs incorrectly rejected with 401 errors (ACI-4586)
The system now correctly validates JWT tokens.
In this release cycle, we are excited to introduce the Payments by Booking Onboarding API, Credit Card Status API, and a new Property Deal in the Promotions API. Additionally, we want to bring your attention to three bug fixes. Read on for more information.
Payments by Booking Onboarding API New API with multiple endpoints
Payments by Booking Onboarding API enables you to check whether a property is eligible for Payments by Booking, submit onboarding requests with preferred payout settings, track request status, and receive status update notifications.
To learn more and start using it, see the Payments by Booking Onboarding API documentation.
Credit Card Status API New API with multiple endpoints
Credit Card Status API enables you to check the validity of credit cards for "Pay at property" reservations and take action when a card is invalid.
To learn more and start using it, see the Credit Card Status API documentation.
Promotions API New Property Deal
New Property Deal enables you to create a new promotion type in the existing Promotions API for eligible new properties that have been open and bookable on Booking.com for less than 12 months and have no reservations yet.
To learn more and start using it, see the Creating a new property deal.
Property Details API Duplicate concurrent request errors on property creation (ACI-4582)
The system now correctly returns successful creation responses for new properties without duplicate concurrent request errors again when using the Property Details API.
Reservations API Cancellation XML sent as modification (ACI-4554)
The system now correctly returns cancellation XML messages without roomstay information again when using the Reservations API.
Reservations API Incorrect roomrate price (ACI-4486 and ACI-4499)
On 14 April, we announced a fix for the issue affecting the roomrate price information returned by the Reservations API. However, we continued to observe the issue after that release. The relevant team has now implemented an additional fix, and the system is correctly returning roomrate price information again when using the Reservations API.
Happy Spring! In this release cycle, we are excited to introduce you to the new version 1.3 of the POST OTA_HotelProductNotif endpoint. Additionally, we want to bring your attention to five bug fixes.
Room type and rate plan management API New version of the
OTA_HotelProductNotifendpoint is now live!Booking.com has released a new version 1.3 of the
POST OTA_HotelProductNotifendpoint.To learn more and start using it, see the blog about What’s new in OTA_HotelProductNotif v1.3?.
We plan to deprecate the old version 1.0 by 15th of May 2026, and sunset it on 1st of September 2026. For more information, see the Migration guide.
Facilities API Error when deleting all bathrooms (ACI-4544)
The system now correctly returns valid responses when deleting all bathrooms again when using the Facilities API.
Reservations API Intermittent 503 errors (ACI-4549)
The system now correctly returns reservation retrieval responses again when using the Reservations API.
Reservations API Cancellation XML contained roomstay information (ACI-4554)
The system now correctly returns cancellation XML messages without roomstay information again when using the Reservation API.
Reservations API Missing confirmation XML messages (ACI-4569)
The system now correctly returns confirmation XML messages for reservations again when using the Reservations API.
[Extranet Pages] Unable to activate or deactivate connectivity connection in the Connectivity Provider page (ACI-4580)
Extranet users can now correctly activate or deactivate the connectivity connections again from the Connectivity Provider page.
In this release cycle, we don't have any major updates. However, we want to bring your attention to two bug fixes. Read on for more information.
Reservations API Incorrect roomrate price (ACI-4486 and ACI-4499)
The system now correctly returns the roomrate price information when using the Reservations API.
In this release cycle, we don't have any major updates. However, we want to bring your attention to two bug fixes. Read on for more information.
Room type and rate plan management API Incorrect
room_name(ACI-4494)The system now correclty returns the
room_namewhen using thePOST xml/roomratesendpoint.Reservations API Cancellation messages incorrectly shared as modifications (ACI-4500)
The system now correctly returns all cancellation messages again when using the Reservations API.
In this release cycle, we don't have any major updates. However, we want to bring your attention to two bug fixes. Read on for more information.
Reservations API Missing Promotion ID (ACI-4480)
The system now correctly includes the promotion ID in reservation messages again.
Reservations API Missing reservation messages (ACI-4497)
The system now correctly returns all reservation messages again when using the Reservations API.
In this release cycle, we don't have any major updates. However, we want to bring your attention to one bug fix. Read on for more information.
Reservations API Incorrect guest count details in
guest_counts(ACI-4461)The system now returns correct
guest_countsdetails in reservation messages again.
In this release cycle, we don't have any updates. We will come back next time with more information.
In this release cycle, we don't have any major updates. However, we want to bring your attention to one bug fix. Read on for more information.
Property API Incorrect
Invalid postal code: 00000 in invoice_settings for country code: AEerror (ACI-4422)The system no longer incorrectly returns an
Invalid postal code: 00000 in invoice_settings for country code: AEerror when using thePOST /property-api/properties/{property_id}/settingsendpoint.
In this release cycle, we don't have any major updates. However, we want to bring your attention to a few bug fixes. Read on for more information.
Property API Incorrect
allowed_values:["OTHER"]error (ACI-4435)The system no longer incorrectly returns an
allowed_values:["OTHER"]error when using thePOST /property-api/statusendpoint.Reservations API Incorrect
Total@AmountinPriceDetailsnode (ACI-4425)The system now returns correct
Total@AmountofPriceDetails/HotelViewandPriceDetails/GuestViewnodes in reservation messages again.[Contacts API] Incorrect 500 error (ACI-4405)
The system no longer returns internal server error when calling the
PUT /contacts-api/properties/{propertyID}/contactsandPUT /contacts-api/properties/{propertyID}/contactsendpoints.
Happy new year! In this release cycle, we are excited to introduce the new Try it feature in our API documentation, which helps you perform static API response testing. Additionally, we want to bring your attention to a few bug fixes. Read on for more information.
[Documentation] Enabling static API response testing
The developer portal now supports testing static API responses using the existing OpenAPI specifications. Use the
Try itbutton available on the OpenAPI specification pages to test API requests with custom parameters and payloads.For example, you can use the specifications from the Property API, Rooms API, Contacts API, Facilities API and Charges API. This makes it easier to explore the API behavior, validate request and response bodies, and iterate on integrations without leaving the developer portal.
To learn more about this feature and how to use it effectively, see About Try it.
Reservations API Incorrect guest count details in
guest_counts(ACI-4412)The system now returns correct
guest_countsdetails in reservation messages again.Property API Incorrect
Authorization errorerror (ACI-4406)The system no longer incorrectly returns an
Authorization errorerror when using thePATCH /property-api/propertiesendpoint.Reservations API Missing credit card details after the guest updates their card (ACI-4395)
The system now correctly includes the updated credit card details in the modification messages again.
Room type and rate plan management API Incorrect
Successresponse when creating a rate (ACI-4386)The system now correctly creates the rateplan and returns a valid
ResponseRatePlanCodewhen using the version 1.0OTA_HotelRatePlanNotifendpoint.Authentication Valid JWTs incorrectly rejected with 401 errors (ACI-4384)
The system now correctly validates JWT tokens.