Changelog
/
Q3 and Q4 2025
Last updated

Changelog

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.

16 December 2025

In this last release cycle for this year, we do not have any updates for you. We wish you happy holidays and a wonderful new year!

9 December 2025

In this release cycle, we do not have any updates for you.

25 November 2025

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.

  • Reservations API Missing reservation messages (ACI-4362)

    The system now correctly returns all reservation messages again when using the Reservations API.

  • Room type and rate plan management API Incorrect Restricted. Net rates must have a non-refundable policy error (ACI-4355)

    The system no longer incorrectly returns the Restricted. Net rates must have a non-refundable policy error when using the POST OTA_HotelProductNotifRS endpoint.

  • [Rates and Availability API] Incorrect RLO updates with single occupancy price specified (ACI-4352)

    The system now correctly returns an error when updating RLO rates with the price1 element.

  • [Provider Portal] Downloaded Email Fallbacks reports incorrectly showing limited data (ACI-4307)

    The Provider Portal now correctly exports all relevant fallback data in CSV files again.

11 November 2025

In this release cycle, we are excited to inform you about new features for the Contracting API, Promotions API and token-based authentication, as well as additional documentation for our Facilities API and Content API. In addition, we want to bring your attention to two bug fixes. Read on for more information.

What is new?

  • [Contracting API] Request to access the existing partner account

    We've introduced a new endpoint POST /partners/request_access in the Contracting API that enables you to request access to the partner account to list properties on their behalf.

    To learn more, see Requesting access to existing partner account.

  • Promotions API Introducing four new deals and configuration options

    We've added the following four new deals to the Promotions API:

    • Black friday deal
    • Early year deal
    • Getaway deal
    • Late escape deal

    In addition, we’ve enhanced the Mobile Rates and the Geo Rates with the following new capabilities where you can:

    • Set unlimited block dates
    • Select specific rate plans
    • Set Minimum length of stay
    • Specify the minimum and maximum booking window

    To learn more, see the blog about the four new deals and flexibility options.

  • Authentication Accessing the public key by the new JWKS (JSON Web Key Set) endpoint

    We've introduced a new GET token-based-authentication/.well-known/jwks.json endpoint that enables you to retrieve the public key to verify the authenticity of the received token.

    To learn more, see Get public key to verify token's signature.

What has changed?

  • [Facilities API][Documentation] List of facilities added

    We've added a new topic that covers two ways to visualize the list of supported facilities.

    • The list of supported facilities using a visual interface.
    • The list of supported facilities using a code-based approach.

    To learn more, see Facilities list.

  • [Content API][Documentation] Migration strategy added

    In the element table of the OTA_HotelDescriptiveContentNotif endpoint, we've added a new column, "Migration Strategy," that describes which new modular content APIs can be used to update each element.

    To learn more, see Create a property page.

What was fixed?

  • [Rates and Availability API] Incorrect OCCUPANCY_EXCEEDS_MAX_PERSONS error (ACI-4342)

    The system no longer incorrectly returns the OCCUPANCY_EXCEEDS_MAX_PERSONS error when using the POST OTA_HotelRateAmountNotif endpoint and the csv/los_pricing endpoint.

  • Reservations API Incorrect Fee Tax Type Codes (ACI-4332)

    The system no longer incorrectly returns text instead of fee tax type codes for the Tax/@Code element in reservation messages again.

28 October 2025

In this release cycle, we do not have any updates for you.

14 October 2025

In this release cycle, we would like to inform you about the removal of add-on information via the Reservations API. In addition, we want to bring your attention to two bug fixes. Read on for more information.

What has changed?

  • [Reservations API][Documentation] Add-On information removed

    The Reservations API no longer includes information related to add-ons as of September 30, 2021. In addition, the API documentation has been updated to remove all add-on related information.

What was fixed?

  • [Rates and Availability API] Reservations allowed for closed roomrates (ACI-4260)

    The system now correctly blocks reservations from being made on roomrates that are closed.

  • Content API Incorrect invalid zip/postal code error (ACI-4269)

    The system no longer incorrectly returns the error when sending overlay updates via the POST OTA_HotelDescriptiveContentNotif endpoint.

30 September 2025 (updated 07 Oct.)

In this release cycle, we would like to introduce you to the version 1.1 of the OTA_HotelRatePlanNotif endpoint. In addition, we want to bring your attention to two bug fixes. Read on for more information.

What is going to change?

What was fixed?

  • Content API Incorrect bathroom count increment (ACI-4264)

    The system now correctly sets the number of bathrooms when sending overlay updates via the POST OTA_HotelInvNotif endpoint.

  • Reservations API Missing Genius rate information (ACI-4235)

    The system now correctly includes the Genius rate information in the relevant reservation messages again.

