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.

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.

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.

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.