{ "data": { "a": { "slug": "ratehawk", "name": "ETG API (RateHawk)", "vendor": "Emerging Travel Group", "vendorUrl": "https://www.ratehawk.com", "kind": "http-api", "category": "travel", "summary": "Hotel search and booking API from Emerging Travel Group, the company behind RateHawk and ZenHotels. Contracted partners search rates, prebook, book and cancel stays over REST, with B2B, Affiliate and Content APIs.", "url": "https://www.anchorterminal.com/tools/ratehawk", "markdownUrl": "https://www.anchorterminal.com/tools/ratehawk.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/ratehawk.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/ratehawk.json", "repo": "https://github.com/EmergingTravel/papi-sdk-python", "license": "Proprietary service under a signed partner agreement that is not published. The Python and PHP SDKs on GitHub are MIT", "transports": [ "http" ], "remoteUrl": "https://api.ratehawk.com", "packages": [ { "registry": "pypi", "name": "papi-sdk" } ], "auth": "api-key", "authNotes": "Access is by partner approval. A person registers at ratehawk.com/registration, picks API integration as the purpose, then asks an account manager for credentials, and the docs say the relevant agreement must be signed before the API is used. Keys are `\u003cKEY_ID\u003e:\u003cAPI_KEY\u003e` pairs sent as HTTP Basic auth, issued separately for sandbox, test and production. A production key follows a written certification that the docs put at 14 to 30 days. Each key has its own endpoint permissions and request limits, readable at `/api/b2b/v3/overview/`.", "pricing": "byo-plan", "pricingNotes": "No public price list. Partners buy at net rates under contract and pay from a deposit with a credit limit, at the hotel or by card, depending on the rate. The landing page calls the API key free, and the sandbox makes no real bookings or charges, but a key comes from an account manager after registration, so an agent cannot start without a person and an agreement (checked 2026-10-08).", "priceSummary": "Your plan", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the Swagger file or the API landing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 9, "npmWeekly": null, "pypiWeekly": 12, "asOf": "2026-10-08" }, "docsUrl": "https://docs.emergingtravel.com/", "llmsTxt": "https://docs.emergingtravel.com/llms.txt", "openapi": "https://api.ratehawk.com/openapi.json", "capabilities": [ "travel.stays", "travel.booking", "travel.changes", "travel.search" ], "tags": [ "hosted", "closed-source", "openapi", "llms-txt", "sandbox", "sales-led", "certification", "status-page", "python", "php", "eu" ], "lastRelease": "2026-10-05", "graded": true, "anchor": { "graded": true, "score": 53, "grade": "D", "agentReady": false, "rank": 554, "ranked": true, "rankOf": 722, "categoryRank": 4, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 65, "payments": 10, "reliability": 45, "schema": 85, "security": 41, "transparency": 56 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "Hotel search and booking are documented in a public Swagger 2.0 file, an llms.txt index and a changelog with 64 dated entries in 2026. Access is by contract. Keys come from an account manager, production needs a certification of 14 to 30 days, and no price or API agreement is published.", "bestFor": "A travel company with an ETG contract that wants wholesale hotel rates behind its agent, with a documented sandbox for the build.", "strengths": [ "Public Swagger 2.0 file at `https://api.ratehawk.com/openapi.json` with 48 operations and 171 definitions for the B2B and Content APIs", "`llms.txt` and a Markdown copy of every docs page at `index.md`, with robots.txt allowing AI crawlers by name", "Changelog with 64 dated entries in 2026, the latest on 5 October 2026", "Sandbox host with over 2,000 test hotels, named error scenarios and no real bookings or charges", "`partner_order_id` identifies a booking across retries, and the docs say how to handle `timeout`, `unknown` and 5xx during booking" ], "weaknesses": [ "No self-serve key. Registration is followed by a request to an account manager, and the docs say an agreement must be signed before use", "No public price list or API agreement was found. Rates and request limits are set per contract", "The status page's orders monitor recorded downtime of an hour or more on four days between 21 July and 14 September 2026, with no written incident reports", "Both official SDKs (Python and PHP) last changed in 2021 and default to `api.worldota.net`, a host the docs call deprecated", "No `security.txt`, disclosure policy or security certification page was found on ratehawk.com, emergingtravel.com or the docs site" ], "agentNotes": [ "Call `/api/b2b/v3/overview/` first. It lists the endpoints the key may use and each one's request limit.", "Keep sandbox IDs, keys and hashes inside `api-sandbox.ratehawk.com`. Sandbox region IDs are limited to 2011, 2395, 2734 and 6053839.", "Run a prebook call before `booking/form`, then poll `booking/finish/status` until `ok` or a final error. Treat `timeout`, `unknown` and 5xx as still in progress.", "Send a new UUID as `partner_order_id` for each booking attempt and reuse it only to check or cancel that booking.", "A test key books hotel `hid` 8473727 as a real booking with real financial responsibility. Cancel it afterwards." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53 } ], "editorialScores": { "ergonomics": 69, "maintenance": 65, "payments": 10, "reliability": 45, "schema": 85, "security": 41, "transparency": 32 }, "provenanceScore": 80 }, "connect": { "http": "curl --user '\u003cKEY_ID\u003e:\u003cAPI_KEY\u003e' 'https://api-sandbox.ratehawk.com/api/b2b/v3/overview/'" }, "letme": { "capability": "https://letme.dev/travel.stays", "tool": "https://letme.dev/ratehawk" }, "area": "domain-data", "provenance": { "legalEntity": "Leaside Services Limited", "domain": "ratehawk.com", "domainRegistered": "2006-08-24", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://www.ratehawk.com/legal/site/privacy-policy/", "statusPage": "https://status.emergingtravel.com", "changelog": "https://docs.emergingtravel.com/docs/changelog/2026/", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "No terms document for the API is published. The docs say the relevant agreement must be signed before use, and the only public terms we found are website terms of use on emergingtravel.com, so the terms field is left out.", "The RateHawk legal notice names Leaside Services Limited, a Cyprus company with registration number HE 342401, at Ifigeneias 17, Strovolos, Nicosia. The privacy notice (version 1.0, updated 8 May 2026) gives the same company an address in Limassol and lists eight other Emerging Travel entities as controllers by contract.", "The API answers at api.ratehawk.com and api-sandbox.ratehawk.com. Card tokenisation is at api.payota.net and the docs are at docs.emergingtravel.com, both outside ratehawk.com.", "`/.well-known/security.txt` returned 404 on www.ratehawk.com, api.ratehawk.com, www.emergingtravel.com and docs.emergingtravel.com.", "RDAP gives ratehawk.com a registration date of 2006-08-24 and emergingtravel.com 2007-02-25." ], "score": 80 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/ratehawk.json", "live": { "slug": "ratehawk", "probe": { "target": "https://api.ratehawk.com", "method": "get", "lastAt": "2026-10-08T21:12:19.571043581Z", "lastOk": true, "lastStatus": 200, "lastMs": 115, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 132, "p95ms24h": 175, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "vendorStatus": { "page": "https://status.emergingtravel.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T19:39:06.568833713Z" }, "updatedAt": "2026-10-08T21:12:19.571043581Z" } }, "answer": "ETG API (RateHawk) scores 53 (D) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 5 of 7 scored categories. Travelport TripServices APIs leads on security \u0026 auth and payments \u0026 pricing.", "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:12:23.884869501Z", "lastOk": true, "lastStatus": 404, "lastMs": 132, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 132, "p95ms24h": 194, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-08", "probes": 21, "ok": 21 } ] }, "updatedAt": "2026-10-08T21:12:23.884869501Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Emerging Travel Group", "b": "Travelport", "name": "Vendor" }, { "a": "https://api.ratehawk.com", "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": "Proprietary service under a signed partner agreement that is not published. The Python and PHP SDKs on GitHub are MIT", "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": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-05", "b": "2026-08-12", "name": "Last release" }, { "a": "no document linked", "b": "no date given", "name": "Terms last updated" }, { "a": "2026-05-08", "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": "9 stars, 12 PyPI/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "ETG API (RateHawk) scores 53 (D) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 5 of 7 scored categories. Travelport TripServices APIs leads on security \u0026 auth and payments \u0026 pricing.", "question": "Which is better for AI agents, ETG API (RateHawk) or Travelport TripServices APIs?" }, { "answer": "ETG API (RateHawk) needs an API key. Travelport TripServices APIs uses an OAuth sign-in.", "question": "Do ETG API (RateHawk) and Travelport TripServices APIs need an API key?" }, { "answer": "Yes. ETG API (RateHawk) has a hosted endpoint at https://api.ratehawk.com and Travelport TripServices APIs at https://api.travelport.net.", "question": "Can an agent call ETG API (RateHawk) and Travelport TripServices APIs without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 45 against 19", "Agent ergonomics, 69 against 51", "Maintenance \u0026 community, 65 against 56" ], "also": null, "goodFor": "A travel company with an ETG contract that wants wholesale hotel rates behind its agent, with a documented sandbox for the build.", "slug": "ratehawk", "watchFor": "No self-serve key. Registration is followed by a request to an account manager, and the docs say an agreement must be signed before use" }, { "aheadOn": [ "Security \u0026 auth, 47 against 41", "Payments \u0026 pricing, 20 against 10" ], "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-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-travelport.json", "title": "Booking.com Demand API vs Travelport TripServices APIs", "url": "https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport" }, { "json": "https://www.anchorterminal.com/compare/duffel-vs-ratehawk.json", "title": "Duffel Flights and Stays API vs ETG API (RateHawk)", "url": "https://www.anchorterminal.com/compare/duffel-vs-ratehawk" }, { "json": "https://www.anchorterminal.com/compare/expedia-rapid-vs-ratehawk.json", "title": "Expedia Group Rapid API vs ETG API (RateHawk)", "url": "https://www.anchorterminal.com/compare/expedia-rapid-vs-ratehawk" }, { "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-ratehawk.json", "title": "Hotelbeds Hotel Booking API vs ETG API (RateHawk)", "url": "https://www.anchorterminal.com/compare/hotelbeds-vs-ratehawk" }, { "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/letsfg-vs-ratehawk.json", "title": "LetsFG vs ETG API (RateHawk)", "url": "https://www.anchorterminal.com/compare/letsfg-vs-ratehawk" }, { "json": "https://www.anchorterminal.com/compare/liteapi-vs-ratehawk.json", "title": "LiteAPI (Nuitee Connect) vs ETG API (RateHawk)", "url": "https://www.anchorterminal.com/compare/liteapi-vs-ratehawk" }, { "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-skyscanner.json", "title": "ETG API (RateHawk) vs Skyscanner Travel APIs", "url": "https://www.anchorterminal.com/compare/ratehawk-vs-skyscanner" }, { "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/flightclaw-vs-ratehawk.json", "title": "FlightClaw vs ETG API (RateHawk)", "url": "https://www.anchorterminal.com/compare/flightclaw-vs-ratehawk" }, { "json": "https://www.anchorterminal.com/compare/kiwi-mcp-vs-ratehawk.json", "title": "Kiwi.com MCP Server vs ETG API (RateHawk)", "url": "https://www.anchorterminal.com/compare/kiwi-mcp-vs-ratehawk" } ], "scores": [ { "by": 26, "edge": "ratehawk", "key": "reliability", "name": "Reliability", "ratehawk": 45, "travelport": 19, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 1, "edge": "ratehawk", "key": "schema", "name": "Schema \u0026 documentation", "ratehawk": 85, "travelport": 84, "weight": 13 }, { "by": 18, "edge": "ratehawk", "key": "ergonomics", "name": "Agent ergonomics", "ratehawk": 69, "travelport": 51, "weight": 13 }, { "by": 6, "edge": "travelport", "key": "security", "name": "Security \u0026 auth", "ratehawk": 41, "travelport": 47, "weight": 14 }, { "by": 10, "edge": "travelport", "key": "payments", "name": "Payments \u0026 pricing", "ratehawk": 10, "travelport": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 9, "edge": "ratehawk", "key": "maintenance", "name": "Maintenance \u0026 community", "ratehawk": 65, "travelport": 56, "weight": 7 }, { "by": 4, "edge": "ratehawk", "key": "transparency", "name": "Transparency \u0026 trust", "ratehawk": 56, "travelport": 52, "weight": 7 } ], "summary": "ETG API (RateHawk) scores 53 (D) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 5 of 7 scored categories. Travelport TripServices APIs leads on security \u0026 auth and payments \u0026 pricing. Both do travel stays.", "verdicts": { "ratehawk": "Hotel search and booking are documented in a public Swagger 2.0 file, an llms.txt index and a changelog with 64 dated entries in 2026. Access is by contract. Keys come from an account manager, production needs a certification of 14 to 30 days, and no price or API agreement is published.", "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/ratehawk-vs-travelport", "json": "https://www.anchorterminal.com/compare/ratehawk-vs-travelport.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/ratehawk-vs-travelport.md", "slim": "https://www.anchorterminal.com/compare/ratehawk-vs-travelport.min.md" }, "markdown": "ETG API (RateHawk) scores 53 (D) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 5 of 7 scored categories. Travelport TripServices APIs leads on security \u0026 auth and payments \u0026 pricing. Both do travel stays.\n\n- ETG API (RateHawk): grade D, 53/100, rank #554 of 722. Markdown https://www.anchorterminal.com/tools/ratehawk.md · JSON https://www.anchorterminal.com/api/v1/tools/ratehawk.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### ETG API (RateHawk) (D)\n\nGood for: A travel company with an ETG contract that wants wholesale hotel rates behind its agent, with a documented sandbox for the build.\n\nAhead on:\n- Reliability, 45 against 19\n- Agent ergonomics, 69 against 51\n- Maintenance \u0026 community, 65 against 56\n\nWatch for: No self-serve key. Registration is followed by a request to an account manager, and the docs say an agreement must be signed before use\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- Security \u0026 auth, 47 against 41\n- Payments \u0026 pricing, 20 against 10\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 | ETG API (RateHawk) | Travelport TripServices APIs | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 19 | ETG API (RateHawk) +26 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 85 | 84 | ETG API (RateHawk) +1 |\n| Agent ergonomics | 13% (16.2 this run) | 69 | 51 | ETG API (RateHawk) +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 41 | 47 | Travelport TripServices APIs +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 10 | 20 | Travelport TripServices APIs +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 65 | 56 | ETG API (RateHawk) +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 56 | 52 | ETG API (RateHawk) +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **53 · D** | **45.9 · E** | |\n\n## Facts side by side\n\n| Fact | ETG API (RateHawk) | Travelport TripServices APIs |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Emerging Travel Group | Travelport |\n| Hosted endpoint | `https://api.ratehawk.com` | `https://api.travelport.net` |\n| Transports | HTTP | HTTP |\n| Auth | API key | OAuth |\n| Pricing | Your plan | Paid |\n| x402 | no | no |\n| Licence | Proprietary service under a signed partner agreement that is not published. The Python and PHP SDKs on GitHub are MIT | 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 | yes | yes |\n| Last release | 2026-10-05 | 2026-08-12 |\n| Terms last updated | no document linked | no date given |\n| Privacy policy last updated | 2026-05-08 | 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| Popularity | 9 stars, 12 PyPI/wk | none |\n\n## Verdicts\n\n**ETG API (RateHawk).** Hotel search and booking are documented in a public Swagger 2.0 file, an llms.txt index and a changelog with 64 dated entries in 2026. Access is by contract. Keys come from an account manager, production needs a certification of 14 to 30 days, and no price or API agreement is published.\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### ETG API (RateHawk)\n\n1. Call `/api/b2b/v3/overview/` first. It lists the endpoints the key may use and each one's request limit.\n2. Keep sandbox IDs, keys and hashes inside `api-sandbox.ratehawk.com`. Sandbox region IDs are limited to 2011, 2395, 2734 and 6053839.\n3. Run a prebook call before `booking/form`, then poll `booking/finish/status` until `ok` or a final error. Treat `timeout`, `unknown` and 5xx as still in progress.\n4. Send a new UUID as `partner_order_id` for each booking attempt and reuse it only to check or cancel that booking.\n5. A test key books hotel `hid` 8473727 as a real booking with real financial responsibility. Cancel it afterwards.\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, ETG API (RateHawk) or Travelport TripServices APIs?\n\nETG API (RateHawk) scores 53 (D) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 5 of 7 scored categories. Travelport TripServices APIs leads on security \u0026 auth and payments \u0026 pricing.\n\n### Do ETG API (RateHawk) and Travelport TripServices APIs need an API key?\n\nETG API (RateHawk) needs an API key. Travelport TripServices APIs uses an OAuth sign-in.\n\n### Can an agent call ETG API (RateHawk) and Travelport TripServices APIs without installing anything?\n\nYes. ETG API (RateHawk) has a hosted endpoint at https://api.ratehawk.com 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/ratehawk-vs-travelport.json, and with the fewest tokens: https://www.anchorterminal.com/compare/ratehawk-vs-travelport.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"ratehawk\", \"b\": \"travelport\"}`. From a terminal: `anchor compare ratehawk travelport`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/ratehawk.json and https://www.anchorterminal.com/api/v1/tools/travelport.json\n\n## Other comparisons with ETG API (RateHawk) or Travelport TripServices APIs\n\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 Travelport TripServices APIs](https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport.md)\n- [Duffel Flights and Stays API vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/duffel-vs-ratehawk.md)\n- [Expedia Group Rapid API vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/expedia-rapid-vs-ratehawk.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 ETG API (RateHawk)](https://www.anchorterminal.com/compare/hotelbeds-vs-ratehawk.md)\n- [Hotelbeds Hotel Booking API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/hotelbeds-vs-travelport.md)\n- [LetsFG vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/letsfg-vs-ratehawk.md)\n- [LiteAPI (Nuitee Connect) vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/liteapi-vs-ratehawk.md)\n- [LiteAPI (Nuitee Connect) vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/liteapi-vs-travelport.md)\n- [ETG API (RateHawk) vs Skyscanner Travel APIs](https://www.anchorterminal.com/compare/ratehawk-vs-skyscanner.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- [FlightClaw vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/flightclaw-vs-ratehawk.md)\n- [Kiwi.com MCP Server vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/kiwi-mcp-vs-ratehawk.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": "ETG API (RateHawk) vs Travelport TripServices APIs", "url": "" } ], "description": "ETG API (RateHawk) scores 53 (D) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 5 of 7 scored categories. Travelport TripServices APIs leads on security \u0026 auth and payments \u0026 pricing. Both do travel stays. Category scores, facts, verdicts and…", "facts": [ "ETG API (RateHawk) D 53", "Travelport TripServices APIs E 45.9", "scores" ], "h1": "ETG API (RateHawk) vs Travelport TripServices APIs", "image": "https://www.anchorterminal.com/assets/og/compare-ratehawk-vs-travelport.png", "path": "/compare/ratehawk-vs-travelport", "published": "2026-10-01", "section": "tools", "title": "ETG API (RateHawk) vs Travelport TripServices APIs for AI agents", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/ratehawk-vs-travelport" }, "tokens": { "markdown": 2500, "slim": 730 }, "version": 1 }