Home

Changelog archive

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.

Q4 2023

12 December 2023

In this release cycle, we would like to remind you about the extension to the upcoming sunsetting dates of version 1.0 of the B.XML availability and the roomrates endpoints. In addition, we want to bring two bug fixes to your attention. Read on for more information.

What is going to change?

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

We are extending the sunsetting date for B.XML availability and B.XML roomrates v1.0 endpoints to Jan 15, 2024. This would give you more time to test and adopt the new versions of the API. After Jan 15, 2024, version 1.0 will not be available and providers would be automatically moved to version 1.1.

Please ensure that you test and 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.

What was fixed?

  • [Rates and Availability API] Incorrectly failed OBP updates in BXML v1.1 availability and v1.1 OTA_HotelRateAmountNotif endpoints (ACI-3651)

    The system no longer fails the complete OBP update when the defined occupancy for a part of the update exceeds the maximum occupancy of the room.

  • [Rates and Availability API] Incorrectly unprocessed updates in BXML v1.1 availability endpoint (ACI-3659)

    Booking.com now processes all partial updates correctly again.

28 November 2023 (updated 05 Dec.)

In this release cycle, we would like to share the extension to the upcoming sunsetting dates of version 1.0 of the B.XML availability and the roomrates endpoints. In addition, we want to bring three bug fixes to your attention. Read on for more information.

What is going to change?

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

We are extending the sunsetting date for B.XML availability and B.XML roomrates v1.0 endpoints to Jan 15, 2024. This would give you more time to test and adopt the new versions of the API. After Jan 15, 2024, version 1.0 will not be available and providers would be automatically moved to version 1.1.

Please ensure that you test and 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.

What was fixed?

  • [Reservations API] Reservations not available for retrieval due to missing data (ACI-3585)

    The system now correctly returns all reservations queued for delivery.

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

    The system no longer returns an error with error code 500 when calling the POST /properties/{property_id}/conversations/{conversation_id} endpoint. However, the security filters may still cause this in some corner cases.

  • [Reviews API] Duplicate reviews (ACI-3640)

    Booking.com no longer returns duplicate reviews when retrieving reviews by property ID.

14 November 2023

In this release cycle we did not have any bug fixes. However, we would like to inform you about the sunsetting of selling meal plans as addons via the POST OTA_HotelDescriptiveContentNotif endpoint. Read on for more information.

What is going to change?

  • [Content API] Deprecating selling meal plans as addons via the POST OTA_HotelDescriptiveContentNotif endpoint

    Booking.com has deprecated the meal plan add-on functionality as of December 2021. You could still enable or disable SellMealsThroughBooking before it becomes sunset via the API on December 21, 2023, but this has no longer an impact on properties selling the meal plan as add-ons on Booking.com. You can manage meal plans via the POST /ota/OTA_HotelProductNotif endpoint.

31 October 2023

In this release cycle, we would like to introduce you to the version 1.1 of the OTA_HotelRateAmountNotif endpoint. In addition, we have a few bug fixes to tell you about. Read on for more information.

What is new?

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

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

    We plan to deprecate the old version 1.0 by January 31, 2024, and sunset it on February 14, 2024.

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

What was fixed?

  • [Provider Portal] Missing SMS two-factor authentication codes (ACI-3593)

    Provider portal users now receive SMS messages again when requesting two-factor authentication codes.

  • [Content API] Connection incorrectly deactivated due to an outage (ACI-3608)

    We have reconnected the affected properties with their connectivity providers.

  • [Reservations API] Exclusive fees, taxes and charges incorrectly shown as inclusive (ACI-3627)

    Booking.com now correctly shows exclusive fees, taxes and charges in reservation messages again.

17 October 2023

In this release cycle, we would like to inform you about the updated deprecation and sunsetting dates of version 1.0 of the OTA_HotelAvailNotif endpoint. In addition, we have a few bug fixes to share with you. Read on for more information.

What is going to change?

  • [Rates and Availability API] Updated deprecation and sunsetting dates of version 1.0 of the OTA_HotelAvailNotif endpoint

    We plan to deprecate the old version 1.0 by January 31, 2024, and subsequently sunset it on February 14, 2024.

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

What was fixed?

  • [Content API][Documentation] Booking.com internal cancellation policy codes (ACI-3579)

    You can now find a list of internally assigned Booking.com cancellation policies. Booking.com assigns these policies for specific reservations of applicable properties. You cannot assign these policies via the POST OTA_HotelDescriptiveContentNotif endpoint.

    For more information, see the Booking.com internal cancellation policy codes.

  • [Rates and Availability API][Documentation] Availability update for past dates in version 1.1 via the OTA_HotelAvailNotif endpoint (ACI-3591)

    The documentation now states that you can update availability for periods in the future and up to one day in the past, in the Central European Time (CET) timezone. To learn more, see the Changes to the OTA_HotelAvailNotif endpoint.

  • [Rates and Availability API] Incorrect warning message WARN_DUPLICATE_DATES (ACI-3602)

    The system now correctly handles overlapping date availability updates in version 1.1 of the OTA_HotelAvailNotif endpoint.

  • [Reservations API] Incorrect payment details for non virtual credit card reservations (ACI-3607)

    Booking.com now shows the correct payment details again for non virtual credit card reservations.

3 October 2023

In this release cycle, we would like to introduce you to the version 1.1 of the OTA_HotelAvailNotif endpoint. In addition, we have multiple documentation changes and bug fixes to tell you about. Read on for more information.

What's new?

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

    Booking.com has released a new and improved version 1.1 of the OTA_HotelAvailNotif endpoint. You can now open or close a specific roomtype irrespective of whether there are multiple active roomrates assigned to the roomtype.

    For more information, see the Migration guide.

  • [Reservations API][Documentation] New Reservations API FAQ and tutorial

    We have added a new FAQ section which covers reservation related topics such as overbookings and payments. In addition, you can follow a new tutorial which guides you to make test reservations, including those with children.

    Take a look at the FAQ and the create a test reservation tutorial.

