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.

28 June 2022

In this release cycle, we have added a new feature for the Photo API. In addition, we would like to share some details about few bug fixes. Read on for more information:

What is new?

  • [Photo API] New feature

    The Photo API now enables you to specify whether the photos in the property-level photo gallery are shown to the guests in the order optimised using Booking.com's machine learning algorithm (Smart ordering) or in the order set by you. To learn more, see the Photo API documentation.

What was fixed?

  • [Content API] Incorrect error for policy code 569 (ACI-2660)

    The system no longer returns an error when you set properties' policies with policy code 569 via the OTA_HotelDescriptiveContentNotif endpoint.

  • [Content API] [Room type and rate plan management API] Missing warning message for the OTA_HotelProductNotif endpoint (ACI-2946)

    Booking.com now returns warning messages when sending updates on roomrates including those which are inactive.

  • [Promotions API] [Documentation] Active promotions with stay dates in the past (ACI-3022)

    The documentation now states that promotions with stay dates in the past are active promotions and they will be returned when calling the getpromotions endpoint. To learn more, see the Promotions API documentation.

  • [Messaging API] [Documentation] Incorrect participant_type (ACI-3084)

    The documentation now shows the correct participant_type "property" in the response body example of the GET /messages/latest request. Take a look at the Messaging API documentation.

14 June 2022

In this release cycle we bring a bug fix to your attention. Read on for more information.

What was fixed?

  • [Messaging API] Missing messages (ACI-3013)

    Booking.com now returns all messages when calling the GET /properties/{property_id}/conversations/{conversation_id} endpoint.

31 May 2022

In this release cycle, we do not have any major changes to share. However, we want to bring your attention to the following bug fixes.

What was fixed?

  • [Messaging API] Internal server errors (ACI-2704)

    The system no longer returns an error with error code 500 when calling the following endpoints:
    - GET /properties/{property_id}/conversations
    - GET /properties/{property_id}/conversations/{conversation_id}
    - POST /properties/{property_id}/conversations/{conversation_id}/attachment_chunks

  • [Reservations API] Missing cancellation policy timeline (ACI-3042)

    Booking.com now returns the cancellation policy timeline of bookings when the feature res_cancel_policy_details is enabled.

  • [Messaging API] Incorrect 404 errors (ACI-3063)

    The system no longer returns incorrect 404 error when calling the GET /properties/{property_id}/conversations/type/{conversation_type} endpoint.

17 May 2022

We fixed another round of bugs, including issues on the Connectivity Provider page of the extranet. Read on for more information.

What was fixed?

  • [Extranet] Unexpected error when accessing the Connectivity Provider page on the extranet (ACI-2744)

    Properties can now access the Connectivity Provider page again on the extranet.

  • [Messaging API] Incorrect 400 and 500 errors (ACI-2801)

    The system no longer returns an error with error codes 400 or 500 when calling the POST /properties/{property_id}/conversations/{conversation_id}/attachment_chunks endpoint.

  • [Reservations API] Missing virtual credit card on confirmations of Smart Flex reservations (ACI-2991)

    Booking.com now returns virtual credit card details in the reservation messages of Smart Flex reservations.

  • [Messaging API] Missing attachment (ACI-3016)

    When posting a message with an attachment to a conversation (using the POST /properties/{property_id}/conversations/{conversation_id} endpoint), the system sends the attachment to the guests and also shows the attachment on the extranet.

  • [Provider Portal] Error "please try again later" (ACI-3033)

    The system no longer shows the error when accessing the Reservation Timeline on the Provider Portal.

  • [Licences API] Incorrect licence requirements (ACI-3035)

    Booking.com no longer shows incorrect licence requirements as not required for properties that have a mandatory regional licence requirement when calling the GET /rules/properties/{property_id} endpoint.

  • [Extranet] Incorrect connection status during the Quick Connect process (ACI-3039)

    When connection requests made by properties are accepted, the system now shows correct connection status again. In addition, properties can access the Connectivity Provider page on the extranet again.

03 May 2022

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

