Booking.com API: Official Options vs Third-Party Data APIs

A Booking.com API is one of three very different things: the official Connectivity API (for PMS, channel managers and other connectivity providers that push rates and inventory into Booking.com), the official Demand API (for managed affiliates that search and sell Booking.com inventory), or a third-party data API that returns the rates, availability, reviews and property details you can see on Booking.com as structured JSON, with no partner status required. Veetal Connect API belongs to the third group: it delivers Booking.com hotel data on demand (Real Time layer) and as scheduled comp-set reports with a parity score (Feed layer). This guide explains what each option does, who qualifies, and how to choose.

Why "Booking.com API" means three different products

If you search for "booking api" or "booking.com data api", you are usually trying to do one of these jobs:

• Distribute your own property on Booking.com (send rates, availability, receive reservations).
• Sell Booking.com inventory to your users and earn a commission.
• Read what Booking.com shows for any hotel: prices, room types, availability, guest score, reviews, photos, facilities.

The first two are covered by Booking.com's official programs, each gated behind a partner contract. The third is what data APIs exist for. Knowing the boundary saves weeks of applying to the wrong program.

The official Booking.com APIs

Connectivity API: for PMS, channel managers and connectivity providers

The Booking.com Connectivity APIs are a suite that lets a software provider manage its connected properties on Booking.com: Rates & Availability, Reservations, Content, Photos, Guest Review, Messaging, Reporting, Promotions, Facilities, Property and Market Insights, among others. The intended audience is a company offering a "one-stop shop" to hotels it already serves, typically a PMS or channel manager.

Key characteristics:

• Scope: only the properties connected through your platform. You cannot query a competitor's rates or a hotel you do not serve.
• Direction: mostly write (push rates, restrictions, content) plus reservation retrieval. A distribution tool, not a market-intelligence feed.
• Onboarding: you apply as a connectivity partner, support the available API functions, load a full year of rates and availability per property and give hotels an interface to manage rooms and rates.
• Minimum requirements to remain a partner, per the partner programme page: under 5% reservation fallbacks per month, under 10% error rate on Rates & Availability calls, at least 3,000 bookings per programme year and a daily average of at least 250 bookable listings.
• Program status: at the time of writing, the connectivity portal states that Booking.com is pausing integrations with new connectivity providers until further notice.

Demand API: for managed affiliate partners

The Booking.com Demand API is the successor of the old affiliate API. It lets an affiliate search accommodations, retrieve availability and prices, and complete bookings so that its users book Booking.com inventory and the affiliate earns a commission.

Its prerequisites are explicit: you must be registered as a Booking.com Managed Affiliate Partner, get access to Partner Centre through a Booking.com account manager after signing the contract, and generate an API key and an X-Affiliate-Id. Managed status is granted to partners with meaningful booking volume; it is not a self-serve sign-up.

In practice, the Demand API is built for selling, not for monitoring: the data powers your booking flow and is not meant to be forwarded to other companies, and there is no concept of "my hotel vs my competitors". You query inventory as a seller, not as a revenue manager.

What neither official API is designed for

Both official programs solve a distribution problem. They are not designed for these common needs:

1. Rate shopping: what does my comp set charge on Booking.com for next weekend?
2. Reputation monitoring: a hotel's review score and recent guest comments in a dashboard.
3. Price comparison products that show Booking.com alongside Expedia, Hotels.com or Google Hotels.
4. Availability and length-of-stay analysis for a hotel you do not operate.
5. Market research: how many hotels a destination lists, at what price band, on a given date.

For those, you need a data API.

Third-party Booking.com data APIs

A Booking.com data API is a read-only service that returns what the Booking.com property page and search results display, as structured JSON. You identify a hotel by URL, Booking.com hotel ID or your own slug, pass the stay parameters, and receive prices, room types, meal plans, cancellation policies, guest scores, reviews and property details. No partner contract, no minimum booking volume.

Veetal Connect API implements this with two complementary layers:

• Real Time: on-demand requests against any hotel, returning live data in seconds. Consumes credits per request; responses can be cached from 0 to 24 hours, and no_cache=true forces fresh data.
• Feed: you register your hotels and their competitor set once, imports run on a schedule, and the API serves pre-processed reports: daily rates by comp set, a parity score per competitor, stored reputation and reviews, destination listings. Reads are cheap and the history is kept.