What was fixed?

  • [Reservations API][Documentation] Updated Smart Flex reservation related flags

    The documentation now shows the updated Smart Flex reservation flags smart_flex_reservation and smart_flex_replacement_reservation.

    For more information on the updates, take a look at the following documentation pages:
    - Retrieving new reservations
    - Retrieving modified/cancelled reservations
    - Retrieving reservations using B.XML

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

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

  • [Provider Portal] Infinite loading issue on the Properties page (ACI-3586)

    Booking.com now shows the list of connected properties again on the Properties page.

  • [Provider Portal] System error in the Reservation Timeline (ACI-3592)

    The system no longer shows system error when you search for a reservation in Reservation Timeline tool.

Q3 2023

19 September 2023

In this release cycle we did not have any bug fixes. However, we would like to share with you the updated deprecation and sunsetting dates of version 1.0 of the B.XML availability and the roomrates endpoint. Read on for more information:

What is going to change?

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

Booking.com has released a new and improved version 1.1 for both B.XML availability and B.XML roomrates endpoints. We fixed the bugs on B.XML availability v1.1 and set new deprecation and sunsetting dates for the old version 1.0 on both endpoints:

  • Deprecation date: December 06, 2023
  • Sunsetting date: December 16, 2023

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

5 September 2023

In this release cycle, we would like to talk about the recent enhancement to our authentication rules. In addition, we have multiple bug fixes to tell you about. Read on for more information.

What's new?

  • [New functionality] Open or close a specific roomtype

    You can now open or close a specific roomtype irrespective of whether there are multiple active roomrates assigned to the roomtype using the version 1.1 of the following endpoints:

    You can also retrieve information whether a roomtype is closed using the B.XML v1.1 roomrateavailability endpoint. For more information, see the Migration guide.

What has changed?

  • [All APIs] Enhanced authentication rules to validate each API request

    We have improved our authentication and authorisation rules while validating API requests for increased safety. If your API requests do not meet the improved authentication rules, then our system returns an HTTP 401 authentication error. For more information, see the Enhanced authentication rules section.

What was fixed?

  • [Rates and Availability API] Faulty partial updates with overlapping dates (ACI-3523)

    Booking.com now processes availability updates with overlapping dates for different attributes such as prices, restrictions and inventory again when you send them via the BXML v1.1 availability endpoint.

  • [Reservations API] Incorrect payout remarks for bank transfer reservations (ACI-3527)

    The system no longer shows virtual credit card as payout type for bank transfer bookings.

  • [Content API] PrepaymentPolicy incorrectly defaults to effective from after_cancellation_fee_begins (ACI-3539)

    The system now applies PrepaymentPolicy effective from after_reservation_is_made by default again when sending overlay updates via the POST OTA_HotelDescriptiveContentNotif endpoint.

  • [Content API] Internal server errors (ACI-3545)

    The system no longer returns internal server errors when updating CVC collection via the POST OTA_HotelDescriptiveContentNotif endpoint.

  • [Content API][Documentation] Attribute currencycode for element Services

    The documentation now shows the attribute currencycode for element Services. Take a look at the Create a property documentation and the Service documentation.

22 August 2023

In this release cycle, we would like to bring two bug fixes to your attention. Read on for more information.

What was fixed?

  • [Rates and Availability API] 400 errors NOT_A_VALID_DATE for updating the current date (ACI-3521)

    Booking.com now accepts availability updates for the current date when you send them via the BXML v1.1 availability endpoint.

  • [Reservations API] Retrieved modification messages failed and stayed in the message queue (ACI-3522)

    The system now acknowledges retrieved modification messages and removes them from the message queue again.

8 August 2023

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

25 July 2023

In this release, we want to talk about the release of the Reservation Recovery API! We also want to remind you about the upcoming changes to our network routing infrastructure on August 1, 2023 for secure-supply-xml.booking.com (reservations) traffic. In addition, we have information on bed types for multi-bedroom room types and special requests in the documentation that we want to share with you. Read on for more information.

What is new?

What is going to change?

  • [Reservations API] Important changes to our network routing infrastructure for secure-supply-xml.booking.com traffic

    Booking.com will migrate all traffic from secure-supply-xml.booking.com to Amazon Cloudfront on August 1, 2023. As a result, our IP addresses (which have been static before) 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 have applied any IP whitelisting earlier, you must remove them as per our previous communication, and reach us using the DNS lookup according to best practices. Failing to make these changes prior to August 1, 2023, will result in our APIs being unreachable for reservation retrieval and other services.

    To learn more, see the related announcement posted on July 20, 2023 on the Provider Portal.

What has changed?

  • [Room type and rate plan management API] [modify-room-amenities] Setting bed types for rooms that support multiple bedrooms [Documentation]

    To set up bed types for rooms that support multiple bedrooms (such as Apartment or Suite), you must now use the Amenities element under SubRooms. To learn more, see room amenities and bed types in a multi-bedroom room type.

  • [Messaging API] [Documentation] List of special and structured requests

    The documentation now shows the list of special and structured requests which are currently not supported by the Messaging API. Take a look at the Messaging API documentation.

11 July 2023

What is new?

What has changed?

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

    Booking.com has sunset the functionality of specifying nearby attractions and property's relative position information using AreaInfo and HotelInfo > RelativePositions as of July 3, 2023. Booking.com has deprecated the functionality on March 15, 2023 and has started automatically generating the nearby places and the property's relative position information.

    For more information on the deprecation and sunsetting, see [Property nearby places and relative position information in Content API.][property-area-info]

What was fixed?

  • [Content API] [Documentation] Clarification on setting up parking fee (ACI-3450)

    The documentation now states that you can set up parking fee policy details as a FeePolicy via the POST OTA_HotelDescriptiveContentNotif endpoint, which will not be added to reservation price. To apply parking fee as charges which is applied to all reservations, properties must request Booking.com local support team to set it as VAT/Tax/Charges in the extranet.

    To learn more, see the Create a property and the Retrieve property details documentation pages.

  • [Provider Portal] 400 Bad Request and 403 Forbidden Errors (ACI-3486)

    The system no longer shows the errors when accessing the Provider Portal.

Q2 2023

27 June 2023

