Search for hotel availability and understand the Booking.com Demand API booking fundamentals
domain: developers.booking.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with the Booking.com Demand API (also called the Affiliate API or distribution API) using your affiliate credentials via the specified authentication mechanism
Call the block availability endpoint with hotel ID or search criteria, check-in/check-out dates, and occupancy to retrieve available room blocks and prices
Parse the availability response for room type identifiers, meal plan codes, cancellation policy type, and price components including tax and fee breakdowns
Select a block and call the pre-booking or reservation endpoint to reserve the room; capture the reservation token returned for use in the final booking step
Complete the booking by submitting guest details, contact information, and payment data; retrieve the booking number from the confirmation response for the guest and for reconciliation
Known gotchas
Booking.com Demand API access is tiered and not universally available; confirm your affiliate or partner agreement grants access to transactional booking endpoints, not just search
Cancellation policy codes from Booking.com must be decoded against their policy taxonomy — do not display raw codes to users; translate them to plain-language terms
Booking.com pricing may include non-refundable value-added tax collected at the property; verify whether displayed prices are inclusive or exclusive of local taxes before presenting to the user
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?