Head to head · Travel stays · October 2026 research run
ETG API (RateHawk) vs Travelport TripServices APIs
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 & auth and payments & pricing. Both do travel stays.
Which one, for what
Good for A travel company with an ETG contract that wants wholesale hotel rates behind its agent, with a documented sandbox for the build.
Ahead on
- Reliability, 45 against 19
- Agent ergonomics, 69 against 51
- Maintenance & community, 65 against 56
Watch 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
Travelport TripServices APIs E
Good 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.
Ahead on
- Security & auth, 47 against 41
- Payments & pricing, 20 against 10
Watch for
The API and SDK Terms of Use forbid any automated process or tool, such as a bot, without written authorisation from Travelport
Score by category
| Category | Weight this run | ETG API (RateHawk) | Travelport TripServices APIs | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 45 | 19 | ETG API (RateHawk) +26 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 85 | 84 | ETG API (RateHawk) +1 |
| Agent ergonomics | 13%16.2 | 69 | 51 | ETG API (RateHawk) +18 |
| Security & auth | 14%17.5 | 41 | 47 | Travelport TripServices APIs +6 |
| Payments & pricing | 10%12.5 | 10 | 20 | Travelport TripServices APIs +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 65 | 56 | ETG API (RateHawk) +9 |
| Transparency & trust | 7%8.8 | 56 | 52 | ETG API (RateHawk) +4 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 53 · D | 45.9 · E |
Facts side by side
| Fact | ETG API (RateHawk) | Travelport TripServices APIs |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Emerging Travel Group | Travelport |
| Hosted endpoint | https://api.ratehawk.com | https://api.travelport.net |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth |
| Pricing | Your plan | Paid |
| x402 | no | no |
| 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 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-05 | 2026-08-12 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | 2026-05-08 | 2025-01-03 |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | yes | |
| Terms restrict benchmarking | not found in the text | |
| Terms or service can change without notice | yes | |
| Arbitration or class-action waiver | not found in the text | |
| Popularity | 9 stars, 12 PyPI/wk | none |
Verdicts
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.
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.
Before you call either
ETG API (RateHawk)
- 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 pollbooking/finish/statusuntilokor a final error. Treattimeout,unknownand 5xx as still in progress. - Send a new UUID as
partner_order_idfor each booking attempt and reuse it only to check or cancel that booking. - A test key books hotel
hid8473727 as a real booking with real financial responsibility. Cancel it afterwards.
Travelport TripServices APIs
- 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, deflateandXAUTH_TRAVELPORT_ACCESSGROUP(orTVP-PCC-CORE) on every call. Production traffic without compression is refused - Send
offersPerPageon 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/Errorin the body even on HTTP 200 - Get written authorisation for agent access before production. The terms bar automated tools and speculative or duplicate bookings
Questions
Which is better for AI agents, ETG API (RateHawk) or Travelport TripServices APIs?
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 & auth and payments & pricing.
Do ETG API (RateHawk) and Travelport TripServices APIs need an API key?
ETG API (RateHawk) needs an API key. Travelport TripServices APIs uses an OAuth sign-in.
Can an agent call ETG API (RateHawk) and Travelport TripServices APIs without installing anything?
Yes. ETG API (RateHawk) has a hosted endpoint at https://api.ratehawk.com and Travelport TripServices APIs at https://api.travelport.net.
Other comparisons with ETG API (RateHawk) or Travelport TripServices APIs
- Booking.com Demand API vs ETG API (RateHawk)
- Booking.com Demand API vs Travelport TripServices APIs
- Duffel Flights and Stays API vs ETG API (RateHawk)
- Expedia Group Rapid API vs ETG API (RateHawk)
- Expedia Group Rapid API vs Travelport TripServices APIs
- Hotelbeds Hotel Booking API vs ETG API (RateHawk)
- Hotelbeds Hotel Booking API vs Travelport TripServices APIs
- LetsFG vs ETG API (RateHawk)
- LiteAPI (Nuitee Connect) vs ETG API (RateHawk)
- LiteAPI (Nuitee Connect) vs Travelport TripServices APIs
- ETG API (RateHawk) vs Skyscanner Travel APIs
- Duffel Flights and Stays API vs Travelport TripServices APIs
- FlightClaw vs Travelport TripServices APIs
- Kiwi.com MCP Server vs Travelport TripServices APIs
- LetsFG vs Travelport TripServices APIs
- Skyscanner Travel APIs vs Travelport TripServices APIs
- FlightClaw vs ETG API (RateHawk)
- Kiwi.com MCP Server vs ETG API (RateHawk)
Machine-readable
- This page as Markdown
/compare/ratehawk-vs-travelport.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/ratehawk.json·/api/v1/tools/travelport.json - From a terminal
anchor compare ratehawk travelport(the CLI) - Over MCP
compare_tools {"a": "ratehawk", "b": "travelport"}at/mcp, no key