What is going to change?

  • [All APIs] Sunsetting HTTP 1.0 for all API endpoints

    Booking.com is sunsetting HTTP 1.0 support for all the API endpoints on August 31, 2023. If you are still using HTTP 1.0, start using a newer version of HTTP, such as HTTP 1.1 or HTTP 2. For more information on the sunsetting, see Sunsetting HTTP 1.0 support.

What was fixed?

  • [Reservations API] Acknowledged modification messages stayed in the queue (ACI-3454)

    Booking.com now removes acknowledged modification messages in the queue again when you send acknowledgement via the POST OTA_HotelResModifyNotif endpoint.

  • [OFFICE] Properties with change in ownership got disconnected repeatedly by cron job (ACI-3478)

    The system no longer repeatedly disconnects properties which had recently changed ownership.

13 June 2023

In this release cycle, we would like to remind you about the upcoming sunsetting of HTTP 1.0 support. In addition, we want to reiterate the upcoming changes to a few amenity codes and the sunsetting of the functionality of specifying nearby attractions and property's relative position information via Content API. Read on for more information.

What is going to change?

  • [All APIs] Sunsetting HTTP 1.0 for all API endpoints

    Booking.com is sunsetting HTTP 1.0 support for all the API endpoints on August 31, 2023. If you are still using HTTP 1.0, start using a newer version of HTTP, such as HTTP 1.1 or HTTP 2.

  • [Content API] Change of amenity codes

    To reiterate our previous notice, Booking.com will start returning a different amenity code for the following amenities when calling the POST OTA_HotelDescriptiveInfo endpoint from June 22, 2023 onwards.

    The codes will match the amenity codes you can set via the POST OTA_HotelDescriptiveContentNotif and POST OTA_HotelInvNotif endpoints.

    • Balcony (change from code 7 to code 5017)
    • Patio (change from code 7 to code 5037)
    • Clothing Iron (change from code 55 to code 5015)
    • Coffee Machine (change from code 19 to code 5120)
    • Wake Up Service/Alarm-clock (change from code 3 to code 5013)

    To view the list of amenity codes, see Room Amenity Type Codes.

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

    Booking.com is sunsetting the functionality of specifying nearby attractions and property's relative position information using AreaInfo and HotelInfo > RelativePositions on June 30, 2023. Booking.com has deprecated the functionality on March 15, 2023 and has started automatically generating the nearby places and the property's relative position information.

    For more information on the deprecation and sunsetting, see [Property nearby places and relative position information in Content API.][property-area-info]

30 May 2023

In this release cycle, we want to:

  • Introduce a new and improved roomrates endpoint version.
  • Reiterate on the upcoming changes to a few amenity codes, and,
  • Share a couple of improvements to the API documentation.

Read on to learn more about these changes.

What is new?

  • [Room type and rate plan management API] - New and improved version of B.XML roomrates endpoint

    We have released a new and improved version of the B.XML roomrates endpoint (v 1.1). However, you can also continue to use the old version by specifying the version 1.0 until October 13, 2023. To learn more about versioning, see What is versioning?

With the v1.1 B.XML roomrates endpoint, you can:

  • Query roomrate details with or without rewritten rate details.
  • Retrieve additional response details like flexible children prices, if they are set.
  • See improved latency.

Also, in version v1.1:

  • To resolve security issues and non-standard system behavior, the v1.1 roomrates endpoint supports the UTF-16 encoding algorithm.
  • The endpoint returns all responses within the roomrates object.
  • The endpoint doesn't return the max_children attribute anymore.

  • The endpoint doesn't return the redundant follows_room_rate_properties attribute in the response while retrieving roomrates with rate relations.

    For more information on how to call the new version, see the [Changes to the roomrates endpoint][changes-to-the-roomrate-endpoint] section in the migration guide.

What is going to change?

  • [Content API] - Change of amenity codes

    To reiterate our previous notice, Booking.com will start returning a different amenity code for the following amenities when calling the POST OTA_HotelDescriptiveInfo endpoint from June 22, 2023 onwards. The codes will match the amenity codes you can set via the POST OTA_HotelDescriptiveContentNotif and POST OTA_HotelInvNotif endpoints.

    • Balcony (change from code 7 to code 5017)
    • Patio (change from code 7 to code 5037)
    • Clothing Iron (change from code 55 to code 5015)
    • Coffee Machine (change from code 19 to code 5120)
    • Wake Up Service/Alarm-clock (change from code 3 to code 5013)

    To view the list of amenity codes, see Room Amenity Type Codes.

What has changed in API documentation?

  • [Content API] - Revamped topics in the Content API documentation

    We have added/updated the following sections in the Content API documentation for improved clarity:

16 May 2023

In this release cycle, we want to talk about the change related to a few amenity codes. In addition, we have two bug fixes to tell you about. Read on for more information.

What is going to change?

  • [Content API] Change of amenity codes

    Booking.com will start returning a different amenity code for the following amenities when calling the POST OTA_HotelDescriptiveInfo endpoint from June 22, 2023 onwards. The codes will match the amenity codes you can set via the POST OTA_HotelDescriptiveContentNotif and POST OTA_HotelInvNotif endpoints.

    • Balcony (change from code 7 to code 5017)
    • Patio (change from code 7 to code 5037)
    • Clothing Iron (change from code 55 to code 5015)
    • Coffee Machine (change from code 19 to code 5120)
    • Wake Up Service/Alarm-clock (change from code 3 to code 5013)

    To view the list of amenity codes, see Room Amenity Type Codes.

What was fixed?

  • [Rates and Availability API] Incorrect error "The request could not be fulfilled due to technical difficulties" (ACI-3427)

    Booking.com no longer returns the incorrect error message with 200 response when calling the B.XML availability endpoint.

  • [Reservations API] Cancellation messages with RoomStay element (ACI-3438)

    The system now returns cancellation messages without RoomStay elements again when calling the GET OTA_HotelResModifyNotif endpoint.

2 May 2023

In this release cycle, we want to talk about the deprecation of HTTP 1.0 support. In addition, we want to bring your attention to two bug fixes. Read on for more information.

