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.

29 October 2024

In this release cycle, we are excited to announce the launch of a new token-based authentication process to our APIs. In addition, we want to bring your attention to a few bug fixes. Read on for more information.

What is new?

  • New machine account token-based authentication

    We are introducing a new token-based authentication process for accessing Booking.com Connectivity APIs. Connectivity partners are required to migrate all machine accounts from basic auth to the new token-based authentication by December 2025.

    You can find more details on the New machine account token-based authentication article.

What was fixed?

  • [Provider Portal] Users not receiving two-factor authentication codes (ACI-3917)

    Provider portal users now receive an SMS message or a call back when requesting a two-factor authentication code.

  • Content API Incorrect error Invalid value. Failed to create charge definition for hotel {hotelID} (ACI-3958)

    The system no longer incorrectly returns the error Invalid value. Failed to create charge definition for hotel {hotelID} when sending overlay updates via the POST OTA_HotelDescriptiveContentNotif endpoint.

  • Content API Missing UniqueID element (ACI-3959)

    The system now returns the UniqueID element again when creating a new property via the POST OTA_HotelDescriptiveContentNotif endpoint.

15 October 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.

  • Messaging API Missing messages (ACI-3926)

    The system now returns all messages again when calling the GET /properties/{property_id}/conversations/{conversation_id} endpoint.

  • Reservations API Missing virtual credit card activation date (ACI-3918)

    The system now shows the activation date of virtual credit card in reservation messages again.

01 October 2024 (updated 03 Oct.)

In this release, we want to talk about the release of Value adds! In addition, we want to bring your attention to a bug fix. Read on for more information.

What is new?

What was fixed?

  • Reservations API Withheld French city tax incorrectly included in HotelView total amount for bookings with VCC payment solution (ACI-3880)

    The system now excludes the amount of withheld French city tax in the HotelViewtotal amount when using the feature Payments Clarity Package V2 (payment_clarity_package_v2).

17 September 2024

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

03 September 2024

In this release, we would like to highlight an update to the Reservations API documentation. In addition, we want to inform you about a bug fix. Read on for more information.

What has changed?

  • [Reservations API][Documentation] Updates on features res_cancel_policies and res_cancel_policy_details (ACI-3847)

    The documentation now covers how cancellation grace period information is shared when using the features: res_cancel_policies and res_cancel_policy_details.

    To learn more, see Processing reservations using OTA and Processing reservations using B.XML.

What was fixed?

  • Property API Incorrect property settings error (ACI-3906)

    The system no longer returns the Property location is not eligible for French City Tax error incorrectly when calling the POST property-api/properties/{{property_id}}/settings endpoint.

20 August 2024

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

What was fixed?

  • Content API HTTP code 404 error (ACI-3877)

    The system no longer incorrectly returns 404 errors when calling the POST /property-profile/properties/{property id}/hotelier_messages endpoint.

  • Content API Incorrect duplicate cancellation policy error (ACI-3851)

    The system no longer incorrectly returns duplicate cancellation policy errors when sending overlay updates via the POST OTA_HotelDescriptiveContentNotif endpoint.

  • Request to Book API Returns booking requests at the machine-account level

    Request to Book API now returns booking requests at the machine-account level. Previously, it was done at the provider level.

6 August 2024

In this release cycle, we are excited to announce the launch of a Postman collection for Room Type and Rate Plan Management (RRM) APIs. In addition, we have the change in promotion statistic retention and two bug fixes to tell you about. Read on for more information.

What's new?

  • Room Type and Rate Plan Management API: Launching Postman Collection

    We are excited to announce the launch of a Postman collection for Room Type and Rate Plan Management (RRM) APIs. This collection allows Providers to perform various actions supported by the RRM API by specifying their property ID and authentication credentials.

    For more information on downloading and using the collection, please see Using Postman Collection for RRM APIs.

What is going to change?

  • Promotions API: Promotion statistic retention

    Booking.com has made the decision to retain promotion statistics for 12 months, effective on September 15, 2024. The getpromotions endpoint will thereby return promotion statistics up to the past 12 months.

What was fixed?

  • [Rates and Availability API] HTTP code 403 error (ACI-3876)

    The system no longer returns 403 errors when sending availability updates.

  • Reservations API Missing guest count information (ACI-3871)

    The system now shows the guest count information in reservation messages again.

23 July 2024

In this release cycle, we are excited to announce the release of the Facilities API and a new endpoint in the Property API! Additionally, we have addressed several bug fixes. Read on for more information.

What's new?

  • Facilities API: New API with multiple endpoints

    Using the Facilities API, you can:

    • Retrieve facilities metadata
    • Retrieve property and room-level facilities details
    • Add, modify or delete property and room level facilities details

    To learn more, see the Facilities API documentation.

  • Property API: New Settings endpoint

    Using the settings endpoint, you can create and update certain property details including:

    • Quiet hours or curfew timing
    • Long stay details
    • Damage policy
    • Pets policy
    • Children policy and so on

    To learn more, see the Property API documentation.

What was fixed?

  • Content API: Incorrect prepayment policy (ACI-3866)

    The system now correctly applies the prepayment policy when sending overlay updates via the POST OTA_HotelDescriptiveContentNotif endpoint.

  • Content API: Incorrect cancellation policy (ACI-3865)

    The system now correctly applies the cancellation policy when creating a property via the POST OTA_HotelDescriptiveContentNotif endpoint.

  • Reservations API: Incorrect cancel_penalties node elements order (ACI-3863)

    The system now correctly returns the child elements of cancel_penalties node in the reservation messages, when enabling both res_cancel_policies and res_cancel_policy_details features. For more information about the features, see the Feature Management page in the provider portal.

  • Messaging API: HTTP code 404 error (ACI-3856)

    The system no longer returns a 404 error when sending messages via the POST /properties/{property_id}/conversations/{conversation_id} endpoint.

  • Reservations API: Incorrect city tax amount (ACI-3842)

    The system now correctly returns the city tax amount in the reservation messages.

  • Room type and rate plan management API: Incorrect room type names (ACI-3720)

    The system now correctly returns the room type names when calling the POST xml/rooms endpoint.

09 July 2024

In this release cycle, we want to talk about the release of the Request to Book API! In addition, we want to bring a bug fix to your attention. Read on for more information.

What's new?

  • Request to Book API New Request to Book API

    Using our Request to Book API, you can take the following actions:

    • Enable eligible home properties to work with Booking.com on the Request to Book model
    • Retrieve booking requests made by guests
    • Update a booking request

    To learn more about the Request to Book booking model and the Request to Book API, see the Request to Book API documentation.

What was fixed?

  • [Provider Portal] Missing "Disconnected Hotels (with csv)" email reports (ACI-3811)

    Providers can receive the email report "Disconnected Hotels (with csv)" again.