Home

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.

19 March 2024

In this release cycle, we would like to talk about four new Market Insights API endpoints! We also want to share with you our new Going Live page in the documentation. In addition, we've fixed a Reservations API bug. Read on for more information.

What's new?

  • [Market Insights API] New Market Insights API endpoints

    We've added the following new endpoints that capture property performance insights:

    • The pace_report_data endpoint enables you to keep track of properties' future reservations, and compare the performance to previous years. You can also check how your properties perform when comparing to similar properties in the same area, competitive set or the market in general.
    • The sales_statistics_report_data endpoint provides reservations from guests who have booked or stayed at the property. You can compare the results with values from the previous year. You can compare your properties' past performance with similar properties in the same area, competitive set or the market in general. You can also specify which bookings to take into consideration.
    • The booker_insights_data endpoint enables you to understand which countries your guests are booking from. The API uses the reservations based on the date of booking minus cancellations.
    • The book_window_data endpoint enables you to retrieve booking window information for the target property's region based on historical data. The API uses the reservations based on the date of booking minus cancellations.

    To learn more, see the Market insights API documentation.

  • [Documentation] New Going Live page

    We've added a new Going Live page which outlines the technical and compliance requirements for each Booking.com API and the API elements before going live.

    Take a look at the Going Live page.

What was fixed?

  • Reservations API Missing commission information (ACI-3729)

    Booking.com now returns commission information in reservation messages again when pulling via the GET OTA_HotelResNotif and the GET OTA_HotelResModifyNotif endpoints.

05 March 2024

In this release cycle, we want to talk about the release of the Connections API! We would also like to introduce you to the version 1.1 of the los_pricing endpoint. In addition, we've added a new FAQ page which covers Rates and Availability API related topics. Read on for more information.

What's new?

  • Connections API

    This API enables you to take the following key connection management actions:

    • accept or reject connection requests
    • deactivate an active connection
    • retrieve active connections
    • retrieve pending connection requests
    • check the status of connections
    • retrieve disconnection summaries

    To learn more, see the Connections API documentation.

  • [Documentation] [Rates and Availability API] New Rates and Availability API FAQ

    We have added a new FAQ section which covers Rates and Availability API related frequently asked questions.

    Take a look at the FAQ.

What is going to change?

  • [Rates and Availability API] New version of the los_pricing endpoint is now live!

    Booking.com has released a new version 1.1 of the los_pricing endpoint. For more information on the v1.1 changes, see the Migration guide.

    We plan to deprecate the old version 1.0 by April 1, 2024, and sunset it on June 10, 2024.

    You can find more details on the Deprecation and sunsetting page.

20 February 2024

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

What was fixed?

  • Reservations API Incorrect commission amount (ACI-3658)

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

  • [Messaging API] Error Unable to identify proxy for host (ACI-3726)

    Booking.com no longer returns the Unable to identify proxy for host error when calling the GET /properties/{property_id}/conversations/{conversation_id} and the GET /messages/latest request requests.

06 February 2024

In this release cycle, we want to share about one bug fix in the Room type and rate plan management API and the launch of the Payments Clarity Package V2 that's coming soon.

What's to come?

  • Reservations API Launching Payments Clarity Package V2 soon

    We are rolling out changes to the way the Reservations API calculates and displays the breakdown of the total price for each reservation booking using a new feature: _Payments Clarity Package V2 (payment_clarity_package_v2). For more information, see the Migration guide.

What was fixed?

  • Room type and rate plan management API No changes made despite success response (ACI-3711)

    The issue is resolved. You can continue to use the OTA_HotelProductNotif endpoint to create roomrates.

23 January 2024

In this release cycle, we want to talk about new content in the the Reservation API FAQ. We have also added more error codes for the availability v1.1 endpoints. In addition, we want to bring your attention to a bug fix related to the Connectivity Errors Extranet page. Read on for more information.

What is new?

  • Documentation New content in the Reservations API FAQ

    We've added the following new questions and their answers:
    - Why does an XML message show the wrong number of guests?
    - Are bookers allowed to specify which guests go into which rooms for multi-room reservations?
    - How can I see the ages of children in a reservation?
    - What are the reservation details I need to show to properties in my system?

    Take a look at the General information and the Testing the Reservations API FAQ pages.

  • [Documentation] [Rates and Availability API] New errors and warnings of v1.1 endpoints

    The documentation now shows more error codes and warnings for the following endpoints:
    - new error codes and warnings on v1.1 of OTA_HotelRateAmountNotif - new error codes on v1.1 of OTA_HotelAvailNotif - new error codes and warning on v1.1 of B.XML availability

    You can find more details in the Migration guide.

What was fixed?

  • Rates and Availability API Outdated errors and warnings in the Connectivity Errors Extranet page (ACI-3676)

    The Connectivity Errors Extranet page no longer shows outdated availability errors and warnings that occurred more than 30 days in the past.

09 January 2024

Happy new year! In this release cycle, we are excited to announce that we now offer multiple new troubleshooting pages in the documentation and a new Connectivity API Status page in the Provider Portal. We would also like to remind you about the upcoming deprecation and sunsetting of a few v1.0 endpoints. In addition, we want to bring multiple bug fixes to your attention. Read on for more information.

What is new?

What is going to change?

[Rates and Availability API] Upcoming sunsetting dates of version 1.0 of the B.XML availability and roomrates endpoints

The sunsetting of both B.XML availability and B.XML roomrates version 1.0 endpoints will take place on Jan 15, 2024. After Jan 15, 2024, you will not have access to version 1.0 and the traffic will be automatically transitioned to version 1.1.

Please ensure that you migrate to the new version 1.1. of both endpoints before January 15, 2024. If you have already moved to version 1.1, there is no impact. You can continue using the new version.

You can find more details on the Deprecation and sunsetting page.

[Rates and Availability API] Upcoming deprecation and sunsetting dates of version 1.0 of the OTA_HotelAvailNotif and OTA_HotelRateAmountNotif endpoints

The OTA_HotelAvailNotif and OTA_HotelRateAmountNotif version 1.0 endpoints will be deprecated on Jan 31, 2024. The sunsettnig will follow and happen on Feb 14, 2024.

Please ensure that you test and migrate to the new version 1.1. of both endpoints before Jan 31, 2024. If you've already moved to version 1.1, there is no impact. You can continue using the new version.

For more information, see the Deprecation and sunsetting page.

What was fixed?

  • Reservations API Missing cancellation messages and fallback emails (ACI-3661)

    The system now enqueues cancellation messages again when calling the OTA_HotelResModifyNotif endpoint.

  • [Rates and Availability API][Documentation] Failed price and restriction updates for child rate returned with 200 response(ACI-3677)

    The documentation now reflects a new behaviour of the BXML availability version 1.1 endpoint. When setting prices and restrictions for a child rate which follows restrictions or prices of a parent rate, the API now returns a partial success response with an error message.

    You can find more details of the new behavior on the Migration guide.

  • [Messaging API] Unsupported Structured requests returned (ACI-3678)

    The system no longer returns structured requests via the GET /messages/latest endpoint.

  • [Rates and Availability API] LOS updates returning Transaction aborted due to a deadlock found error (ACI-3685)

    Booking.com now processes LOS updates again, and no longer returns the error.

  • [Market insights API] 403 error (ACI-3689)

    The system no longer incorrectly returns 403 error when sending the GET /market-insights-api/properties/{property_id}/area_demand_data request.

Is this page helpful?    Yes   |    No