Comparison table: official Connectivity vs official Demand vs data API

What Veetal Connect API returns from Booking.com

All Booking.com endpoints live under /v2/real-time/... (live) and /v2/feed/... (scheduled). A hotel is referenced either by the slug of one of your registered accommodations, or by booking-id (the numeric Booking.com hotel ID) for a hotel that is not yours. Full documentation is on the Booking.com data source page.

Real Time endpoints

• Room rates for a stay — GET /v2/real-time/accommodation/{slug}/rate/booking/{checkin}/{checkout}/{adults}. Every room rate shown for the stay: room type, price per night and total, capacity, meal plan, cancellation policy, plus Genius and mobile pricing on request. Filters: currency, childs, meal_plan, cancellation. A booking-entity variant covers hotels outside your account. Dataset: hotel rates.
• Day-by-day availability — GET /v2/real-time/accommodation/{slug}/availability/booking/{from_date}/{to_date}/{adults}. Evaluates each day of the range individually (up to 365 days): the raw material for length-of-stay and pickup analysis. Dataset: availability.
• Reviews — GET /v2/real-time/{reference_type}/{identifier}/reviews/booking. Paginated reviews with score, positive and negative text, traveler type, stay date, room type, language and management response; sort, language, from_date and limit (1 to 1,000). Dataset: reviews.
• Reputation — GET /v2/real-time/{reference_type}/{identifier}/reputation/booking returns the overall score, review count and category averages; the reputation-compset/booking variant returns them for your hotel and its whole comp set in one call.
• Property details — GET /v2/real-time/{reference_type}/{identifier}/accommodation-data/booking. Basic info, location, stars, review score and count, photos, facilities, room types and open/closed status. Dataset: hotel detail.
• Location search — GET /v2/real-time/location-search/{location_search_id}/booking/{target_date}. Runs a destination search with your configured filters (stars, board, distance from centre, minimum score) and returns availability and pricing for every hotel listed. Dataset: Booking location listing.

Feed endpoints (scheduled, comp set aware)

GET /v2/feed/accommodation/{slug}/rate serves the daily rate report for your hotel and its comp set (filterable by OTA, occupancy, board, cancellation policy, Genius and device); /parity serves the parity score against each competitor over a date range; /reputation and /reviews serve the stored reputation data; and GET /v2/feed/location-search/{location_search_id}/{target_date}/booking-location-search serves the stored destination listing, where one run of 192 hotels costs 0.32 credits.

Example request

Live Booking.com rates for a registered hotel, two adults, breakfast included, prices in EUR:

curl "https://api.veetal.app/v2/real-time/accommodation/vincci-mae/rate/booking/2026-11-12/2026-11-14/2?currency=EUR&meal_plan=breakfast" \
  -H "VEETAL-API-KEY: your_api_key"

Abbreviated response:

{
  "status": "success",
  "accommodation": { "name": "Vincci Mae", "slug": "vincci-mae", "bookingId": 1956465, "stars": 5 },
  "search": { "checkin": "2026-11-12", "checkout": "2026-11-14", "nights": 2, "adults": 2, "currency": "EUR", "meal_plan": "breakfast" },
  "rates": [
    {
      "room_type": "Vincci room",
      "price_per_night": 189.5,
      "price_total": 379,
      "capacity": 2,
      "meal_plan": { "breakfast": true, "half_board": false, "full_board": false, "all_inclusive": false },
      "cancellation": { "free_cancellation": true }
    }
  ]
}

When no rate is returned, a reason field (no_availability, no_meal_plan_match, no_cancellation_match) lets your pipeline tell a sold-out date from a filter mismatch. You can try the call without code in the first Real Time call playground.

Data API vs maintaining your own parser

Teams that cannot join an official program sometimes write their own HTML parser. The trade-offs are purely technical, and they add up:

• Output: raw HTML to parse and clean, versus normalized JSON with typed fields and one schema across OTAs.
• Layout changes: every redesign breaks your extraction until someone fixes it; a provider absorbs that work.
• Scale: retries, queueing and timeouts are your problem, versus cached responses, paginated endpoints and predictable latency.
• Comp-set logic: you build it, versus managed comp sets, a parity score and scheduled imports out of the box.

