{
 "categories": [
  "platform"
 ],
 "deployment": "saas",
 "evidence": [
  {
   "date": "2026-10-16",
   "fact": "homepage",
   "note": "The authentication guide is Booking.com documentation for the Demand API.",
   "source": "https://developers.booking.com/demand/docs/development-guide/authentication",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "name",
   "note": "The OpenAPI page is titled Booking.com Demand API 3.2.",
   "source": "https://developers.booking.com/demand/docs/open-api/3.2/demand-api",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "vendor",
   "note": "The guide is published on developers.booking.com and tells partners to use the Affiliate Partner Centre.",
   "source": "https://developers.booking.com/demand/docs/development-guide/authentication",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "license",
   "note": "Access requires a partner account and an API user. The page does not describe a public unauthenticated tier. The API is commercial partner access.",
   "source": "https://developers.booking.com/demand/docs/development-guide/authentication",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "deployment",
   "note": "The 3.2 server URL is https://demandapi.booking.com/3.2. The API is hosted.",
   "source": "https://developers.booking.com/demand/docs/open-api/3.2/demand-api",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.exists",
   "note": "The page says the Demand API follows REST principles, returns JSON, and is called with HTTPS POST.",
   "source": "https://developers.booking.com/demand/docs/open-api/3.2/demand-api",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.kinds[0]",
   "note": "The page calls the interface RESTful and says responses are JSON.",
   "source": "https://developers.booking.com/demand/docs/open-api/3.2/demand-api",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.auth[0]",
   "note": "Every request sends Authorization Bearer with the API key token generated in the Affiliate Partner Centre.",
   "source": "https://developers.booking.com/demand/docs/development-guide/authentication",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.auth[1]",
   "note": "Every request also sends X-Affiliate-Id for the API user. A wrong affiliate or missing permission returns 403.",
   "source": "https://developers.booking.com/demand/docs/development-guide/authentication",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.coverage",
   "note": "Version 3.2 covers accommodations, car rentals, flights, and post-booking reporting. Endpoint permission still depends on the API user. Coverage is partial.",
   "source": "https://developers.booking.com/demand/docs/open-api/3.2/demand-api",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.api.docs",
   "note": "Opened as the current Demand API authentication guide.",
   "source": "https://developers.booking.com/demand/docs/development-guide/authentication",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.mcp.first_party",
   "note": "Booking.com documents the hosted MCP endpoint https://demandapi-mcp.booking.com/v1/sp/mcp/ on developers.booking.com.",
   "source": "https://developers.booking.com/mcp-server/docs/implementation-guide",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.mcp.verdict",
   "note": "The implementation guide is vendor documentation of the Demand MCP server, so the verdict is official.",
   "source": "https://developers.booking.com/mcp-server/docs/implementation-guide",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "modalities.data_access.export[0]",
   "note": "The OpenAPI page says the API returns JSON.",
   "source": "https://developers.booking.com/demand/docs/open-api/3.2/demand-api",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "verdict.scores.api",
   "note": "A versioned JSON API with bearer tokens and an affiliate ID is a usable production path. Partner approval and per-endpoint permission keep the score at 6.",
   "source": "https://developers.booking.com/demand/docs/development-guide/authentication",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "verdict.scores.mcp",
   "note": "The hosted MCP server is official and authenticated with the Demand credentials. The tool list is account-specific, so the score is 6.",
   "source": "https://developers.booking.com/mcp-server/docs/implementation-guide",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[0].url",
   "note": "Opened and verified as the current Demand API authentication guide.",
   "source": "https://developers.booking.com/demand/docs/development-guide/authentication",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[1].url",
   "note": "Opened and verified as the Demand API 3.2 OpenAPI page, including the production server URL.",
   "source": "https://developers.booking.com/demand/docs/open-api/3.2/demand-api",
   "tier": "declared"
  },
  {
   "date": "2026-10-16",
   "fact": "freshness.watch[2].url",
   "note": "Opened and verified as the current Demand MCP implementation guide.",
   "source": "https://developers.booking.com/mcp-server/docs/implementation-guide",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-10-16",
  "volatility": "high",
  "watch": [
   {
    "type": "docs",
    "url": "https://developers.booking.com/demand/docs/development-guide/authentication"
   },
   {
    "type": "docs",
    "url": "https://developers.booking.com/demand/docs/open-api/3.2/demand-api"
   },
   {
    "type": "mcp",
    "url": "https://developers.booking.com/mcp-server/docs/implementation-guide"
   }
  ]
 },
 "homepage": "https://developers.booking.com/demand/docs/development-guide/authentication",
 "id": "booking-demand-api",
 "license": "commercial",
 "modalities": {
  "agent_docs": {
   "llms_txt": "unknown"
  },
  "api": {
   "auth": [
    "bearer",
    "affiliate-id"
   ],
   "coverage": "partial",
   "docs": "https://developers.booking.com/demand/docs/development-guide/authentication",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": "unknown"
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [
    "json"
   ],
   "import": []
  },
  "extensibility": {
   "scripting": [],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": true,
   "third_party": [],
   "verdict": "official"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. This record is the Booking.com Demand API for affiliate partners. It is not the consumer website or the property extranet.\n",
   "ui_stack": [],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Booking.com Demand API",
 "platforms": [
  "web"
 ],
 "related": {
  "alternatives": [],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Booking.com",
 "verdict": {
  "best_path": "api",
  "scores": {
   "api": 6,
   "cli": null,
   "computer_use": null,
   "integrations": null,
   "mcp": 6,
   "overall": 6,
   "rpa": null
  },
  "search": {
   "description": "Demand API v3 uses a bearer key and an affiliate ID. Booking.com also hosts an MCP endpoint whose tools depend on the affiliate account.",
   "title": "Booking.com Demand API is a partner REST API"
  },
  "summary": "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.\n"
 }
}