16 September 2025

In this release cycle, we want to talk about the deprecation of the GET /hotels/json/messaging-auth endpoint from the Messaging API. In addition, we want to bring your attention to a few bug fix. Read on for more information.

What is going to change?

  • Messaging API Upcoming deprecation and sunsetting of the GET /hotels/json/messaging-auth endpoint

    Booking.com will deprecate the GET /hotels/json/messaging-auth endpoint on October 8, 2025 and will sunset it on December 15, 2025.

    To support special & structured request through messaging, use the Messaging API v1.2. To learn more about the deprecation, see Deprecation and sunsetting page.

What was fixed?

  • [Rates and Availability API] Incorrect 403 error (ACI-4228)

    The system no longer incorrectly returns 403 error when using the Rates and Availability API.

  • Reservations API Missing credit card details for SmartFlex reservations (ACI-4252)

    The system now returns the guests' credit card details again in relevant modification messages for SmartFlex reservations.

  • Promotions API Newly created promotions not included in the GET hotels/xml/getpromotions endpoint (ACI-4258)

    The system now returns all promotions again when using the GET hotels/xml/getpromotions endpoint.

  • Content API Incorrect 400 error (ACI-4272)

    The system no longer incorrectly returns the error No city found within 50km lat/lon provided when sending overlay updates via the POST OTA_HotelDescriptiveContentNotif endpoint.

2 September 2025

In this release, we're excited to announce a new feature added to the Charges API. Read on for more information.

What is new?

  • Charges API Age-based charge configuration

    We've introduced a new feature for the Charges API that enables you to configure modifications to the charge amount based on the age of child travelers. This feature is useful for implementing age-specific taxes or discounting a charge for children.

    To learn more, see Age-based charge configuration.

19 August 2025

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.

What was fixed?

  • [Office] Missing connection request emails (ACI-4195)

    When properties make a connection request with a provider via extranet, the system now sends a notification email to the provider again.

  • Content API Incorrect Invalid value. The given data is invalid. - Policy rule is missing required fields HTTP 400 errors (ACI-4233)

    The system no longer returns incorrect error when using the POST OTA_HotelDescriptiveContentNotif endpoint.

5 August 2025

In this release cycle, we're excited to announce a new feature to the Licenses API that enables uploading a license file and a new label element. In addition, we want to bring your attention to two bug fixes. Read on for more information.

What is new?

  • [Licences API] New feature and element for the Licenses API

    We've added a new feature to the Licenses API that allows you to upload a license file, which is required by certain regions and countries. This functionality accepts a single file per request and supports .jpg, .jpeg, .png, or .pdf formats.

    A new element label is now available in the GET /licenses/rules endpoint. The label element provides a short, human-readable description for a license variant.

    To learn more, see the Licences API documentation.

What was fixed?

  • Property API Incorrect error French tax details are incomplete but mandatory for property's location (ACI-4177)

    The system no longer incorrectly returns the French tax details are incomplete but mandatory for property's location error when using the POST /properties/{propertyId}/status endpoint.

  • [Provider Portal] "Something went wrong" error when adding a new endpoint in the Notification Service Settings (ACI-4196)

    The Provider Portal now correctly sets a new endpoint in the Notification Service Settings again.

22 July 2025

In this release cycle, we would like to inform you about the new version of the Messaging API. In addition, we want to bring your attention to two bug fixes. Read on for more information.

What is new?

Booking.com has released a new version 1.2 of the Messaging API. The new version supports the following:

  • self-service request messages (special and structured requests)
  • new field message_type for all messages
  • new attributes object
  • guest name in metadata.name

For more information on the v1.2 changes, see version 1.2.

What was fixed?

  • [Rates and Availability API] Incorrect 403 error (ACI-4131)

    The system no longer incorrectly returns 403 error when using the Rates and Availability API.

  • Content API Incorrect 500 error (ACI-4197)

    The system no longer returns internal server error when calling the POST OTA_HotelDescriptiveContentNotif endpoint.

8 July 2025

In this release cycle, we would like to remind you about the deprecation of the credentials-based authentication scheme. In addition, we want to bring your attention to four bug fixes. Read on for more information.

What is going to change?

What was fixed?

  • Reservations API Incorrect commission amount (ACI-4145)

    The system now shows the correct commission amount in reservation messages again.

  • Promotions API Internal server errors (ACI-4165)

    The system no longer returns internal server error when calling the POST xml/getpromotions endpoint.

  • Reservations API Missing reservation messages (ACI-4174)

    The system now returns all reservation messages again when using the Reservations API.

  • Content API: Incorrect Subroom information (ACI-4178)

    The system now correctly returns the subroom information when calling the POST OTA_HotelDescriptiveInfo endpoint.

Previous page
Next page