Migrating to new versions

At Booking.com, we want to continuously improve the Connectivity Partner experience. This means we try to build better products and deprecate the older versions. When Booking.com plans to deprecate a feature or a product, you can no longer use it after the communicated date of deprecation. To help facilitate the potential changes you must make, the migration guide tables on this page aim to help you understand what is deprecated and what its (improved) alternative is.

Changes to roomrateavailability endpoint

We plan to roll out the improvements made to the roomrateavailability endpoint soon.

The changes outlined in this section are applicable only when you use the test endpoint provided by your Connectivity account manager. This section covers only the changes based on the test endpoint. You can refer to the Rates & Availability documentation to know more about the existing functionalities.

Changes to the roomrateavailability endpoint

This section captures the latest changes to roomrateavailability available on the test endpoint. For a detailed explanation of the existing endpoint, see Retrieving rate and inventory details.

Test Endpoint

POST
https://supply-xml.booking.com/v1-beta/hotel/roomrateavailability
What changed? Old behaviour New behaviour Notes
Data type change for price and price1 integer double
The number of rows returned when number_of_days is specified Returns (number_of_days + 1) rows. Returns number_of_days rows starting from the date specified in start_date (including). If the start_date is not provided, then the API returns inventory information from the next day of the request till the number_of_days value.
For example, if you specify number_of_days as 2, the API returns 3 rows starting from the date provided in the start_date. For example, if you specify number_of_days as 2, the API returns 2 rows starting from the date provided in the start_date.

Request example

<request>
  <hotel_id>8011855</hotel_id>
  <room_id>801185502</room_id>
  <start_date>2022-11-02</start_date>
  <number_of_days>2</number_of_days>
</request>

[Old behaviour] Response example

<result>
    <roomrate booked="2" cancelled="0" closed="0" date="2022-11-02" min_contracted_rooms="0" min_contracted_rooms_until="0" rate_id="25279855" room_id="801185502" rooms_to_sell="8"/>
    <roomrate booked="2" cancelled="0" closed="0" date="2022-11-03" min_contracted_rooms="0" min_contracted_rooms_until="0" rate_id="25279855" room_id="801185502" rooms_to_sell="8"/>
    <roomrate booked="2" cancelled="0" closed="0" date="2022-11-04" min_contracted_rooms="0" min_contracted_rooms_until="0" rate_id="25279855" room_id="801185502" rooms_to_sell="8"/>
</result>

[New behaviour] Response example

<result>
    <roomrate booked="2" cancelled="0" closed="0" date="2022-11-02" min_contracted_rooms="0" min_contracted_rooms_until="0" rate_id="25279855" room_id="801185502" rooms_to_sell="8"/>
    <roomrate booked="2" cancelled="0" closed="0" date="2022-11-03" min_contracted_rooms="0" min_contracted_rooms_until="0" rate_id="25279855" room_id="801185502" rooms_to_sell="8"/>
</result>

Licences

We plan to deprecate the old Licences API features on February 15, 2022. You can find the features we plan to deprecate next to their alternatives:

Deprecating CAPI feature New solution or alternative
Retrieving licence requirements using the licenses/check_requirements endpoint] or the static licences table. Retrieving the up-to-date licence requirements using the licenses/rules/properties/{property_id} endpoint.
Depending on the region of your properties, those requirements differ.
Sending licence information with the LicenseInfos element using the /ota/OTA_HotelDescriptiveContentNotif and [/ota/OTA_HotelInvNotif][creating-room] endpoints. Sending licence information using the /licenses/data/properties/{property_id} endpoint for property-level licences and the /licenses/data/properties/{property_id}/rooms/{room_id} endpoint for room type-level licences.
Retrieving existing licence information using the ota/OTA_HotelDescriptiveInfo endpoint. Retrieving existing licence information per property using the /licenses/data/properties/{property_id} endpoint endpoint for property-level licence information and the /licenses/data/properties/{property_id}/rooms/{room_id} endpoint for the room type-level licence information.

Hotelier messages

We plan to deprecate sending hotelier messages using the Content API on February 15, 2022. You can find the features we plan to deprecate next to their alternatives:

Deprecating CAPI feature New solution or alternative
Sending a hotelier message using the OTA_HotelDescriptiveContentNotif endpoint. Sending a hotelier message using the /properties/{property_id}/hotelier_messages endpoint.
Retrieving hotelier messages info using the OTA_HotelDescriptiveInfo endpoint. Retrieving hotelier messages using the /properties/{property_id}/hotelier_messages endpoint.

Single property owner (SPO) flow

We plan to deprecate the SPO flow, which is creating an independent property without legal entity id, on September 15, 2021. You can find the features we plan to deprecate next to their alternatives:

Deprecating CAPI feature New solution or alternative
Creating an independent property using the OTA_HotelDescriptiveContentNotif endpoint, which refers to creating a property without a legal entity id. Switching on the contracting feature that enables you to build a property first using [the OTA_HotelDescriptiveContentNotif endpoint][creating-independent-property] by providing a legal contact email under <ContactInfo ContactProfileType="contract">. For more information, see the Contracting API.

Photos through HotelDescriptiveContentNotif (HDCN)

We plan to deprecate sending photos using the HotelDescriptiveContentNotif endpoint on September 15, 2021. You can find the features we plan to deprecate next to their alternatives:

Deprecating CAPI feature New solution or alternative
Sending and uploading photos using the MultimediaDescriptions element in the the OTA_HotelDescriptiveContentNotif endpoint. Using the improved Photo API to manage all your photo needs.