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.

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 LicenseInfos element using the /ota/OTA_HotelDescriptiveContentNotif and /ota/OTA_HotelInvNotif 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 (HotelierMessage element) using the OTA_HotelDescriptiveContentNotif endpoint. Sending a hotelier message using the /properties/{property_id}/hotelier_messages endpoint.
Retrieving hotelier messages (HotelierMessage) 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 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.