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 has changed?
    Refers to minor changes or updates to existing API products or features.
  • What was fixed?
    Refers to bug fixes.

21 Mar 2023

In this release cycle, we want to talk about the change related to the attribute MaxChildOccupancy. In addition, we want to bring your attention to a bug fix related to guest count. Read on for more information.

What is new?

  • Content API [Room type and rate plan management API] Changes to the MaxChildOccupancy attribute usage

    We have changed the way you can specify child occupancy settings for a room type or a unit using the OTA_HotelInvNotif endpoint on 20 March 2023. In addition, we have introduced an additional attribute MaxChildPayableOccupancy under TPA_Extensions to capture the number of children that are eligible for the children rate. Starting from 20 March 2023, the value in the MaxChildOccupancy attribute no longer reflects the eligibility for children rates and instead specifies the physical child occupancy limit of the room type or unit.

    For more information on the change, see Changes to MaxChildOccupancy attribute usage.

What was fixed?

  • Reservations API Missing guest count information for children aged 0 (ACI-3377)

    The system now shows the guest count information of children aged 0 in reservation messages again when the feature Include reservation-level guest count (childcount) is enabled.

7 Mar 2023

In this release cycle, we would like to remind you about the upcoming deprecation and sunsetting of the functionality of specifying nearby attractions and property's relative position. We would also like to remind you about the changes to the MaxChildOccupancy attribute usage starting from 20 March 2023. In addition, we have fixed a guest count related bug to tell you about. Read on for more information.

What is going to change?

  • Content API [Room type and rate plan management API] Changes to the MaxChildOccupancy attribute usage

    We plan to change the way you can specify child occupancy settings for a room type or a unit using the OTA_HotelInvNotif endpoint from 20 March 2023. In addition, we plan to introduce an additional attribute MaxChildPayableOccupancy under TPA_Extensions to capture the number of children that are eligible for the children rate. Starting from 20 March 2023, the value in the MaxChildOccupancy attribute no longer reflects the eligibility for children rates and instead specifies the physical child occupancy limit of the room type or unit.

    For more information on the change, see Changes to MaxChildOccupancy attribute usage.

  • Content API Specifying attractions and property's relative position information in Content API

    Booking.com is deprecating the functionality of specifying nearby attractions and property's relative position information using AreaInfo and HotelInfo > RelativePositions as of March 15, 2023. Booking.com automatically generates the nearby places and the property's relative position information. The functionality will sunset on June 30, 2023.

    With this change, the OTA_HotelDescriptiveContentNotif and OTA_HotelDescriptiveInfo endpoints would soon stop supporting the usage of AreaInfo and HotelInfo > RelativePositions elements.

    For more information on the deprecation guidelines, see Property nearby places and relative position information in Content API.

  • Content API Use the OTA_HotelDescriptiveInfo endpoint to also view property details for properties in pending connection status.

    You can use the OTA_HotelDescriptiveInfo endpoint on properties whose connection is in pending status with the property among other states. For more information on how to check the connection status with the property, see Retrieve property attributes.

What was fixed?

  • Reservations API Incorrect room-level guest counts (ACI-3299)

    The system is no longer incorrectly showing the total number of guests as room-level guest counts in reservation messages.

21 Feb 2023

In this release cycle, we want to talk about the upcoming change related to the attribute MaxChildOccupancy. In addition, we have a bug fix to tell you about. Read on for more information:

What is going to change?

  • Content API [Room type and rate plan management API] Changes to the MaxChildOccupancy attribute usage

    We plan to change the way you can specify child occupancy settings for a room type or a unit using the OTA_HotelInvNotif endpoint from 20 March 2023. In addition, we plan to introduce an additional attribute MaxChildPayableOccupancy under TPA_Extensions to capture the number of children that are eligible for the children rate. Starting from 20 March 2023, the value in the MaxChildOccupancy attribute no longer reflects the eligibility for children rates and instead specifies the physical child occupancy limit of the room type or unit.

    For more information on the change, see Changes to MaxChildOccupancy attribute usage.

  • Content API Specifying attractions and property's relative position information in Content API

    Booking.com is deprecating the functionality of specifying nearby attractions and property's relative position information using AreaInfo and HotelInfo > RelativePositions as of March 15, 2023. Booking.com automatically generates the nearby places and the property's relative position information. The functionality will sunset on June 30, 2023.

    With this change, the OTA_HotelDescriptiveContentNotif and OTA_HotelDescriptiveInfo endpoints would soon stop supporting the usage of AreaInfo and HotelInfo > RelativePositions elements.

    For more information on the deprecation guidelines, see Property nearby places and relative position information in Content API.

What was fixed?

  • [Office] Incorrect information on the Daily Fallback Summary emails (ACI-3364)

    Booking.com now sends correct fallback information again in the Daily Fallback Summary email.

7 Feb 2023

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 Missing RoomRate element (ACI-3322)

    Booking.com now shows RoomRate element again in reservation messages.

  • Reservations API Unretrieved XML messages treated as retrieved (ACI-3361)

    The system now treats unretrieved XML messages as fallbacks and sends fallback emails to the property again.

24 Jan 2023

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

10 Jan 2023

Happy new year! In this release cycle, we want to talk about the upcoming change to our network traffic management. In addition, we have a bug fix to tell you about. Read on for more information:

What is going to change?

  • Introducing AWS Cloudfront for network traffic management

    We will adopt AWS Cloudfront for network traffic management from Feb 1, 2023. As a result, our IP addresses (which have been static to date) will no longer work as a way to reach Connectivity APIs. Connectivity domain names will instead automatically resolve to various IPs owned by Amazon. If you are currently applying any IP-whitelisting, this will need to be removed as soon as possible. It is critical to reach us using DNS lookup according to best practices.

    You can validate and verify that no unusual DNS setup or static IPs exist in your system with the following new domain names. These two domains are already working in our new AWS Cloudfront setup:

    • supply-xml-migration.booking.com
    • secure-supply-xml-migration.booking.com

    For more information on the change, see Introducing AWS Cloudfront for network traffic management.

What was fixed?

  • [Rates and Availability API] 503 errors caused by service mesh network issue (ACI-3340)

    Booking.com no longer returns 503 errors when sending availability updates.

Is this page helpful?    Yes   |    No