Booking.com Demand API is a partner REST API

The Booking.com Demand API is automatable today through Demand API v3. Every request sends Authorization Bearer with an API key generated in the Affiliate Partner Centre, and X-Affiliate-Id with the affiliate ID. Production calls use HTTPS POST to https://demandapi.booking.com/3.2. The sandbox host is https://demandapi-sandbox.booking.com. The authentication guide says a missing or invalid API user returns 401, and an authenticated user without endpoint permission returns 403. An account can hold two active keys so one can be rotated. Partner Centre access itself can require an account manager. Booking.com also documents a hosted MCP endpoint at https://demandapi-mcp.booking.com/v1/sp/mcp/. Each request sends x-booking-affiliate-id and x-booking-authorization with the Demand API key and no Bearer prefix. The guide says the tool list depends on the affiliate configuration. Example names include accommodations_search, cars_search, and flights_search, and the page says tools/list is authoritative. A 429 uses Retry-After. This record is the partner Demand API. Connector catalogs were not opened. Computer-use viability is unassessed. The API and the MCP server each score 6 because both are documented and both require an approved affiliate account. The API is the best path because any HTTPS client can call it, while the MCP tool list changes with the affiliate configuration.

Best path today: api · Overall automatability: 6/10