What is new?

  • [All APIs] Deprecating HTTP 1.0 for all API endpoints

    Booking.com is deprecating HTTP 1.0 support for all API endpoints on August 31, 2023. Start using a newer version of HTTP, such as HTTP 1.1 or HTTP 2 before the deprecation date if you are still using HTTP 1.0.

What was fixed?

  • [OFFICE] 404 Not Found error when trying to access to the Extranet Connectivity provider page(ACI-3433)

    The Connectivity Provider page is now accessible for property partners again.

  • [Content API] Wrong number of swimming pools created (ACI-3417)

    The system no longer creates multiple pools when setting only one swimming pool via the POST OTA_HotelDescriptiveContentNotif endpoint.

18 April 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?

  • [Content API] Created properties not linked to the specified LEID (ACI-3413)

    The system now links the created properties to the LEID again when you specify the LEID in the CompanyName Code via the POST OTA_HotelDescriptiveContentNotif endpoint.

  • [Reservations API] Missing payment collection information for Pay at Property bookings (ACI-3416)

    Booking.com now shows the payment collection information in the XML messages of Pay at Property bookings again.

4 April 2023

In this release cycle, we want to introduce you to a new version in the B.XML availability endpoint. Read on for more information.

What is versioning?

Going forward, we want to release improvements and feature enhancements to APIs through versions. With versions, you can continue to use the old endpoint (for a limited time until it is deprecated) or migrate to a new version when you want to get the advantage of the new enhancements. You can do so by just adding a new header accept-version in the calls to the old API endpoint.

By using the new header and the version number supported by the API, you can get the API functionality specific to that version.

Not all APIs support versioning yet

Only the B.XML availability and roomrates endpoints currently supports versioning.

What is new?

  • New and improved version of B.XML availability endpoint

    We have released a new and improved version of the B.XML availability endpoint (v 1.1). However, you can also continue to use the old version by specifying the version 1.0 until September 10, 2023.

    With the v1.1 B.XML availability endpoint, you get:

    • Improved error handling and error description.
    • Improved latency.

    For more information on how to call the new version, see the [Changes to the availability endpoint][changes-to-the-availability-endpoint] section in the migration guide.

Q1 2023

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.][property-area-info]

  • [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.][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.][property-area-info]

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.

Q4 2022

27 Dec 2022

Happy Holidays and a Wonderful New Year to everyone! In this release cycle, we want to bring your attention to two bug fixes. Read on for more information.

What was fixed?

  • [Reservations API] Decoding issue of non-UTF8 promotion names (ACI-3301)

    Booking.com now correctly returns non-UTF8 promotion names again in the reservation messages.

  • [Reviews API] Missing element review_score (ACI-3333)

    The system now returns the element review_score again when calling the GET properties/{property_id}/score endpoint.

13 Dec 2022

In this release we want to talk about the release of the Market Insights API! We also have a few bug fixes and a reminder about the upcoming changes to the roomrateavailability endpoint. Read on for more information.

What is new?

  • Market Insights API

    This API enables eligible providers to explore what the guests are searching for using Booking.com and to better understand the demand in their eligible properties' region. To learn more, see the Market insights API documentation.

What is going to change?

  • Roomrateavailability endpoint

    We have made some updates to the roomrateavailability endpoint as part of our API Modernisation Project to improve the overall experience of the API. You can implement our test endpoint (provided temporarily) to evaluate the new behaviour. The new changes will take effect on Feb 13, 2023.

    For more information on the updates, see Changes to roomrateavailability endpoint.

What was fixed?

  • [Content API] Missing parking amenity (ACI-3215)

    The system now updates the hotel amenities "Indoor parking" and "Street parking" when calling the OTA_HotelDescriptiveContentNotif endpoint without an empty ParkingFeePolicy element. For more information, see ParkingFeePolicy.

  • [Messaging API] Incorrect message conversations (ACI-3228)

    Booking.com no longer returns message conversations with blocked access when calling the GET /properties/{property_id}/conversations endpoint.

  • [Reviews API] Incorrect review ID (ACI-3325)

    The system now returns the unique review_id of reservations again when calling the GET /properties/{property_id}/reviews endpoint.

29 Nov 2022

In this release cycle we have added a new endpoint for the Licences API. In addition, we want to bring your attention to a few bug fixes. Read on for more information:

What is new?

  • [Licences API] New endpoint

    The Licences API now enables you to retrieve licence requirements data without specifying the property ID. You must specify the following information:

    • Property's latitude and longitude information.
    • The country code of the property.
    • The property type ID.

    To learn more, see the Licences API documentation.

What is going to change?

  • Roomrateavailability endpoint

    We propose to make some updates to the roomrateavailability endpoint to align with the general expectation and to improve the overall experience of the API. You can implement our test endpoint (provided temporarily) to evaluate the new behaviour. The new changes will take effect from Feb 13, 2023.

    For more information on the updates, see Changes to roomrateavailability endpoint.

What was fixed?

  • [Reservations API] Missing guest count information (ACI-3164)

    Booking.com now returns guest count data of children aged 0 in the reservation messages.

  • [Reporting API] 400 errors for no-show reported 24 hours after check-in (ACI-3269)

    The system now accepts no-show reporting up to 48 hours after check-in again when calling the POST /xml/reporting endpoint.

  • [Content API] [Room type and rate plan management API] Missing room names (ACI-3305)

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

15 Nov 2022

In this release cycle, we have added a few new features and a change in how fee updates work via the Content API. In addition, we have multiple bug fixes to tell you about. Read on for more information:

What is new?

What was fixed?

  • [Messaging API] Incorrect message data (ACI-3256)

    Booking.com now returns correct message data again when calling the GET /messages/search/result/{job_id} endpoint.

  • [Licenses API] Inconsistent error messages for properties that do not require licenses(ACI-3264)

    The system now returns empty response for properties that do not require licenses again when calling the GET /rules/properties/{property_id} endpoint.

  • [Provider Portal] Missing data in Email Fallbacks report (ACI-3273)

    The Email Fallbacks report now shows the correct fallback data again.

01 Nov 2022

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

