Seamlessly incorporate Booking.com inventory into your metasearch engine.
Metasearch Connect API is dedicated for integration of metasearch engines. Initially, it is made compatible with the Demand API to simplify the transition for metasearch providers that currently use it. Later, Metasearch Connect API will offer a new set of endpoints that are tailored for metasearch-specific use cases.
The transition will be performed in two phases:
- During phase 1, the changes you will need to make will be minimal: switching to a new API address and implementing a new token-based authentication mode. However, this will require extensive monitoring on our end; therefore, the process will be coordinated via account managers.
- Phase 2 may require some more effort on your part, but it will not be purely a technical change. New endpoints will also offer more features specific to metasearch engines and extend to our inventory in other vertical sectors of the travel market (e.g., flights).
The Connect API endpoints are currently grouped into two main collections, also referred to as API layers. Each collection provides a different area of functionality.
The endpoints in this layer are grouped under the base path /demand-api-v2-compatible and use the interface compatible with Demand API V2. These endpoints are meant for easy transition in the short term and provide functionality specific to the accommodations sector of the travel market.
The Demand API compatibility endpoints exist only to ease the transition and will be used for that purpose only. Over time, we will add new collections of endpoints with a different interface, and we will ask all metasearch providers to migrate to the latest version.
Alongside the compatibility layers, the Connect API is starting to offer purpose-built endpoints designed specifically for metasearch use cases (rather than for Demand API compatibility):
- List accommodation properties (
POST /inventory/properties) — streams the full Booking.com accommodation-property inventory (a property is a place to stay — a hotel, apartment, hostel, and so on; static content such as names, location, ratings, policies, images, and booking links) as a newline-delimited JSON (NDJSON) feed, with support for full and incremental delta syncs. See the API Reference for the request parameters, response schema, and streaming protocol. - Conversions (
POST /reports/conversions) — returns conversion data for bookings within a specified date range. Available to selected accounts based on contractual agreements. See the API Reference.