Booking Holdings
Booking Holdings is the world's leading provider of online travel and related services, operating a portfolio of brands including Booking.com, Priceline, Agoda, KAYAK, OpenTable, Rentalcars.com, Rocketmiles, FareHarbor, HotelsCombined, Cheapflights, and Momondo. The company connects travelers with accommodations, flights, rental cars, restaurant reservations, and travel experiences worldwide.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Booking Holdings the way a machine reads it — 94 machine-readable artifacts across 9 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Booking Holdings scores 46.2/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Booking Holdings
Each block below is one kind of artifact we hold for Booking Holdings. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Booking Holdings Accommodations API
This API collection is specific for the stay part of the connected trip. Use these endpoints to search for stays such as hotels and apartments, check availability, ret...
Booking Holdings Attachments API
Provides endpoints for handling message attachments. Use these endpoints to upload and download images shared within conversations.
Booking Holdings Cars API
This API collection is specific to the car rentals part of the connected trip. Use these endpoints to search for car rentals, check car details and look for depots and...
Booking Holdings Common/languages API
Provides a list of supported language codes for use in API requests.
Booking Holdings Common/locations API
Provides identifiers for a wide range of geographical locations, including airports, countries, cities, and regions. Use these identifiers to construct your requests. ...
Booking Holdings Common/payments API
Provides generic payment-related endpoints, including supported currencies and payment types.
Booking Holdings Conversations API
Provides endpoints to retrieve and manage messaging conversations. Use these endpoints to list conversations, fetch conversation details, and track updates.
Booking Holdings Messages API
Provides endpoints for two-way post-booking communication between guests and properties. Use these endpoints to send and retrieve messages, exchange images, and check ...
Booking Holdings Orders API
Enables management of booking orders within the Demand API. Use these endpoints to preview and create new orders, check order details, cancel or modify existing orders...
Scroll within the panel for all 9 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Booking Holdings Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Booking Holdings Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Booking Holdings API Rules
SPECTRALBooking Holdings API Rules
SPECTRALBooking Holdings API Rules
SPECTRALJSON Schema 25
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccommodationsAvailabilityInput
JSON SCHEMAAccommodationsAvailabilityProductOutput
JSON SCHEMAAccommodationsDetailsDataOutput
JSON SCHEMAAccommodationsDetailsInput
JSON SCHEMAAccommodationsDetailsRoomOutput
JSON SCHEMAAccommodationsLocationOutput
JSON SCHEMAAccommodationsPoliciesOutput
JSON SCHEMAAccommodationsReviewOutput
JSON SCHEMAAccommodationsReviewsScoresOutput
JSON SCHEMAAccommodationsSearchInput
JSON SCHEMAAccommodationsSearchProductOutput
JSON SCHEMAAirportsInput
JSON SCHEMACitiesInput
JSON SCHEMAConstantsDataOutput
JSON SCHEMACountriesInput
JSON SCHEMADistrictsInput
JSON SCHEMAFlightsOutput
JSON SCHEMALandmarksInput
JSON SCHEMAOrderCreateBookerInput
JSON SCHEMAOrderCreatePaymentInput
JSON SCHEMAOrderDetailsBookerOutput
JSON SCHEMAOrderDetailsDataOutput
JSON SCHEMAOrdersPreviewProductOutput
JSON SCHEMARegionsInput
JSON SCHEMATraderOutput
JSON SCHEMAScroll within the panel for all 25 ·
JSON Structure 25
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Demand Api Accommodations Availability Input Structure
JSON STRUCTUREDemand Api Accommodations Details Data Output Structure
JSON STRUCTUREDemand Api Accommodations Details Input Structure
JSON STRUCTUREDemand Api Accommodations Details Room Output Structure
JSON STRUCTUREDemand Api Accommodations Location Output Structure
JSON STRUCTUREDemand Api Accommodations Policies Output Structure
JSON STRUCTUREDemand Api Accommodations Review Output Structure
JSON STRUCTUREDemand Api Accommodations Search Input Structure
JSON STRUCTUREDemand Api Airports Input Structure
JSON STRUCTUREDemand Api Cities Input Structure
JSON STRUCTUREDemand Api Constants Data Output Structure
JSON STRUCTUREDemand Api Countries Input Structure
JSON STRUCTUREDemand Api Districts Input Structure
JSON STRUCTUREDemand Api Flights Output Structure
JSON STRUCTUREDemand Api Landmarks Input Structure
JSON STRUCTUREDemand Api Order Create Booker Input Structure
JSON STRUCTUREDemand Api Order Create Payment Input Structure
JSON STRUCTUREDemand Api Order Details Booker Output Structure
JSON STRUCTUREDemand Api Order Details Data Output Structure
JSON STRUCTUREDemand Api Orders Preview Product Output Structure
JSON STRUCTUREDemand Api Regions Input Structure
JSON STRUCTUREDemand Api Trader Output Structure
JSON STRUCTUREScroll within the panel for all 25 ·
Examples 25
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 25 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Booking Holdings — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/booking-holdings · machine-readable index on apis.io