Booking.com API Explained: The Three Programs, Who Gets Access, and What Each Does

Search for the Booking.com API and you'll find partner portals describing what sound like completely different products.
That's because a single Booking.com API doesn't exist.
There are two official programs (the Connectivity API and the Demand API), plus content and review surfaces inside each, and every one of them has its own access rules.
None of them is a general-purpose public API.
Most people searching "booking.com api" actually want a fourth thing: pulling rates, availability, or reviews for any hotel programmatically.
The official programs weren't built for that job, and a hotel data API is the route that was.
That path is covered below.
Here's the short routing: property owners and channel managers need Connectivity, travel sellers and affiliates need Demand, and developers who need data need neither.

Key Takeaways

• "The Booking.com API" means three different things. The Connectivity API manages properties, the Demand API sells inventory, and content surfaces live inside both programs.
• No official program offers open data access. You can manage listings you operate and sell rooms that are bookable. Bulk data for arbitrary properties sits outside both.
• The Connectivity API is free for registered partners. It pushes rates and availability, receives reservations, and manages content. Software vendors go through a certification program.
• Demand API approval targets businesses with distribution. Established travel sites, apps with traffic, and TMCs clear the bar. Side projects rarely do.
• Third-party data APIs fill the data gap. Rates, availability, and full review objects for any public Booking.com property, with signup instead of an approval cycle.

The Three Booking.com API Programs at a Glance

Each program serves Booking.com's two-sided marketplace: supply on one side, demand on the other.
Reading data out at scale, for any property, serves neither side, which is why no program covers it.

The Booking.com Connectivity API: For Properties and Channel Managers

If you own or manage accommodation listed on Booking.com, this is your program.
The Connectivity API lets registered partners and their software providers manage listings programmatically.
What it covers:
- Push rates and availability from a PMS, channel manager, or revenue system
- Receive reservations, modifications, and cancellations into your software
- Manage room types, rate plans, property content, and photos
- Reply to guest reviews and handle guest messaging
- Run promotions and pull performance reporting for your own properties
Access is free for registered accommodation partners.
Software vendors (PMS and channel manager companies) go through Booking.com's connectivity partner program, which includes certification requirements; the current process and timeline live on the partner portal.
The scope boundary matters more than the feature list.
Everything in the Connectivity API operates on inventory you manage.
It returns nothing about competitor properties, market rates, or other hotels' reviews, and it has no bulk review-reading endpoint even for your own listings.
It's a management pipe for your own properties, and expecting market data from it is the single most common Booking.com API misunderstanding.

The Booking.com Demand API: For Travel Sellers and Affiliates

The Demand API is the current form of what many searchers still call the Booking.com affiliate API.
Approved partners search Booking.com's live inventory (properties, rates, availability), display it to travelers, send bookings back, and earn commission on completed stays.
Who actually gets access is the part that saves you a dead-end application.
Approval targets businesses with real distribution: established travel sites, apps with meaningful traffic, and travel management companies.
A side project or pre-launch startup rarely clears the bar.
What you can do with it:
- Live search and availability for bookable inventory
- Property content and review scores for display alongside offers
- Deep-link or API-based booking flows with commission attribution
The Demand API is shaped entirely around selling: search, display, book.
Rate intelligence, price history, and market analysis need stored, repeated, property-wide reads, and the program is built for live bookable display rather than analytical reuse.
Teams that try to run analytics through it end up fighting the product's shape the whole way.

What About Reviews, Content, and Data?

Put the two programs side by side and a pattern shows up: you can manage what's yours and sell what's bookable.
Extracting data at scale, for any property, for analysis, has no official home.
Reviews make the pattern concrete.
Connectivity partners can reply to reviews, and Demand partners receive review scores for display next to bookable offers.
Reading a property's reviews in bulk, with full text and metadata, has no official endpoint in either program; the full story is in our Booking.com reviews API guide.
Market data follows the same logic.
Booking.com shows partners some analytics inside the extranet UI, and it stays there: dashboard access with no API surface and no export.
That leaves a specific searcher stranded: the developer building rate monitoring, review aggregation, market analysis, or an AI travel tool.
The next two sections are for them.

The Unofficial Routes (and Their Problems)