What was fixed?

  • [Messaging API] Incorrect element names (ACI-3005)

    Booking.com now returns the following correct element names when calling the GET /messages/latest endpoint:
    - conversation_id
    - conversation_type
    - conversation_reference

  • [Provider Portal] No values in multiple reports (ACI-3020)

    The following reports on the Provider portal now show the correct data again:
    - Reservation Retrieval Times
    - Bookable until History
    - API Error

19 April 2022

In this release cycle, we bring a few bug fixes to your attention. In addition, we would like to remind you about the solutions that will be sunset on 20 April 2022.

What is new?

  • Sunsetting few solutions

    The following deprecated solutions will be sunset starting 20 April 2022:
    - Hotelier message
    - Licences via Content API and
    - Children policies via Content API

These solutions will be unusable starting from the sunset date. The APIs will return an error response when used. For more information, see the deprecation and sunsetting documentation.

What was fixed?

  • [Content API] [Documentation] Attribute LanguageCode (ACI-2593)

    The documentation now states that you can specify the language of choice in which the property wants to view and retrieve their Booking.com extranet content and communication by using the LanguageCode attribute when calling the OTA_HotelDescriptiveContentNotif and OTA_HotelDescriptiveInfo endpoint respectively. To learn more, see the HotelDescriptiveContent documentation.

  • [Messaging API] Incorrect element names returned on response (ACI-3008)

    Booking.com now returns the correct element names message_id and participant_id when calling the POST /properties/{property_id}/conversations/{conversation_id} and GET /messages/latest endpoints.

05 April 2022

In this release cycle, we would like to bring your attention to solutions that were sunset. In addition, we have also included details of multiple bug fixes. Read on for more information.

What is new?

  • Sunset few solutions

    The following deprecated solutions were sunset as of April 01, 2022:
    - SPO flow
    - Photos via Content API and
    - One past stay
    These solutions are unusable since the sunset date. The APIs now return an error response when used. For more information, see the deprecation and sunsetting documentation.

What was fixed?

  • [Promotion API] [Documentation] Setting value 0 for last_minute (ACI-2863)

    The documentation now states that when last_minute value is set to 0, irrespective of the value set in unit, the API creates a last minimum promotion effective 3 days and fewer. To learn more, see the Promotions API documentation.

  • [Content API] [Documentation] Incorrect Charge Type codes (ACI-2960)

    The documentation now lists all charge type codes that are supported on Booking.com. Take a look at the charge type codes.

  • [Office] Missing contact email address and phone number on connection request emails (ACI-2973)

    You can receive the email address and phone number of the property's contact person on the connection request emails again.

  • [Reservations API] Missing OTA response token on cancellation messages of multiple-room bookings (ACI-2980)

    Booking.com now returns the OTA hotel reservation response token on the cancellation messages of multiple-room bookings when the feature ota_res_response_token is enabled.

22 March 2022

In this release cycle we want to bring your attention to multiple bug fixes. In addition, we want to remind you that a few solutions are going to be sunset soon in April. For more information on the affected solutions, see the deprecation and sunsetting documentation.

What was fixed?

  • [Reservations API] Wrong mealplan information shared in Russian language (ACI-2697)

    The system now correctly shows breakfast as "Завтрак" instead of "завтрака" in reservation messages.

  • [Reservations API] Incorrect mealplan information (ACI-2715)

    Booking.com now returns correct mealplan information in reservation messages under mealplan and info.

  • [Messaging API] Incorrect 400 and 500 errors (ACI-2730)

    The system no longer returns an error with error codes 400 or 500 when calling the GET /properties/{property_id}/conversation endpoint.

  • [Photo API] Error "You cannot remove the main_photo from gallery for Open property. Specify a different main_photo first" (ACI-2792)

    Booking.com now returns a PHOTO_NOT_ENABLED error when the call to set a new main photo update was successful but the system hasn't enabled the photo yet. This error message can help providers from accidentally deleting a photo that was previously set as the main photo while the newly set main photo is yet to get activated.

  • [Reservations API] Missing flag Booker_is_genius (ACI-2896)

    If a booking is made by a Booking.com Genius-level customer, the system now shows Booker_is_genius in the reservation message.

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

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

  • [Reservations API] Incorrect mealplan information in Japanese (ACI-2979)

    Booking.com no longer shows incorrect mealplan information in Japanese like "朝食を希望" in reservation messages for reservations that are booked without any mealplans.

  • [Content API] Error "Can't parse malformed XML" (ACI-2988)

    The system no longer returns an error when calling the OTA_HotelSummaryNotif endpoint for properties with license details.

