# Overview The Booking.com Partner Supply API is designed for sending relevant data from the Connectivity Partner to Booking.com and handling booking retrieval information and communication for those reservations made on the Booking.com website. # API Call types At the time of this writing, Booking.com supports two general types of calls: 1. **B_XML** — an "in-house" Booking.com standard 2. **OTA** — Booking.com implementations based on the OTA standard In-house Booking.com functionality will generally be supported by the B_XML calls. It is therefore normal and expected that an Connectivity Partner will be using a mix of these two call types to achieve all necessary interface functionality. However, it is **not** recommended that an Connectivity Partner mix calls for the same, generic method simultaneously in both OTA and B_XML. For example, because the OTA reservation implementation involves different steps when it comes to achieving success or failure in reservation retrieval, problems could arise mixing OTA calls for reservation retrieval along with B_XML calls for reservation retrieval that overlap in function. The Booking.com OTA implementations are generally based on the OTA 2003B version, unless otherwise indicated. # Subdomains for API Calls The Booking.com subdomains used for its Supply API calls are the following: 1. **supply-xml.booking.com** — non-PCI servers, generally used for any non-reservation related information 2. **secure-supply-xml.booking.com** — PCI servers, generally used for reservation retrieval and confirmation Regardless of the subdomain used, the HTTPS protocol is required to send messages. For the specific URL endpoints needed, refer to the specific API call documentation. Creating an IP allowlist on behalf of the provider should be done based on the **domain name only**. Booking.com accepts no liability should a provider create an allowlist based on a range of IP addresses, and especially not a single IP address. Current probable IP ranges at the time of writing for supply-xml.booking.com are 5.57.16.0/23, and for secure-supply-xml.booking.com, 5.57.18.0/23. # Security All calls are expected to use the method **HTTP POST** via the **HTTPS** protocol (Hypertext Transfer Protocol [**HTTP/1.1**] over Transport Layer Security [**TLS 1.2**]. This is required to ensure encryption of machine account credentials. Booking.com will support crytographic protocols below the most recent version (TLS 1.2 at the time of this writing) on its own discretion. Providers should be aware that if they are using an older cryptographic protocol, support for it is subject to be dropped by Booking.com at any given time depending on the security landscape. This statement also applies to what are now current cryptographic protocols (eg. TLS 1.2) should these protocols be determined to no longer provide adaquate security. # API Call Categories The following categories of calls are available to you at this time: [Content Methods](/connectivity/docs/content) — Calls for building accommodations, rooms, rates, and policies, and linking this information together for the Booking.com website [System Information Retrieval Methods](/connectivity/docs/sysinfo) — Calls for retrieving general Booking.com system information, such as currencies needed per the accommodation's country. [Inventory / Rate / Restriction Methods](/connectivity/docs/ari) — Calls for loading inventory counts, rates, and price availability restrictions (for specific room-rate combinations) per date and/or date range combination. [Reservation Methods](/assets/res.6c68d5348b9e4b018a4bc48ce85d21718fa7fa063d953c80087e43090a4691d8.53c68abe.md) — Calls for Retrieving New Reservations, Modifications, Cancellations made on Booking.com, as well as the transmission of post-reservation guest requests and the reporting of certain reservation status. Should you be programming to the Booking.com API for the first time, it is recommended that you start with calls from the [System Information Retrieval Methods](/connectivity/docs/sysinfo) category once your machine accounts have been configured. # Expectations As new features are continuously implemented on Booking.com, new API calls and modifications are common place. It is expected that the Connectivity Partner will be able to implement new functionality within the shortest time possible. The following technical recommendations are suggested: * Support all accommodation functionalities * Work with PMS partners to implement existing and new Booking.com functionalities in an end-user friendly way * Offer real-time and last room rates and availability to avoid rate and availability parity issues * Load at least a full year of rates and availability * Offer an easy to use system for hotels including a simple and quick tool for room / rate creation and mapping * Advise accommodations to visit the Booking.com Extranet to check Booking.com specific details and verify information * Reduce reservations falling back to fax/e-mail Also, the following operational recommendations are suggested: * Inform accommodations about low availability * Inform accommodations of when their property is "bookable until" on Booking.com * Inform accommodations when specific rooms/rates are "bookable until" on Booking.com * Inform accommodations about unmapped room or rates on Booking.com * Offer great customer support and training for accommodations If you are seeking to request additional functionality, please discuss your proposals with your Booking.com Connectivity Account Manager. # Disclaimer All information contained in this document is subject to the terms and conditions of your contractual agreement with Booking.com.