What was fixed?

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

    The system now returns message data again when calling the GET/messaging/messages/latest endpoint.

18 Oct 2022

In this release cycle, we do not have any major releases. However, we have bug fixes to tell you about. Read on for more information.

What was fixed?

  • [Reservations API] Incorrect empty responses when calling the POST reservations endpoint (ACI-3167)

    The system now returns the reservation details of bookings that were previously processed via the GET OTA_HotelResNotif and the POST OTA_HotelResNotif endpoints when called using the POST reservations endpoint with the id specified.

  • [Reservations API] Incorrect payment information for virtual credit card reservations (ACI-3242)

    Booking.com now shows correct payment information of virtual credit card bookings in the reservation messages again.

04 Oct 2022

In this release cycle, we would like to bring your attention to our newly revamped Reservations API documentation. In addition, we have fixed a few bugs. Read on for more information.

What is new?

  • [Reservations API] Revamped documentation

    We have revamped our Reservations API documentation, and added new topics and flowcharts! To learn more, see the Reservation API documentation.

  • [Promotions API] China channel deprecation

    Booking.com has deprecated the China channel for promotions that are not geo rates (Promotions API) on October 5, 2022 and will sunset it December 7, 2022. You can still set the channel to China before it becomes sunset, but this has no longer an impact on guests making reservations through Booking.com. To emphasise, you can still set geo rates for China, this only affects the specific China target channel.

What was fixed?

  • [Provider Portal] Missing data in Email Fallbacks report (ACI-3166)

    The Email Fallbacks report now shows the correct fallback data again.

  • [Messaging API] Missing conversations (ACI-3192)

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

Q3 2022

20 Sep 2022

In this release cycle we have added a new endpoint to the Online Check-in API, which enables properties to select which input fields to include in their online guest registration form. In addition, we have multiple bug fixes to tell you about. Read on for more information:

What is new?

  • [Online Check-in API] New endpoint

    We have added the GET /online-checkin-api/properties/{property_id}/checkin-form-config endpoint, which enables you to retrieve the current configuration for a property's check-in form. In addition, there is the PUT /online-checkin-api/properties/{property_id}/checkin-form-config endpoint, which enables you to modify or update the form configuration per property. To learn more, see the Online Check-in API documentation.

What was fixed?

  • [Reporting API] [Documentation] Possibility to change check-in date (ACI-3180)

    The documentation now states that properties can temporarily change the check-in dates more than once within 24 hours before check-in via the Reporting API. To learn more, see the Reporting API documentation.

  • [Property Profile API] Incorrct 404 errors (ACI-3184)

    The system no longer returns incorrect 404 error when calling the POST /properties/{propertyId} endpoint.

  • [Reservations API] Missing daily and weekly fallback reports (ACI-3193)

    You can now receive the daily and weekly fallback reports via email again.

  • [Content API] [Documentation] Missing element Quantity (ACI-3197)

    Booking.com now returns the number of rooms per roomtype when calling the OTA_HotelDescriptiveInfo endpoint. If the information is set via the extranet or the API, you will find the information specified in element Quantity in the responses. To view an example request response, see the Content API documentation.

  • [Reservations API] Missing credit card details (ACI-3202)

    The system now returns the credit card details again within relevant reservation messages.

06 Sep 2022

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

What was fixed?

  • [Reservations API] Incorrect CommissionPayableAmount showing as 0 (ACI-3176)

    Booking.com now shows the correct commission payable amount in the reservation messages.

23 Aug 2022

This time we have removed all old documentation related to room type and rate management. To access the recently revamped documentation, see room type and rate plan management API. In addition, we want to bring your attention to the following bug fixes. Read on for more information.

What was fixed?

  • [Reservations API] Wrong smoking policy (ACI-2971)

    The system now shows the correct smoking policy in reservation messages.

  • [Messaging API] Forbidden 403 error messages returned when sending messages via the POST /properties/{property_id}/conversations/{conversation_id} endpoint (ACI-3120)

    Booking.com now returns an error message "Sender does not have write access to the conversation" when the property does not have write access to the conversation. For updates that contain messages that do not pass the security filter, the system returns an error message "Message content failed to pass security filters".

  • [Content API] Incorrect error 'LEID not allowed to add properties in this location' when calling the OTA_HotelDescriptiveContentNotif endpoint (ACI-3126)

    The system no longer returns the 'LEID not allowed to add properties in this location' error when creating or updating properties in Northern Cyprus for partners who have already signed a contract for Northern Cyprus.

09 Aug 2022

In this release cycle we have removed all documentation related to the solutions we sunsetted in April. For more information, see the deprecation and sunsetting documentation. In addition, we have fixed multiple bugs. Read on for more information.

What was fixed?

  • [Messaging API] Retrieved messages remain in the queue (ACI-3098)

    Booking.com now removes retrieved messages from the messaging queue and returns new messages when calling the GET /messages/latest endpoint again.

  • [Content API] Duplicated properties (ACI-3136)

    The system no longer creates properties which have the same property name, address and location with an existing properties when calling the OTA_HotelDescriptiveContentNotif endpoint.

  • [Content API] Unclear error message returned via the POST /OTA_HotelSummaryNotif endpoint (ACI-3149)

    Booking.com now returns an error message "License information for property/room did not pass validation. Use Licenses API to update license details." when the license information of a property is missing.

  • [Reservations API] Incorrect format of RoomDescription Name (ACI-3152)

    The system returns the room type name and then the policy (in that order) within the RoomDescription Name element for confirmations and modifications when calling the GET /ota/OTA_HotelResNotif and GET /ota/OTA_HotelResModifyNotif endpoints.

  • [Extranet] Error 'Something went wrong while processing your request - try again' (ACI-3178)

    Booking.com no longer returns the Something went wrong while processing your request - try again error when properties make connection requests on the Connectivity provider page of the extranet.

  • [Documentation] VAT and TAX clarification

    The system does not allow setting both VAT and tax at the same time and will return an error "Trying to define VAT/TAX twice for the same hotel.

26 July 2022

