{ "data": { "a": { "slug": "booking-demand-api", "name": "Booking.com Demand API", "vendor": "Booking.com", "vendorUrl": "https://developers.booking.com/demand/docs", "kind": "http-api", "category": "travel", "summary": "Booking.com's inventory for affiliates, from content-only through search, look and book to order management, across accommodation, cars, attractions and transfers.", "url": "https://www.anchorterminal.com/tools/booking-demand-api", "markdownUrl": "https://www.anchorterminal.com/tools/booking-demand-api.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/booking-demand-api.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/booking-demand-api.json", "transports": [ "http" ], "remoteUrl": "https://demandapi-sandbox.booking.com/3.2", "packages": [], "auth": "api-key", "authNotes": "`Authorization: Bearer \u003capi key\u003e` plus `X-Affiliate-Id: \u003caid\u003e` on every call. The key is generated once in the Affiliate Partner Centre and shown in full only at creation. The same key and affiliate ID work on the sandbox host; the production host is in the API reference behind partner sign-in.", "pricing": "byo-plan", "pricingNotes": "No published prices. Access needs registration as a Booking.com Managed Affiliate Partner with Partner Centre access, and the commercial terms (commission on completed stays) are in that partner agreement rather than the docs. Sandbox and test calls are free once you have a key (https://developers.booking.com/demand/docs/getting-started/try-out-the-api).", "priceSummary": "Your plan", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://developers.booking.com/demand/docs", "capabilities": [ "travel.stays", "travel.booking", "travel.changes", "travel.search" ], "tags": [ "hosted", "closed-source", "enterprise", "partner-only", "eu" ], "graded": true, "anchor": { "graded": true, "score": 38.1, "grade": "E", "agentReady": false, "rank": 697, "ranked": true, "rankOf": 722, "categoryRank": 10, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 28, "payments": 5, "reliability": 33, "schema": 57, "security": 36, "transparency": 49 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Search, look and book plus order management on Booking.com's accommodation inventory. Managed Affiliate Partner status required; no self-serve key.", "bestFor": "An affiliate that already holds Booking.com credentials and wants its agent to book stays, cars and attractions.", "strengths": [ "Search, look and book plus order management on Booking.com's accommodation inventory", "Cars, attractions and transfers under the same key", "Three versions with stated status (3.2 stable, 3.1 supported, 3.2-Beta) and a dated changelog", "Sandbox on the same credentials as production, 50 requests a minute", "Key handling guidance in the docs (shown once, rotate yearly, revoke on compromise)" ], "weaknesses": [ "Managed Affiliate Partner status required; no self-serve key", "No published prices, SLA, status page or production rate limits beyond cars search", "No downloadable OpenAPI file, llms.txt, SDKs or MCP server", "Sandbox payment tests need a real card with temporary charges, and only accommodation books there", "One changelog entry in 2026 that we could read" ], "agentNotes": [ "Send both `Authorization: Bearer` and `X-Affiliate-Id`, or the call fails on auth", "Stay under 50 requests a minute in the sandbox and back off exponentially on 429", "Only accommodation flows book in the sandbox; cars and attractions won't", "Store the key at creation, it's never shown again", "Use filters and pagination on search to keep payloads small" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 1.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 38.1 } ], "editorialScores": { "ergonomics": 53, "maintenance": 28, "payments": 5, "reliability": 33, "schema": 57, "security": 36, "transparency": 28 }, "provenanceScore": 69 }, "connect": { "http": "curl -X POST https://demandapi-sandbox.booking.com/3.2/accommodations/search \\\n -H \"Authorization: Bearer $BOOKING_API_KEY\" -H \"X-Affiliate-Id: $BOOKING_AFFILIATE_ID\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"booker\":{\"country\":\"gb\",\"platform\":\"desktop\"},\"checkin\":\"2026-11-10\",\"checkout\":\"2026-11-12\",\"city\":-2601889,\"guests\":{\"number_of_adults\":2,\"number_of_rooms\":1}}'" }, "letme": { "capability": "https://letme.dev/travel.stays", "tool": "https://letme.dev/booking-demand-api" }, "area": "domain-data", "provenance": { "legalEntity": "Booking.com B.V.", "domain": "booking.com", "domainRegistered": "1998-04-17", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://admin.booking.com/hotel/hoteladmin/privacy.html", "statusPage": "", "changelog": "https://developers.booking.com/demand/docs/whats-new/changelog", "securityTxt": "none", "checked": "2026-10-01", "notes": [ "The partner privacy statement names Booking.com B.V., Amsterdam, as the responsible entity; the affiliate terms sit behind Partner Centre sign-in and weren't readable.", "www.booking.com blocks crawlers by robots.txt, so the consumer privacy and terms pages weren't checked.", "developers.booking.com/.well-known/security.txt returned 404 on 30 September.", "The developer portal has a dated changelog, newest entry August 2026." ], "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/booking-demand-api.json", "live": { "slug": "booking-demand-api", "probe": { "target": "https://demandapi-sandbox.booking.com/3.2", "method": "get", "lastAt": "2026-10-08T21:53:17.814656616Z", "lastOk": true, "lastStatus": 401, "lastMs": 119, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 98, "p95ms24h": 146, "samples24h": 270, "samples30d": 1962, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 246, "ok": 246 } ] }, "securityTxt": { "url": "https://booking.com/.well-known/security.txt", "state": "expired", "expires": "2025-12-31T23:00:00.000Z", "checkedAt": "2026-10-08T15:38:35.024960831Z" }, "domain": { "domain": "booking.com", "registered": "1998-04-17", "source": "https://rdap.verisign.com/com/v1/domain/booking.com", "checkedAt": "2026-10-04T13:09:07.505050512Z" }, "pages": [ { "url": "https://developers.booking.com/demand/docs/whats-new/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:17:26.857706046Z", "changedAt": "2026-10-05T15:54:56.940826217Z", "fingerprint": "2da8ad72216d" }, { "url": "https://admin.booking.com/hotel/hoteladmin/privacy.html", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:14:57.673604687Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f2b0aca34b64" } ], "updatedAt": "2026-10-08T21:53:17.814656616Z" } }, "answer": "Travelport TripServices APIs scores 45.9 (E) on agent readiness against Booking.com Demand API's 38.1 (E), and leads in 5 of 7 scored categories. Booking.com Demand API leads on reliability.", "b": { "slug": "travelport", "name": "Travelport TripServices APIs", "vendor": "Travelport", "vendorUrl": "https://www.travelport.com", "kind": "http-api", "category": "travel", "summary": "Travelport TripServices is a set of REST JSON APIs on the Travelport global distribution system. It searches, prices, books, tickets, exchanges and cancels flights, books and cancels hotel stays, and authorises payment cards, for travel sellers under contract.", "url": "https://www.anchorterminal.com/tools/travelport", "markdownUrl": "https://www.anchorterminal.com/tools/travelport.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/travelport.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/travelport.json", "license": "Proprietary service under a Developer Contract and Travelport's API and SDK Terms of Use", "transports": [ "http" ], "remoteUrl": "https://api.travelport.net", "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 with the password grant. A POST to `https://auth.travelport.net/oauth/token` (pre-production `https://auth.pp.travelport.net/oauth/token`) with `username`, `password`, `client_id` and `client_secret` returns a Bearer token valid for 24 hours. Every call also carries `XAUTH_TRAVELPORT_ACCESSGROUP` or `TVP-PCC-CORE`, which sets the point of sale and the content the caller may reach. Trial credentials are requested on a form at my.travelport.com and arrive by email. Production credentials come after a contract through sales and certification, and are managed in the Credential Access Manager in MyTravelport, which creates, rotates and disables primary and managed identities. No scopes were found.", "pricing": "paid", "pricingNotes": "No public price. The API and SDK Terms of Use say charges are set in each Developer Contract and invoiced monthly, and the docs send new customers to sales. A trial with no payment exists for building against realistic air shopping, requested through a form that asks for a name, work email and company. Production access is per contracted API after certification (checked 2026-10-08).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer portal, the three OpenAPI files or the terms (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developer.travelport.com/", "llmsTxt": "https://developer.travelport.com/llms.txt", "openapi": "https://developer.travelport.com/_bundle/apis/flights/@11.36/index.yaml", "capabilities": [ "travel.flights", "travel.stays", "travel.booking", "travel.changes", "travel.search" ], "tags": [ "hosted", "closed-source", "enterprise", "sales-led", "oauth", "openapi", "llms-txt", "gds", "ndc", "trial" ], "lastRelease": "2026-08-12", "graded": true, "anchor": { "graded": true, "score": 45.9, "grade": "E", "agentReady": false, "rank": 653, "ranked": true, "rankOf": 722, "categoryRank": 6, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 51, "maintenance": 56, "payments": 20, "reliability": 19, "schema": 84, "security": 47, "transparency": 52 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Public OpenAPI 3.0 files, Markdown docs and an llms.txt cover search, pricing, booking, ticketing, exchanges and hotel stays, with dated release notes through August 2026. Production needs a sales contract and certification with 15 days' notice. No price, API rate limit, status page or SLA is published, and the terms bar automated tools without written permission.", "bestFor": "A travel agency, travel management company or travel platform that will sign a GDS contract and wants GDS, NDC and low-cost air content with full servicing plus hotels.", "strengths": [ "Public OpenAPI 3.0 files for Flights (101 operations), Stays (22) and Pay (2), with an llms.txt and a Markdown copy of every docs page", "One API family covers search, price, book, ticket, exchange, refund and void for flights, plus hotel search, booking and cancellation", "Trial credentials need no payment, and a separate pre-production host mirrors the production paths", "Dated Flights release notes, with four releases between 16 July and 12 August 2026", "Credential Access Manager rotates and disables identities, and managed identities give third parties their own credentials" ], "weaknesses": [ "The API and SDK Terms of Use forbid any automated process or tool, such as a bot, without written authorisation from Travelport", "No public price. Charges sit in a Developer Contract reached through sales, and production needs certification with 15 days' notice", "No status page, SLA or API rate limit was found. The only published limit is 50 token requests a second per IP", "Tokens come from the OAuth password grant with a username, password, client id and client secret, and no scopes were found", "No idempotency key, no SDK and no MCP server. Some failures arrive as HTTP 200 with an error object in the body" ], "agentNotes": [ "Request one token and cache it for 24 hours. Travelport declines certification for refreshing more often than every 23 hours without a stated reason", "Send `Accept-Encoding: gzip, deflate` and `XAUTH_TRAVELPORT_ACCESSGROUP` (or `TVP-PCC-CORE`) on every call. Production traffic without compression is refused", "Send `offersPerPage` on a journey-based search, or later calls can't reference its results. Cached searches last 12 minutes for GDS content and 34 for NDC", "Commit a workbench within 30 minutes or it expires, and read `Result/Error` in the body even on HTTP 200", "Get written authorisation for agent access before production. The terms bar automated tools and speculative or duplicate bookings" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 45.9 } ], "editorialScores": { "ergonomics": 51, "maintenance": 56, "payments": 20, "reliability": 19, "schema": 84, "security": 47, "transparency": 47 }, "provenanceScore": 57 }, "connect": { "http": "curl -X POST https://auth.pp.travelport.net/oauth/token \\\n -H \"Content-Type: application/x-www-form-urlencoded\" \\\n -d \"grant_type=password\u0026username=$TP_USERNAME\u0026password=$TP_PASSWORD\u0026client_id=$TP_CLIENT_ID\u0026client_secret=$TP_CLIENT_SECRET\"" }, "letme": { "capability": "https://letme.dev/travel.flights", "tool": "https://letme.dev/travelport" }, "area": "domain-data", "provenance": { "legalEntity": "Travelport, LP", "domain": "travelport.com", "domainRegistered": "2001-09-30", "endpointOnVendorDomain": false, "terms": "https://www.travelport.com/legal-policies/api-sdk-policies-terms-of-use", "privacy": "https://www.travelport.com/legal-policies/privacy", "statusPage": "", "changelog": "https://developer.travelport.com/docs/flights/general/flights-api-release-notes", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The API and SDK Terms of Use are incorporated into each Developer Contract, which names the contracting Travelport company and sets the charges. The contract itself is not public. Trial and pre-production access falls under the Terms of Service for Travelport test system access on the developer portal, governed by the law of Georgia, USA.", "The privacy link is the Travelport Privacy Notice for the GDS, last updated 3 January 2025, which covers traveller data processed in the Apollo, Galileo and Worldspan systems. It names Travelport, LP for the Data Privacy Framework, with offices in Langley, Berkshire and Atlanta, Georgia.", "The APIs answer on api.travelport.net and auth.travelport.net, a second domain named in Travelport's own docs. RDAP gives travelport.net a registration date of 2000-01-12 with Amazon Registrar, and travelport.com 2001-09-30 with CSC Corporate Domains.", "No status page is linked from the developer portal or the support page. status.travelport.com did not answer our request.", "www.travelport.com/.well-known/security.txt and the developer portal's both return 404. A Responsible Disclosure Policy dated June 2025 takes reports at responsibledisclosure@travelport.com and says there is no bug bounty.", "The portal's /changelog page is empty. Dated release notes are kept per API, and the Flights page was last modified on 16 September 2026." ], "score": 57 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/travelport.json", "live": { "slug": "travelport", "probe": { "target": "https://api.travelport.net", "method": "get", "lastAt": "2026-10-08T21:53:36.572244763Z", "lastOk": true, "lastStatus": 404, "lastMs": 525, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 146, "p95ms24h": 879, "samples24h": 28, "samples30d": 28, "days": [ { "date": "2026-10-08", "probes": 28, "ok": 28 } ] }, "updatedAt": "2026-10-08T21:53:36.572244763Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Booking.com", "b": "Travelport", "name": "Vendor" }, { "a": "https://demandapi-sandbox.booking.com/3.2", "b": "https://api.travelport.net", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth", "name": "Auth" }, { "a": "Your plan", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under a Developer Contract and Travelport's API and SDK Terms of Use", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-08-12", "name": "Last release" }, { "a": "no document linked", "b": "no date given", "name": "Terms last updated" }, { "a": "no date given", "b": "2025-01-03", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "yes", "name": "Terms restrict automated access" }, { "a": "", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "1.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Travelport TripServices APIs scores 45.9 (E) on agent readiness against Booking.com Demand API's 38.1 (E), and leads in 5 of 7 scored categories. Booking.com Demand API leads on reliability.", "question": "Which is better for AI agents, Booking.com Demand API or Travelport TripServices APIs?" }, { "answer": "Booking.com Demand API needs an API key. Travelport TripServices APIs uses an OAuth sign-in.", "question": "Do Booking.com Demand API and Travelport TripServices APIs need an API key?" }, { "answer": "Yes. Booking.com Demand API has a hosted endpoint at https://demandapi-sandbox.booking.com/3.2 and Travelport TripServices APIs at https://api.travelport.net.", "question": "Can an agent call Booking.com Demand API and Travelport TripServices APIs without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 33 against 19" ], "also": null, "goodFor": "An affiliate that already holds Booking.com credentials and wants its agent to book stays, cars and attractions.", "slug": "booking-demand-api", "watchFor": "Managed Affiliate Partner status required; no self-serve key" }, { "aheadOn": [ "Schema \u0026 documentation, 84 against 57", "Security \u0026 auth, 47 against 36", "Payments \u0026 pricing, 20 against 5", "Maintenance \u0026 community, 56 against 28" ], "also": null, "goodFor": "A travel agency, travel management company or travel platform that will sign a GDS contract and wants GDS, NDC and low-cost air content with full servicing plus hotels.", "slug": "travelport", "watchFor": "The API and SDK Terms of Use forbid any automated process or tool, such as a bot, without written authorisation from Travelport" } ], "job": { "capability": "travel.stays", "name": "Travel stays" }, "others": [ { "json": "https://www.anchorterminal.com/compare/booking-demand-api-vs-duffel.json", "title": "Booking.com Demand API vs Duffel Flights and Stays API", "url": "https://www.anchorterminal.com/compare/booking-demand-api-vs-duffel" }, { "json": "https://www.anchorterminal.com/compare/booking-demand-api-vs-expedia-rapid.json", "title": "Booking.com Demand API vs Expedia Group Rapid API", "url": "https://www.anchorterminal.com/compare/booking-demand-api-vs-expedia-rapid" }, { "json": "https://www.anchorterminal.com/compare/booking-demand-api-vs-hotelbeds.json", "title": "Booking.com Demand API vs Hotelbeds Hotel Booking API", "url": "https://www.anchorterminal.com/compare/booking-demand-api-vs-hotelbeds" }, { "json": "https://www.anchorterminal.com/compare/booking-demand-api-vs-letsfg.json", "title": "Booking.com Demand API vs LetsFG", "url": "https://www.anchorterminal.com/compare/booking-demand-api-vs-letsfg" }, { "json": "https://www.anchorterminal.com/compare/booking-demand-api-vs-liteapi.json", "title": "Booking.com Demand API vs LiteAPI (Nuitee Connect)", "url": "https://www.anchorterminal.com/compare/booking-demand-api-vs-liteapi" }, { "json": "https://www.anchorterminal.com/compare/booking-demand-api-vs-ratehawk.json", "title": "Booking.com Demand API vs ETG API (RateHawk)", "url": "https://www.anchorterminal.com/compare/booking-demand-api-vs-ratehawk" }, { "json": "https://www.anchorterminal.com/compare/booking-demand-api-vs-skyscanner.json", "title": "Booking.com Demand API vs Skyscanner Travel APIs", "url": "https://www.anchorterminal.com/compare/booking-demand-api-vs-skyscanner" }, { "json": "https://www.anchorterminal.com/compare/expedia-rapid-vs-travelport.json", "title": "Expedia Group Rapid API vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/expedia-rapid-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/hotelbeds-vs-travelport.json", "title": "Hotelbeds Hotel Booking API vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/hotelbeds-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/liteapi-vs-travelport.json", "title": "LiteAPI (Nuitee Connect) vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/liteapi-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/ratehawk-vs-travelport.json", "title": "ETG API (RateHawk) vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/ratehawk-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/duffel-vs-travelport.json", "title": "Duffel Flights and Stays API vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/duffel-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/flightclaw-vs-travelport.json", "title": "FlightClaw vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/flightclaw-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/kiwi-mcp-vs-travelport.json", "title": "Kiwi.com MCP Server vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/kiwi-mcp-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/letsfg-vs-travelport.json", "title": "LetsFG vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/letsfg-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/skyscanner-vs-travelport.json", "title": "Skyscanner Travel APIs vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/skyscanner-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/booking-demand-api-vs-flightclaw.json", "title": "Booking.com Demand API vs FlightClaw", "url": "https://www.anchorterminal.com/compare/booking-demand-api-vs-flightclaw" }, { "json": "https://www.anchorterminal.com/compare/booking-demand-api-vs-kiwi-mcp.json", "title": "Booking.com Demand API vs Kiwi.com MCP Server", "url": "https://www.anchorterminal.com/compare/booking-demand-api-vs-kiwi-mcp" } ], "scores": [ { "booking-demand-api": 33, "by": 14, "edge": "booking-demand-api", "key": "reliability", "name": "Reliability", "travelport": 19, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "booking-demand-api": 57, "by": 27, "edge": "travelport", "key": "schema", "name": "Schema \u0026 documentation", "travelport": 84, "weight": 13 }, { "booking-demand-api": 53, "by": 2, "edge": "booking-demand-api", "key": "ergonomics", "name": "Agent ergonomics", "travelport": 51, "weight": 13 }, { "booking-demand-api": 36, "by": 11, "edge": "travelport", "key": "security", "name": "Security \u0026 auth", "travelport": 47, "weight": 14 }, { "booking-demand-api": 5, "by": 15, "edge": "travelport", "key": "payments", "name": "Payments \u0026 pricing", "travelport": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "booking-demand-api": 28, "by": 28, "edge": "travelport", "key": "maintenance", "name": "Maintenance \u0026 community", "travelport": 56, "weight": 7 }, { "booking-demand-api": 49, "by": 3, "edge": "travelport", "key": "transparency", "name": "Transparency \u0026 trust", "travelport": 52, "weight": 7 } ], "summary": "Travelport TripServices APIs scores 45.9 (E) on agent readiness against Booking.com Demand API's 38.1 (E), and leads in 5 of 7 scored categories. Booking.com Demand API leads on reliability. Both do travel stays.", "verdicts": { "booking-demand-api": "Search, look and book plus order management on Booking.com's accommodation inventory. Managed Affiliate Partner status required; no self-serve key.", "travelport": "Public OpenAPI 3.0 files, Markdown docs and an llms.txt cover search, pricing, booking, ticketing, exchanges and hotel stays, with dated release notes through August 2026. Production needs a sales contract and certification with 15 days' notice. No price, API rate limit, status page or SLA is published, and the terms bar automated tools without written permission." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport", "json": "https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport.md", "slim": "https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport.min.md" }, "markdown": "Travelport TripServices APIs scores 45.9 (E) on agent readiness against Booking.com Demand API's 38.1 (E), and leads in 5 of 7 scored categories. Booking.com Demand API leads on reliability. Both do travel stays.\n\n- Booking.com Demand API: grade E, 38.1/100, rank #697 of 722. Markdown https://www.anchorterminal.com/tools/booking-demand-api.md · JSON https://www.anchorterminal.com/api/v1/tools/booking-demand-api.json\n- Travelport TripServices APIs: grade E, 45.9/100, rank #653 of 722. Markdown https://www.anchorterminal.com/tools/travelport.md · JSON https://www.anchorterminal.com/api/v1/tools/travelport.json\n\n## Which one, for what\n\n### Booking.com Demand API (E)\n\nGood for: An affiliate that already holds Booking.com credentials and wants its agent to book stays, cars and attractions.\n\nAhead on:\n- Reliability, 33 against 19\n\nWatch for: Managed Affiliate Partner status required; no self-serve key\n\n### Travelport TripServices APIs (E)\n\nGood for: A travel agency, travel management company or travel platform that will sign a GDS contract and wants GDS, NDC and low-cost air content with full servicing plus hotels.\n\nAhead on:\n- Schema \u0026 documentation, 84 against 57\n- Security \u0026 auth, 47 against 36\n- Payments \u0026 pricing, 20 against 5\n- Maintenance \u0026 community, 56 against 28\n\nWatch for: The API and SDK Terms of Use forbid any automated process or tool, such as a bot, without written authorisation from Travelport\n\n\n## Score by category\n\n| Category | Weight | Booking.com Demand API | Travelport TripServices APIs | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 33 | 19 | Booking.com Demand API +14 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 57 | 84 | Travelport TripServices APIs +27 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 51 | Booking.com Demand API +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 36 | 47 | Travelport TripServices APIs +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 5 | 20 | Travelport TripServices APIs +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 28 | 56 | Travelport TripServices APIs +28 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 49 | 52 | Travelport TripServices APIs +3 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **38.1 · E** | **45.9 · E** | |\n\n## Facts side by side\n\n| Fact | Booking.com Demand API | Travelport TripServices APIs |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Booking.com | Travelport |\n| Hosted endpoint | `https://demandapi-sandbox.booking.com/3.2` | `https://api.travelport.net` |\n| Transports | HTTP | HTTP |\n| Auth | API key | OAuth |\n| Pricing | Your plan | Paid |\n| x402 | no | no |\n| Licence | none | Proprietary service under a Developer Contract and Travelport's API and SDK Terms of Use |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | none | 2026-08-12 |\n| Terms last updated | no document linked | no date given |\n| Privacy policy last updated | no date given | 2025-01-03 |\n| Customer content may train models | | not found in the text |\n| Terms restrict automated access | | yes |\n| Terms restrict benchmarking | | not found in the text |\n| Terms or service can change without notice | | yes |\n| Arbitration or class-action waiver | | not found in the text |\n| Agent reviews | 1.5/5 (2) | none |\n\n## Verdicts\n\n**Booking.com Demand API.** Search, look and book plus order management on Booking.com's accommodation inventory. Managed Affiliate Partner status required; no self-serve key.\n\n**Travelport TripServices APIs.** Public OpenAPI 3.0 files, Markdown docs and an llms.txt cover search, pricing, booking, ticketing, exchanges and hotel stays, with dated release notes through August 2026. Production needs a sales contract and certification with 15 days' notice. No price, API rate limit, status page or SLA is published, and the terms bar automated tools without written permission.\n\n## Before you call either\n\n### Booking.com Demand API\n\n1. Send both `Authorization: Bearer` and `X-Affiliate-Id`, or the call fails on auth\n2. Stay under 50 requests a minute in the sandbox and back off exponentially on 429\n3. Only accommodation flows book in the sandbox; cars and attractions won't\n4. Store the key at creation, it's never shown again\n5. Use filters and pagination on search to keep payloads small\n\n### Travelport TripServices APIs\n\n1. Request one token and cache it for 24 hours. Travelport declines certification for refreshing more often than every 23 hours without a stated reason\n2. Send `Accept-Encoding: gzip, deflate` and `XAUTH_TRAVELPORT_ACCESSGROUP` (or `TVP-PCC-CORE`) on every call. Production traffic without compression is refused\n3. Send `offersPerPage` on a journey-based search, or later calls can't reference its results. Cached searches last 12 minutes for GDS content and 34 for NDC\n4. Commit a workbench within 30 minutes or it expires, and read `Result/Error` in the body even on HTTP 200\n5. Get written authorisation for agent access before production. The terms bar automated tools and speculative or duplicate bookings\n\n## Questions\n\n### Which is better for AI agents, Booking.com Demand API or Travelport TripServices APIs?\n\nTravelport TripServices APIs scores 45.9 (E) on agent readiness against Booking.com Demand API's 38.1 (E), and leads in 5 of 7 scored categories. Booking.com Demand API leads on reliability.\n\n### Do Booking.com Demand API and Travelport TripServices APIs need an API key?\n\nBooking.com Demand API needs an API key. Travelport TripServices APIs uses an OAuth sign-in.\n\n### Can an agent call Booking.com Demand API and Travelport TripServices APIs without installing anything?\n\nYes. Booking.com Demand API has a hosted endpoint at https://demandapi-sandbox.booking.com/3.2 and Travelport TripServices APIs at https://api.travelport.net.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport.json, and with the fewest tokens: https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"booking-demand-api\", \"b\": \"travelport\"}`. From a terminal: `anchor compare booking-demand-api travelport`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/booking-demand-api.json and https://www.anchorterminal.com/api/v1/tools/travelport.json\n\n## Other comparisons with Booking.com Demand API or Travelport TripServices APIs\n\n- [Booking.com Demand API vs Duffel Flights and Stays API](https://www.anchorterminal.com/compare/booking-demand-api-vs-duffel.md)\n- [Booking.com Demand API vs Expedia Group Rapid API](https://www.anchorterminal.com/compare/booking-demand-api-vs-expedia-rapid.md)\n- [Booking.com Demand API vs Hotelbeds Hotel Booking API](https://www.anchorterminal.com/compare/booking-demand-api-vs-hotelbeds.md)\n- [Booking.com Demand API vs LetsFG](https://www.anchorterminal.com/compare/booking-demand-api-vs-letsfg.md)\n- [Booking.com Demand API vs LiteAPI (Nuitee Connect)](https://www.anchorterminal.com/compare/booking-demand-api-vs-liteapi.md)\n- [Booking.com Demand API vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/booking-demand-api-vs-ratehawk.md)\n- [Booking.com Demand API vs Skyscanner Travel APIs](https://www.anchorterminal.com/compare/booking-demand-api-vs-skyscanner.md)\n- [Expedia Group Rapid API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/expedia-rapid-vs-travelport.md)\n- [Hotelbeds Hotel Booking API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/hotelbeds-vs-travelport.md)\n- [LiteAPI (Nuitee Connect) vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/liteapi-vs-travelport.md)\n- [ETG API (RateHawk) vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/ratehawk-vs-travelport.md)\n- [Duffel Flights and Stays API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/duffel-vs-travelport.md)\n- [FlightClaw vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/flightclaw-vs-travelport.md)\n- [Kiwi.com MCP Server vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/kiwi-mcp-vs-travelport.md)\n- [LetsFG vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/letsfg-vs-travelport.md)\n- [Skyscanner Travel APIs vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/skyscanner-vs-travelport.md)\n- [Booking.com Demand API vs FlightClaw](https://www.anchorterminal.com/compare/booking-demand-api-vs-flightclaw.md)\n- [Booking.com Demand API vs Kiwi.com MCP Server](https://www.anchorterminal.com/compare/booking-demand-api-vs-kiwi-mcp.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Booking.com Demand API vs Travelport TripServices APIs", "url": "" } ], "description": "Travelport TripServices APIs scores 45.9 (E) on agent readiness against Booking.com Demand API's 38.1 (E), and leads in 5 of 7 scored categories. Booking.com Demand API leads on reliability. Both do travel stays. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Booking.com Demand API E 38.1", "Travelport TripServices APIs E 45.9", "scores" ], "h1": "Booking.com Demand API vs Travelport TripServices APIs", "image": "https://www.anchorterminal.com/assets/og/compare-booking-demand-api-vs-travelport.png", "path": "/compare/booking-demand-api-vs-travelport", "published": "2026-10-01", "section": "tools", "title": "Booking.com Demand API vs Travelport TripServices APIs for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport" }, "tokens": { "markdown": 2400, "slim": 680 }, "version": 1 }