Booking.com Connectivity API
The Booking.com API for properties, published as the Connectivity APIs, lets software providers known as Booking.com Connectivity Partners send and retrieve data for properties listed on Booking.com. Booking.com does not accept direct connections from individual properties, so a hotel or rental connects through a channel manager (Connectivity APIs documentation (Booking.com Developers)) (Connectivity Portal (Booking.com)).
Last updated: November 2026
How the Booking.com API works
The purpose is practical: one system, run by the provider, lets a property manage its information on several websites at once. The API set is broad. It covers rates and availability, reservations, prices, guest reviews, reporting, content, photos, guest messages, performance data, onboarding for Payments by Booking.com, promotions, facilities, property settings and Request to Book (Connectivity APIs documentation (Booking.com Developers)).
Requests travel in three formats: OTA XML, the OpenTravel Alliance schema in version 2003B; B.XML, Booking.com's own XML schema; and JSON. Booking.com advises providers not to mix OTA and B.XML requests in the same process (Connectivity APIs documentation (Booking.com Developers)).
Selling a room starts with the Rates & Availability API, which sets inventory, pricing and restrictions for each of a property's rooms (Rates & Availability (Booking.com Developers)). Bookings flow back the other way through a queue. Booking.com collects every new, modified and canceled reservation in a dedicated queue, and the provider retrieves and processes them periodically, which makes it a pull model: the provider collects bookings on its own schedule. Each reservation also has a deadline. The provider must acknowledge it (in OTA) or retrieve it (in B.XML) within 30 minutes, and Connectivity Support can raise that window to 24 hours (Reservations API overview (Booking.com Developers)).
Why the Booking.com API matters for hotel distribution
Picking a channel manager decides how rates, availability and bookings move between a property and Booking.com.
The pool of providers is fixed for now. As of November 2026, Booking.com says it is pausing integrations with new connectivity providers until further notice, and the page does not say when the pause began (Connectivity Portal (Booking.com)).
Missed reservations are the costly failure. When a reservation is not acknowledged or retrieved in time, Booking.com forwards it to the property as an email, and staff must enter it in their own system by hand (Reservations API overview (Booking.com Developers)). Until someone does, the room can stay open for sale on other channels, which is how a double booking starts.
Connections also differ in scope. A property requests connection types from its provider. A provider can set up Reservations and Rates & Availability as its main offering through Connectivity Support, and it chooses which other types to offer, such as guest reviews, content, photos, promotions and property settings. A provider can also mark a connection type as mandatory, and a property that selects it cannot request the same connection type from another provider (Connectivity APIs documentation (Booking.com Developers)). Ask which connection types a provider offers, and which it marks as mandatory, before you connect.
Providers are also ranked. Premier status sits inside Booking.com's Connectivity Partner Program, which recognizes providers for technical performance, service quality and support to accommodation providers (Premier Connectivity Partner release (Hospitality Net, 2025)).
Booking.com Connectivity API compared with the Demand API and a channel manager
Booking.com runs two separate API families. The Connectivity APIs serve supply: they let software providers help property owners manage their properties on Booking.com (Booking.com for Developers). The Demand API serves the other side, helping partners offer Booking.com travel options, from stays to transportation and attractions, through their own platform. It is the API recommended for Managed Affiliate Partners (About the Demand API (Booking.com Developers)) (Demand API (Booking.com Developers)).
| Connectivity API | Demand API | Channel manager | |
|---|---|---|---|
| Who uses it | Connectivity Partners (software providers) | Partners offering Booking.com travel options on their own platform, recommended for Managed Affiliate Partners | Properties, as their link to Booking.com |
| What moves | Rates, availability, reservations, content, reviews and more, for properties listed on Booking.com | Booking.com stays, transportation and attractions offered to travelers on the partner's platform | The property's data, sent through the Connectivity APIs |
| Can a single property connect directly? | No | Not a supply tool | Yes, this is how a property connects |
Frequently asked questions
How do you get Booking.com API access?
How do you integrate with an OTA connectivity API?
How do you use an OTA connectivity API to load prices?
What happens if a channel manager misses a reservation?
Related terms
See all termsWhere Jetstream fits
Jetstream builds an AI channel manager that connects a property to the channels where guests book and keeps its rooms, rates and availability accurate on each one, managed from one place.