In this release cycle, we are excited to announce the availability of the updated room amenities management documentation. We would also like to remind you about the deprecation of Business Booker promotions (business rates) on 29 July 2022, in addition to a Messaging-API-related bug fix. Read on for more information.

What is new?

  • Deprecation of Business Rates

    Business Booker promotions (business rates) will be deprecated as of 29 July 2022. The rates will no longer be available and bookable on our platforms. The sunsetting of business rates will follow and happen on 16 September 2022. For more information, see the deprecation and sunsetting documentation.

  • Revamped documentation on managing room amenities

    The managing room amenities documentation has been completely revised to provide more details on how to manage room amenities via the /ota/OTA_HotelInvNotif endpoint using multiple request and response body examples. Take a look at the managing room amenities documentation.

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 as this reopened bug is fixed again:
    - GET /properties/{property_id}/conversations
    - GET /properties/{property_id}/conversations/{conversation_id}
    - POST /properties/{property_id}/conversations/{conversation_id}/attachment_chunks

12 July 2022

In this release cycle we did not have any bug fixes. However, we want to bring your attention to an update on the Reservations API and the sunsetting of Business Rates. Read on for more information:

What is new?

  • Sunsetting Business Rates

    Business Booker promotions (business rates) will be deprecated 29 July 2022, with the sunsetting happening on 16 September 2022. Take into account that these business rates will no longer be visible to Booking.com guests starting July 29 (deprecation date). More information to follow and keep an eye on the deprecation section.

What has changed?

  • [Reservations API] API Improvements

    Booking.com has made some improvements to the reservations API. If you have implemented the feature ota_res_response_token, you may now see a reduction in API responses with the HTTP status 409 CONFLICT.

Q2 2022

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.

Q1 2022

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.

Q4 2021

28 December 2021

Happy Holidays everyone! In this release cycle, we do not have any updates for you. Stay tuned for more to come in 2022!

14 December 2021

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

30 November 2021

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?

16 November 2021

In this release cycle we bring a bug fix to your attention.

What was fixed?

  • [Promotions API] Incorrect minimum discount value for Secret Deal promotions (ACI-2603)

    You can no longer create Secret Deal promotions (promotions with target_channel as subscribers) with less than 10% discount value.

02 November 2021

In this release cycle we did not have any major news. However, we want to bring your attention to a few bug fixes.

What was fixed?

  • [Rates and Availability API] Outdated last synchronisation timestamp (ACI-2714)

    Properties can now see updated timestamp of the latest rates and availability synchronization on the Extranet Calendars.

  • [Content API] Incorrect ResponseInvCode returned (ACI-2826)

    The system now returns a correct ResponseInvCode when sending overlay updates via the OTA_HotelInvNotif endpoint.

  • [Content API] Incorrect ResponseHotelCode returned (ACI-2827)

    The system no longer returns incorrect ResponseHotelCode to overlay updates via OTA_HotelDescriptiveContentNotif endpoint.

19 October 2021

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?

  • [Photo API] Missing element 'data' (ACI-2755)

    Booking.com now returns element 'data' when calling POST /properties/{property_id}/gallery and POST /properties/{property_id}/rooms/{room_id}/gallery endpoints.

  • [Promotions API] Incorrect Mobile Rate promotions discount value (ACI-2637)

    You can no longer create Mobile Rate promotions with less than 10% discount value.

  • [Messaging API] Missing messages when calling GET /properties/{property_id}/conversations/type/{conversation_type} endpoint (ACI-2721)

    Booking.com now returns all messages sent to email aliases of reservations.

  • [Messaging API] No reply needed tag not removed (ACI-2752)

    Calling DELETE /properties/{property_id}/conversations/{conversation_id}/tags/no_reply_needed endpoint now removes the no_reply_needed tag from a conversation.

  • [Content API] Attractions not returned in the response (ACI-2776)

    The system now returns the attractions element when calling the OTA_HotelDescriptiveInfo endpoint.

  • [Reservation API] Missing booked promotions (ACI-2781)

    Booked promotions (Flash Deal, Getaway Deal, Basic deals Last-minute deal, Early booker deal and Free nights deal) are now present in reservation responses.

  • [Messaging API] 404 errors for conversations without any messages (ACI-2806)

    Booking.com no longer returns 404 errors for conversations without any messages when calling GET /properties/{property_id}/conversations/type/{conversation_type} endpoint.

5 October 2021

In this release cycle we have added a new endpoint for the contracting API. In addition, we have bug fixes to tell you about. Read on for more information:

What is new?

  • [Contracting API] New endpoint

    We have added the GET /partners/legal-details/legal-entity/{id} endpoint, which enables you to retrieve legal details of existing contracts by legal entity id. To learn more, see the Contracting API documentation.

What was fixed?

  • [Reservations API] Missing elements 'cc_type' and 'cc_cvc' for confirmation messages of risk-free reservations (ACI-2729)

    Booking.com now returns all payment-related information for risk-free bookings when calling the BXML reservations endpoint.

  • [Reservation API] Random reservations missing (ACI-2770)

    The system now returns all bookings in the response when calling the BXML reservations endpoint.

  • [Licenses API] Incorrect 500 errors (ACI-2773)

    The system no longer returns internal server error when retrieving licence requirements via GET /rules/properties/{property_id} endpoint.

Q3 2021

21 September 2021

This release cycle we bring a bug fix and documentation update to your attention.

What was fixed?

  • [Promotion API] [Documentation] Incorrect Geo Rate promotions discount value (ACI-2628)

    The system no longer allows creation of Geo Rate promotions with less than 5% discount value. The documentation now correctly shows maximum discount value 80 for Geo Rate promotions. To learn more, see Geo Rate promotion documentation.

7 September 2021

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

24 August 2021

In this release cycle we did not have any bug fixes. However, we want to bring your attention to updates on the Online Check-in API and Messaging API. Read on for more:

What is new?

  • [Online check-in API] New endpoint

    We have added the GET online-checkin-api/connections endpoint that enables you to retrieve all of your properties that are onboarded and can use the online check-in flow. Take a look at the Online Check-in API documentation.

  • [Messaging API] New features

    We have enabled the support for free text special requests (not including structured special requests). In addition, the API now supports messages sent to email aliases of reservations that are made by guests without an account or not logged in on Booking.com. Have a look at the Messaging API documentation.