08 March 2022

In this release cycle we did not have any bug fixes. However, we want to bring your attention to updates on the Photo API and Content API. Read on for more information.

What has changed?

  • [Photo API] Minimum photo size requirement

    We shared that the minimum requirement for photo quality is 300 by 300 pixels. For more information, see the minimum requirements for photo quality.

  • [Content API] Partial deprecation warnings

    When calling a partially deprecated endpoint, you can now find deprecation warnings in the or "warnings" array in the response body. Take a look at the deprecation and sunsetting documentation.

22 February 2022

This release includes bug fixes for the Messaging and Reservation APIs. Read on for more information.

What was fixed?

  • [Messaging API] Missing attachment (ACI-2641)

    When posting a message with an attachment to a conversation (using the POST /properties/{property_id}/conversations/{conversation_id} endpoint) the system sends the attachment to the guests and also shows the attachment on the extranet.

  • [Messaging API] Missing attachment_ids (ACI-2885)

    When uploading a large attachment in multiple smaller chunks using the POST /properties/{property_id}/conversations/{conversation_id}/attachment_chunks endpoint, the system also returns an attachment_id element.

  • [Reservations API] Missing dummy credit card details for last-minute reservations (ACI-2944)

    The Reservations API returns dummy credit card details for last-minute reservations with credit card exceptions. Note that the property must accept reservations with credit card exceptions and the provider must opt in the feature that returns dummy credit card details for such bookings. For more information on enabling the feature, speak to your accounts manager.

08 February 2022

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

25 January 2022

In this release we bring your attention to an update on the Online check-in API. In addition, we have a bug fix to tell you about. Read on for more information:

What has changed?

  • [Online check-in API] Lockbox codes access method and phone number of the primary guest were missing

    We enabled the API to support lockbox codes as a new access method. Besides that, the system now returns the phone number of the main guest when retrieving check-in requests via the GET /properties/{property_id}/checkins and the GET /checkins endpoints. Take a look at the Online Check-in API documentation.

What was fixed?

  • [Reviews API] 503 errors for the GET /review-api/latest/properties/{Hotel_ID}/reviews_iframe endpoint (ACI-2900)

    The system no longer returns 503 errors when retrieving the Guest Reviews iframe URL.

11 January 2022

Happy new year! In this release cycle Booking.com did not have any major releases. However, we want to bring your attention to multiple bug fixes.

What was fixed?

  • [Messaging API] Incorrect read_only access (ACI-2743)

    Booking.com now returns correct access when calling the GET /properties/{property_id}/conversations/type/{conversation_type} endpoint.

  • [Messaging API] Empty attachment_ids(ACI-2783)

    The system now returns the attachment_ids elements when calling the GET /messages/latest endpoint.

  • [Rates and Availability API] Incorrect pricing type set via Provider Portal (ACI-2841)

    You can now set the OBP pricing type for properties via the Provider Portal again.

  • [Reservations API] Room names and extra reservation information shown in English only (ACI-2848)

    The system now shows room names and extra reservation information on reservation messages in the properties' preferred language.

  • [Messaging API] Incorrect 403 and 404 errors (ACI-2853)

    Booking.com no longer returns 403 and 404 errors when calling the GET /properties/{property_id}/conversations/type/{conversation_type} endpoint.

  • [Content API] Additional bathroom set (ACI-2854]

    Booking.com no longer incorrectly sets extra bathroom when calling the OTA_HotelInvNotif endpoint.

  • [Reservations API] Room names and extra reservation information not shown in properties' preferred language (ACI-2860)

    Booking.com now shows room names and extra reservation information in reservation messages in properties' preferred language.

  • [Rates and Availability API] Incorrect pricing type set despite OBP being confirmed via connection request email (ACI-2878)

    You can now confirm OBP as the preferred pricing type for properties from within the connection request email.