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.

29 April 2025

In this release cycle, we would like to introduce a new set of features that can help you use the Content API (OTA_HotelDescriptiveContentNotif or HDCN endpoint) together with the modernised Property APIs. In addition, we would like to notify you about the reply score deprecation and sunsetting from the Property Scores API. Read on for more information.

What is new?

• Property API: New features to protect Property API data from HDCN updates

  The Content API's default overlay behavior treats missing data in updates as intentional omissions. This can accidentally remove data you've set through some of the Property management APIs if you don't include the same data in subsequent HDCN requests.

  To prevent this issue and maintain your new API's data even when it's not included in HDCN updates, Booking.com is introducing multiple features that follow the naming convention: domain_update_lock_<api_name>.

  Note: These features are only applicable for providers who have implemented the new modernised Property APIs and wish to continue using the HDCN endpoint simultaneously.

  For more information about these features, see the Using Property management APIs along with Content API section in the Migration guide.

What is going to change?

• [Property Scores API]: Reply Score deprecation and sunsetting

  Booking.com is going to deprecate and sunset the reply score from the Property Scores API on April 30, 2025 and July 2, 2025 respectively.

  For more information on the deprecation and sunsetting, see Reply Score in Property Scores API.

15 April 2025

In this release cycle, we want to talk about a new content related to Payments Clarity Package v2 and an update on new error codes of the derivedprices endpoint. In addition, we want to bring your attention to three bug fixes. Read on for more information.

What is new?

• Reservations API Documentation Update: Payments Clarity Package v2

  The documentation for the Payments Clarity Package v2 (payment_clarity_package_v2) feature has been relocated from the Migration guide to their respective sections in the Reservations API documentation. The Reservations API documentation now includes changes to how payments and withheld tax data is shared in the API response when using this feature.

  For more information on the Payments Clarity Package v2 (payment_clarity_package_v2):

  • When using the OTA schema: See Include Payments Clarity Package v2 (OTA)
  • When using the B.XML schema: See Include Payments Clarity Package v2 (B.XML)

  For detailed implementation guides:

  • Implementing Payments Clarity Package V2 using OTA

  • Implementing Payments Clarity Package V2 using B.XML

What has changed?

• [Documentation] Updated new error codes for the derivedprices endpoint v1.1

  We've added new error codes for the derivedprices endpoint v1.1 documentation with more detailed explanatory notes to improve troubleshooting. To learn more, see the New error codes on v1.1.

What was fixed?

• [Provider Portal] Users cannot search reservations in the Reservation Timeline (ACI-4101)

  Provider Portal users can now search reservations in the Reservation Timeline again.

• [Provider Portal] Incorrect pricing type set via Provider Portal (ACI-4094)

  The Provider Portal now set the OBP pricing type for properties correctly again.

• [Provider Portal] Incorrect date of events displayed in the Reservation Timeline (ACI-4070)

  The Reservation Timeline now shows the correct date of events again.

1 April 2025

In this release cycle, we do not have any major updates. However, we want to bring your attention to a bug fix. Read on for more information.

What was fixed?

• [Provider Portal] Users cannot update the secondary contacts in Company Settings (ACI-4080)

  Provider Portal users can now update secondary contacts in Company Settings again.

18 March 2025

In this release cycle, we have no bug fixes to report. However, we are excited to announce that the Property API now supports adding land registration number! Read on for more information.

What is new?

• Property Management New feature supporting land_registration_numbers

  The Property Settings API now enables you to update the land registration number (land_registration_numbers) for properties located in EU countries via the property-api settings endpoint.

  To learn more, see Managing property settings.

4 March 2025

In this release cycle, we want to talk about new content in the Going Live page. In addition, we want to bring your attention to two bug fixes. Read on for more information.

What has changed?

• [Documentation] Updated Go live requirements

  We've updated the go live and technical requirements covering the following additional APIs:

  • Charges API
    
  • Connections API
    
  • Facilities API
    
  • Flexible children rates
    
  • Key Collection API
    
  • Property Details API
    
  • Property Profile API
    
  • Property Settings API
    
  • Property Status
    
  • Request to Book API
    
  • Rooms API
    
  • Value Adds Solution
    

  Take a look at the Going Live page.

What was fixed?

• Content API Incorrect error Cannot check availability. Please retry (ACI-4062)

  The system no longer incorrectly returns the error Cannot check availability. Please retry when calling the POST ota/OTA_HotelSummaryNotif endpoint.

• Extranet Error encountered by properties when requesting connection via Quick Connect (ACI-4061)

  Properties no longer see the error message when requesting connection using Quick Connect.

18 Feburary 2025

In this release cycle, we have no bug fixes to report. However, we're excited to announce the launch of the 2025 Connectivity product roadmap! Read on for more information.

What is new?

• 2025 Connectivity Product Roadmap

  The 2025 Connectivity product roadmap is now live! As part of our ongoing commitment to improving our products, we are thrilled to share our roadmap outlining the new initiatives and updates we plan to implement throughout the year.

  To learn more about the roadmap, please visit the Public Roadmap.

  In addition, you can download the roadmap in PDF format from the Resource section of the Connectivity Hub.

4 Feburary 2025

In this release cycle, we are excited to announce the release of the Rooms API. In addition, we want to inform you about a bug fix. Read on for more information.

What is new?

• [Rooms API] New API with multiple endpoints

  This API enables you to retrieve the current room details for a property and add or update room information. In addition, you can retrieve a full list of room types and the available room names supported by the Rooms API.

  To learn more, see the Rooms API documentation.

What was fixed?

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

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

21 January 2025

In this release cycle, we did not have any bug fixes. However, we would like to notify you about the sustainability facilities deprecation and sunsetting retroactively. Read on for more information.

What has changed?

• Content API Retroactive notice to the sustainability facilities deprecation and sunsetting

  Booking.com has deprecated and sunsetted the sustainability facilities on October 11, 2024 and December 13, 2024 respectively.

  For more information on the deprecation and sunsetting, see Sustainability Practices as Facilities.

07 January 2025

Happy new year! In this release cycle, we do not have any major updates. However, we want to bring your attention to a few bug fixes. Read on for more information.

What was fixed?

• Reservations API Reservations not returned when sending requests too frequently (ACI-3954)

  The system returns all reservation messages when calling the API with no less than 20 seconds in between requests. Sending requests with less than 20-second gaps will lead to race condition in our system.

• [Reporting API] Internal server errors (ACI-3963)

  The system no longer returns an error with error code 500 when reporting guest misconduct.

• [Contacts API] Inconsistent case returned for country_code (ACI-4002)

  Booking.com no longer returns country_code in lower case when calling the GET /properties/{propertyID}/contacts endpoint.

• Photo API Internal server errors (ACI-4010)

  The system no longer responds with error code 500 when calling the DELETE /properties/{property_id}/photos/{photo_id}` endpoint.