10 August 2021

This release cycle we bring a few bug fixes to your attention.

What was fixed?

  • [Rates and availability API] [Documentation] Issue with American meal plan (ACI-2500)

    Setting meal plan to American no longer enables all-inclusive meal plan on roomrates. To learn more, see meal plan types.

  • [Rates and Availability API] Incorrect pricing type set for new rate plans created via Extranet (ACI-2524)

    Creating new rate plans for OBP properties via Extranet now results in rate plans on OBP pricing type.

  • [Contracting API] Missing elements 'contract_signed' and 'contract_countries' (ACI-2719)

    The system now returns both elements when calling the POST /partners/legal-details endpoint.

  • [Content API] Unexpected BuildHotel error with overlays via OTA_HotelDescriptiveContentNotif (ACI-2720)

    The system no longer returns BuildHotel errors caused by incorrect dates being written to our databases.

27 July 2021

This release cycle we have added a test flag for the Contracting API so that you can test the entire work flow. Go check it out!

What is new?

  • Contracting API: Testing

    The Contracting API now enables you to test the API's functionality by using a test flag. To learn more, see the Contracting API documentation.

What was fixed?

  • [Reservations API] 502 errors for BXML reservations endpoint (ACI-2705)

    We have taken out a malfunctioning server, which caused the 502 errors.

13 July 2021

In this release cycle we did not have any major releases. However, we want to bring your attention to a few bug fixes.

What was fixed?

  • [Documentation] Incorrect breakfast type codes (ACI-2661)

    The documentation now correctly shows code 5011 for buffet and code 5012 for A la carte. To learn more, see breakfast type codes.

  • [Reservations API] Empty reservation responses (ACI-2682)

    The system now returns reservation details to retrievals via BXML.

  • [Content API] Issues with SPO flow (ACI-2693)

    SPO properties with contract signed are no longer stuck in "Pending Property Registration" status.

  • [Content API] Incorrect 500 errors (ACI-2696)

    The OTA_HotelDescriptiveContentNotif endpoint no longer returns internal server error when creating test properties.

Q2 2021

29 June 2021

In this release we want to talk about the new online check-in API! This could greatly help to facilitate the check-in experience of your properties' guests. We also have a documentation bug fix on the menu that caused some issues.

What is new?

What was fixed?

  • [Reservations API] Incorrect 500 errors (ACI-2662)

    The B-XML reservations endpoint no longer returns incorrect 500 errors when both the reservation timeline indicates a succesful response and no fallback email is triggered to properties.

  • [Documentation] Unclear fee tax types (ACI-2642)

    The documentation now correctly states that certain fee types all return as 14 when retrieving reservations. To learn more, see fee tax type codes.

15 June 2021

This release cycle we bring a few bug fixes to your attention.

What was fixed?

  • [Provider Portal] No values in the "Bookable until History" reports (ACI-2659)

    The reports for Bookable until History now show the correct data again.

  • [Room type and rate plan API] Not returning inactive rate plans (ACI-2622)

    When retrieving rate plans, you can see the inactive rate plans again.

1 June 2021

We fixed another round of bugs, including extranet issues regarding Connectivity Partner details appearing on feature pages.

What was fixed?

  • [Promotions API] Unprompted internal server errors - mobile rates (ACI-2647)

    Creating and updating mobile rates using the Promotions API no longer returns internal server errors.

  • [Promotions API] Unprompted internal server errors - geo rates (ACI-2648)

    Creating and updating geo rates using the Promotions API no longer by returns internal server errors.

  • [Rates and Availability API] MISSING_ROOM_TAG error (ACI-2643)

    Availability updates via BXML no longer returns error "MISSING_ROOM_TAG" when you include the room tag.

  • [Extranet] Not showing all Connectivity Partners (ACI-2524)

    Properties can now find details of all their Connectivity Partners on the extranet features page.

  • [Extranet] Missing 'Set and Update Room Inventory' tag (ACI-2404)

    Properties can now see the 'Set and Update Room Inventory' tag again on the extranet features page.

18 May 2021

In this release we bring your attention to an update on the policies front. In addition, we have bug fixes to tell you about. Read along to see whether any of the fixes postively impact your workflows.

What has changed?

What was fixed?

  • [Rates and availability API] HotelAvailNotif returning "Can't parse malformed XML" errors (ACI-2645)

    A temporary outage caused these errors, which now the systems are back online should no longer occur.

  • [Rates and availability API] B.XML availability returning "Can't parse malformed XML" errors (ACI-2644)

    A temporary outage caused these errors, which now the systems are back online should no longer occur.

  • [Content API] Swimming pool amenity not updated with an overlay call (ACI-2636)

    Setting service code to 66 via HotelDescriptiveContentNotif is now correctly showing the outdoor pool hotel amenity on the extranet and the Booking.com frontend.

  • [Content API] Error 'cannot set price1ok' returned with overlay (ACI-2604)

    The system now returns the remarks element even if the remark element is empty.

  • [Content API] Unexpected EOF at target using HotelSearch (ACI-2404)

    The errors were caused by a gateway issue, which is now resolved.

04 May 2021

May Connectivity be with you. We do not have major news for you, but we did fix some bugs. Read on to see whether this would affect you:

What was fixed?

  • [Reservations API] Increased rate of 502 errors for BXML reservations endpoint (ACI-2618)

    The errors were caused by an outdated load balancer configuration, which now redirects traffic to servers than can handle the incoming requests.

  • [Reservations API] Remarks element not always present in reservation responses (ACI-2617)

    The system now returns the remarks element even if the remark element is empty.

20 April 2021

In this release cycle, we want to bring your attention to the total renovation of the documentation for the room type and rate plan management API! This was a concerted effort to simplify the inner workings of the API to enable you easily integrate with it or update aspects depending on your use case. Besides that we also squashed a few more bugs. Read on for more:

  • [Room type and rate plan management API] New documentation

    We published a new and improved documentation section for the room type and rate plan mangement API. While it focuses mostly on the happy path scenarios, it also includes scenarios and use cases that are there to help you get started and improve existing flows. To discover the new documentation, see the Room type and rate plan management API documentation.