Scraping booking.com directly is attempted constantly and works miserably.
The site runs aggressive bot detection, CAPTCHAs, and fingerprinting, and its markup changes frequently.
A production scraper against Booking.com is an ongoing engineering tax: proxy rotation, breakage monitoring, and re-parsing work that never ends.
API-marketplace wrappers are the same thing one layer removed.
Someone else's scraper with an SLA-shaped sticker on it, so you inherit their fragility and their outages without visibility into either.
For a one-off research pull, a scraper or a public dataset is genuinely fine.
For anything a business depends on daily, the maintenance burden and unpredictable breakage make both routes structurally wrong.

Getting Booking.com Data Without a Partner Agreement

Third-party hotel data APIs cover the gap the official programs leave open: structured data for any public Booking.com property, delivered as JSON, with no partner agreement or eligibility bar.
StayAPI is one example, and it returns Booking.com data alongside the same data from TripAdvisor, Expedia, Agoda, Airbnb, and Google's hotel results.
For Booking.com specifically, that means:
- Live room rates and availability for any property and date range
- Full review objects: the positive/negative comment split, sub-category scores, reviewer country
- Property details, photos, and facilities
- Search results by destination
The data is real-time: you make a request → you get what Booking.com currently shows.
Here's a call to the Booking.com hotel prices endpoint:

curl -X GET "https://api.stayapi.com/v1/booking/hotel/prices?hotel_id=346648&check_in=2026-10-12&check_out=2026-10-14&currency=USD" \
  -H "x-api-key: YOUR_API_KEY"

And the truncated response:

{
  "success": true,
  "hotel_id": "346648",
  "data": {
    "hotel": { "id": "346648", "name": "Angsana Laguna Phuket" },
    "pricing_summary": {
      "price_per_night": "$185",
      "price_per_night_value": 185.0,
      "total_price": "$370",
      "currency": "USD"
    },
    "rooms": [
      {
        "room_name": "Laguna Suite",
        "is_refundable": true,
        "breakfast_included": true,
        "total_price_value": 370.0
      }
    ],
    "is_soldout": false
  }
}

The reviews endpoint pairs with it, and the fields worth knowing across both:

Together the two endpoints cover the jobs the official programs can't: competitor rate monitoring, rate parity checking, review aggregation and sentiment analysis, market research, and AI agents that need live hotel lookups.
Plain terms: signup includes 50 free requests with no credit card, and there's no approval process.
For a one-time pull of a handful of properties, a manual export or a scraper may still be the cheaper move; the API earns its keep once the reads repeat.

Which Booking.com API Path Is Right for You?

The one-sentence version: if the data describes your own listings or rooms you're selling, Booking.com has a program for you, and if the data describes the market, a third-party data API (StayAPI among them) is the working route.

Getting Started

If your job landed in the data rows of the table, here's the practical path:
1. Sign up at stayapi.com: 50 free requests, no credit card.
2. Grab a hotel ID: paste any Booking.com property URL into the URL-to-ID endpoint, or preview a property's data first with the free Booking.com hotel details tool.
3. Make the first call: the prices endpoint with your dates, as shown above, then the reviews endpoint for the same property.
4. Automate it: a scheduled N8N or Make.com workflow appends each day's response to a sheet or database, no code required.
For portfolio-scale monitoring or a walkthrough, book a demo.

FAQ

Is there a public Booking.com API?

There's no general-purpose one.
Booking.com runs the Connectivity API (property management, for registered partners) and the Demand API (selling inventory, approval required).
Neither provides open data access for arbitrary properties.

How do I get a Booking.com API key?

Through one of the official programs: register as an accommodation partner for Connectivity, or apply and get approved as a demand partner.
There's no self-serve developer key for data access; for that job, third-party data APIs like StayAPI issue keys on signup.

Is the Booking.com API free?

Connectivity is free for registered partners, and Demand runs on commission instead of usage pricing.
Neither has per-request pricing in the usual developer sense, because neither is a general developer product.

Can I get Booking.com rates and reviews via API without being a partner?

Booking.com itself doesn't offer that.
Third-party data providers deliver rates, availability, and full review data for any public property as structured JSON; StayAPI covers Booking.com alongside 5 other platforms.

What is the Booking.com Connectivity API used for?

Managing your own listings programmatically: pushing rates and availability, receiving reservations, updating content, and replying to reviews.
Most properties use it indirectly through a PMS or channel manager built on top of it.