Booking.com API

Name: Booking.com API
Brand: Booking.com API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder ManagementapiKey5 EndpointsREST

For Agents

Search hotels, check availability, and create accommodation bookings on Booking.com programmatically.

Install Jentic One Beta

Connect the Booking.com API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Booking.com API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Booking.com API.

Search the Booking.com inventory for hotels matching a destination and date range

Retrieve full hotel details including room types and amenities for a given hotel ID

Check room availability and price for a specific hotel before booking

GET STARTED

Start building with Booking.com API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Booking.com API, keeping it validated and agent-ready. Booking.com is one of the largest accommodation marketplaces and exposes an API for searching hotels, checking availability, and creating bookings. This spec covers a focused set of five core endpoints: hotel search, hotel detail lookup, availability check, booking creation, and booking retrieval. Use it to surface accommodation options inside your own travel product, confirm rooms before booking, and place reservations on behalf of a traveller.

Use Cases

Patterns agents use Booking.com API for, with concrete tasks.

★ Embedded Accommodation Search in a Travel App

Surface Booking.com hotel inventory inside your own travel planning product so users can search and book without leaving the app. GET /hotels/search returns matching hotels for a destination and date range, and GET /hotels/{hotelId} returns the detail used in the listing page. Removes the need to maintain your own accommodation supply pipeline.

GET /hotels/search?destination=Lisbon&check_in=2026-07-12&check_out=2026-07-15&guests=2

Availability-Confirmed Booking Flow

Confirm that a hotel still has rooms at the quoted price before charging the traveller, then place the booking. GET /availability checks live availability for the chosen hotel and dates, and POST /bookings completes the reservation. Avoids the bad customer experience of a booking failure after payment is captured.

GET /availability for hotelId 12345 and dates 2026-07-12 to 2026-07-15, then POST /bookings if available

Itinerary Sync and Receipts

Pull booking detail back into the user's account or a corporate travel system using GET /bookings/{bookingId} once a reservation has been made. Useful for travel apps that consolidate itineraries or expense systems that need to attach receipts. Eliminates the need for the traveller to manually forward confirmation emails.

GET /bookings/BK-998877 and write the result to the trip itinerary record

AI Agent Travel Booking Assistant

An AI travel agent uses Jentic to discover Booking.com operations, searches accommodation, confirms availability, and places bookings on behalf of a user from a single natural-language request. The Booking.com API key lives in the Jentic vault so the agent never sees the raw key. Replaces a multi-step manual booking flow with a single search-load-execute cycle per action.

Search Jentic for 'create a Booking.com hotel booking', load the operation, and execute it for the chosen hotel and stay dates

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for booking.

METHOD

PATH

DESCRIPTION

GET

/hotels/search

Search hotels by destination and dates

GET

/hotels/{hotelId}

Retrieve hotel details

GET

/availability

Check availability for a hotel and date range

POST

/bookings

Create a booking

GET

/bookings/{bookingId}

Retrieve a booking

GET

/hotels/search

Search hotels by destination and dates

GET

/hotels/{hotelId}

Retrieve hotel details

GET

/availability

Check availability for a hotel and date range

POST

/bookings

Create a booking

GET

/bookings/{bookingId}

Retrieve a booking

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Booking.com API keys are stored encrypted in the Jentic vault (MAXsystem) and exchanged for scoped, short-lived access at execution time. The raw partner key never enters the agent's prompt context or logs.

Intent-based discovery

Agents search Jentic with intents like 'search Booking.com hotels' or 'create a hotel booking' and Jentic returns the matching operation with its input schema, removing the need to read the partner reference docs.

Time to first call

Direct Booking.com integration: 1-2 weeks for partner onboarding, auth, search, and booking flows. Through Jentic: under an hour with search, load, and execute against the existing partner credential.

FAQs

Specific to using Booking.com API through Jentic.

Why is there no official OpenAPI spec for Booking.com API?

Booking.com does not publish an OpenAPI specification — its developer portal documents the API in HTML reference. Jentic generates and maintains this spec so AI agents and developers can call Booking.com via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Booking.com API use?

Booking.com uses an API key sent in the Authorization header. Through Jentic the key is held in the encrypted vault and only a scoped, short-lived token reaches the agent context — the raw partner key never enters logs or prompts.

Can I create a hotel booking through the Booking.com API?

Yes. POST /bookings with the hotelId, check-in and check-out dates, and guest details. We recommend calling GET /availability first to confirm the room is still available at the quoted price before placing the booking.

How do I search hotels by destination through Jentic?

Search Jentic for 'search Booking.com hotels', load the GET /hotels/search operation schema, then execute it with the destination and date range. The response returns matching hotels with their IDs you can pass to GET /hotels/{hotelId}.

What are the rate limits for the Booking.com API?

Formal rate limits are not declared in this OpenAPI specification. Booking.com partner programs typically apply per-second and per-day caps — back off on HTTP 429 responses and avoid repeatedly polling /availability for the same hotel.

Can I retrieve a booking after it has been created?

Yes. GET /bookings/{bookingId} returns the booking detail, including stay dates, guest count, and status. Useful for itinerary sync or expense reporting.