What was fixed?

  • [Content API] No cancellation grace period information in HotelDescriptiveInfo response (ACI-2607)

    You can now retrieve CancellationGracePeriod using the OTA_HotelDescriptiveInfo endpoint.

  • [Reservations API] Not returning parent and child rates correctly (ACI-2599)

    Both parent and child rate are present in reservation response if the guest's booking had a rewritten (child) rate.

  • [Licences API and Content API] Issue with retrieving licence requirements via HotelSearchNotif (ACI-2530)

    License requirements returned by Licenses API is now corresponding with license requirements returned by OTA_HotelSummaryNotif

  • [Content API] Updating property amenities removed internet and parking policy (ACI-2522)

    Updating property amenities no longer removes internet and parking policy.

  • [Rates and availability API] Issue with rmeal plan code (ACI-2500)

    RoomRate calls now return a correct MealPlan code, which matches the roomrate configuration.

  • [API errors] Incorrect API error report content (ACI-2569)

    Weekly reservation API error report emails now have the correct content.

6 April 2021

In this release cycle Booking.com did not have any major releases. However, we want to bring your attention to a few bug fixes.

What was fixed?

  • [Content API] Cancellation Exceptions could not be disabled (ACI-2588)

    Setting CancellationGracePeriod/@HoursAfterBooking and CancellationGracePeriod/@WeeksBeforeCheckIn to 0 via the OTA_HotelDescriptiveContentNotif endpoint is now correctly disabling Cancellation Exceptions.

  • [Reservations API] Guest count data missing when testing the feature guestcount_per_room (ACI-2519)

    Room level guest count data is now returned when the feature guestcount_per_room is specified as feature key in the API request header for testing purposes.

Q1 2021

23 March 2021

This release cycle we are happy to announce the release of the Messaging API! To learn more about the Messaging API and other updates, read on:

What is new?

  • [Messaging API] Messaging solution

    We released a new and improved Messaging API which enables you to create an inbox tool to help your properties seamlessly and effectively manage their Booking.com guest communications on your platform. Ready to start? Have a look at the Messaging API documentation.

    💡 Do you want to dive right into how you can build it? Have a look at our implementation use cases.

What was fixed?

  • [Reservations API] Unreadable guest names (ACI-2570)

    The names of the guests now show up without issues in the reservation messages.

  • [Reviews API] 500 errors (ACI-2498)

    The Guest reviews API endpoint no longer returns Internal Server (500) errors when calling it.

  • [Office] PCI emails not being sent (ACI-2555)

    You can receive PCI emails again, including password reset emails and PCI/PII expiration reminders.

9 March 2021

We are excited to announce the release of the Contracting API! This API intends to greatly simplify and expedite the contracting process between Accommodation Partners and Booking.com. Besides that, this cycle also includes the first ever migration guides. These intend to help you move from products and features that will be deprecated to new(er) alternatives. To learn more about these and other updates, read on:

What is new?

  • [Contracting API] Contracting solution

    We released a new, hybrid solution for Contracting, which includes a Contracting API and a new feature in the Connectivity Partner Portal. This solution enables you to automate new partner contracting processes with Booking.com. To start reading the documentation, see the Contracting API documentation.

    💡 Something extra? We included a error library for this particular product. Let us know whether this helpful and how it can be improved. To have a look, see Contracting API troubleshooting guide.

  • [Content API] Migration guides

    A migration guide is now available in the documentation to support you with implementing alternative solutions for Content API features that will be deprecated this and early next year. To learn more about what products and features will be deprecated and what new(er) alternatives you should implement, see migration guides.

What has changed?

What was fixed?

  • [Rates and Availability API] ARI not removed with feature on (ACI-2541)

    ARI is now removed when a property connects with a provider if the "Hotel must reset availability when connected" setting is active in your configuration.

  • [Content API] Double spacing in Chinese transliterations (ACI-2518)

    Transliterated Chinese names of booker and guest no longer have additional spaces in reservation XML.

23 February 2021

In this release cycle Booking.com did not have any major releases. However, we want to bring your attention to a few changes to the Content API and multiple bug fixes.

What has changed?

  • [Content API] Grouping Room Amenity Type Codes

    We grouped certain Room Amenity Type Codes that refer to the same or similar amenity in the documentation. These grouped codes now internally default to the same code on Booking.com. For more information, see the room amenity codes documentation.

  • [Content API] Star rating for non-hotel properties in France and French Territories

    It is now possible for non-hotel properties in France and its territories (country codes FR, YT, GP, MQ, RE, and GF) to set star ratings as well. For more information, see the awards documentation.

What was fixed?

  • [Content API] Damage deposit payment method issue

    The damage deposit payment method (SecurityDepositCollectMethod) is now correctly reflected in the OTA_HotelDescriptiveInfo endpoint.

  • [Content API] Min and Max Advanced Booking Offset inaccuracy

    If you set the min and max advanced booking offset to more than the maximum allowed value of 360 days via the OTA_HotelProductNotif endpoint, it now returns a warning message in the response.

  • [Content API] Spelling mistake for action element closed

    Documentation is updated with the correct element name for closing property via Content API. To see the change, go to closing a property.

  • [Content API] Accidental removal of internet and parking policies

    Modifiying or updating property amenities no longer removes internet and parking policies.

  • [Content API] Default value of deposit collection

    Documentation now states that if property has not been verified to use credit card payments, the default value of deposit collection becomes cash regardless of setting it to credit card.

  • [Content API] Table with cancellation policy codes error

    Information on cancellation policy (code 263) in documentation table is now matching its natural language description. To learn more, see the Booking cancellation and prepayment policies.

  • [Reservations API] Rounding up issue

    Cancellation fees and other tax and charges now round up to two decimals using BXML for reservations.

  • [Promotions API] Minimum discount value inconsistency

    The documentation now correctly shows the minimum accepted discount value for mobile rates is 10%. For more information, see the mobile rate promotions documentation.

Is this page helpful?    Yes   |    No