We covered this in depth in hotel API vs web scraping; the short version is that a parser is a project and an API is a dependency.

The scale of Booking.com data

So many teams need this data because Booking.com is where a large share of hotel demand is priced and reviewed. According to the Booking Holdings factsheet, 1.2 billion room nights were booked across the group in 2025, up 8% year over year, on more than 31 million reported listings on Booking.com. For most markets, a hotel's rate and score there are its public price and public reputation.

Use cases by team

Rate shopping for revenue teams and RMS vendors

Register your hotels and comp sets, schedule imports, read the Feed rate report every morning, and call the Real Time rate endpoint when you need a fresh check on a specific date. The live rate shopper recipe shows the on-demand pattern and the competitor rate grid turns it into a comp-set grid for one stay. Background reading: real-time hotel prices API.

Reputation and guest intelligence

Reputation tools pull the Booking.com score, review count and recent reviews per property, then run sentiment or topic analysis on the text. The Booking reviews without scraping recipe covers the reviews endpoint, pagination and from_date incremental pulls; extract Booking reviews via API covers the analysis side.

Price comparison and travel products

A comparator needs a destination listing with prices per hotel for a target date, then a per-hotel drill-down. Location search provides the listing, the rate endpoint the room-level detail, and the parity endpoint (GET /v2/real-time/{reference_type}/{identifier}/parity/{checkin}/{checkout}/{adults}) the same stay on the other OTAs via Google Hotel Ads.

Worked example. A revenue-management agency runs 40 independent hotels in Spain and registers each one with a comp set of 5 to 8 competitors. Every night the Feed imports rates for the next 90 days; the morning report shows, per hotel, its position against the comp set and its parity score. When a hotel asks why a competitor dropped 20% for the trade-fair weekend, the analyst calls the Real Time rate endpoint for both hotels and answers in under a minute. No partner application, no parser to maintain, and a per-hotel cost measured in credits, as described on the pricing page.

Frequently asked questions

Does Booking.com have a public API? Not in the open, self-serve sense. Booking.com offers two official programs, the Connectivity API for providers that manage connected properties and the Demand API for managed affiliate partners, both requiring a contract and approval. Reading rates, availability or reviews for arbitrary hotels is done through third-party data APIs such as Veetal Connect API.

What is the difference between the Booking.com Connectivity API and the Demand API? The Connectivity API pushes rates, availability and content for properties you connect and retrieves their reservations; it is for PMS and channel managers. The Demand API lets an affiliate search and book Booking.com inventory to sell it. Neither returns competitor data.

Can I get Booking.com rates for hotels that are not mine? Yes, with a data API. Veetal Connect API accepts a Booking.com hotel ID (booking-id) or a Booking entity reference for any listed hotel, and competitors can be added to a managed comp set for scheduled imports.

Is there a Booking.com reviews API? Through Veetal Connect API, GET /v2/real-time/{reference_type}/{identifier}/reviews/booking returns paginated reviews with score, positive and negative text, traveler type, stay date, language and management response, sortable and filterable by date and language. The reputation endpoint returns the aggregate score and review count.

How fresh is the data? Real Time endpoints fetch live data per request, typically in 5 to 15 seconds for rates and property details, longer for full review histories or destination searches. Caching is configurable from 0 to 24 hours and no_cache=true forces fresh data. Feed endpoints return the latest scheduled import; older imports are addressable by import_id.

How much does a Booking.com data API cost? Veetal Connect API uses credits: Real Time calls consume credits per request, Feed reads are cheap, and Account endpoints are free. The free trial includes 1,000 credits without a card, and the pricing page lists the plans.

Which other sources are available alongside Booking.com? Expedia, Hotels.com, Google Hotels (with multi-OTA parity through Google Hotel Ads), Airbnb and TripAdvisor reviews, all under the same /v2 schema.

Start with 1,000 free credits

If your job is distributing your own property, apply to the official Booking.com programs. If your job is reading Booking.com rates, availability, reviews or property data for any hotel, create a free account with 1,000 credits, no card required, register a hotel and its comp set, and run the rate endpoint from the playground today.