# 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. Category scores, facts, verdicts and…

- Canonical: https://www.anchorterminal.com/compare/ratehawk-vs-travelport
- Markdown: https://www.anchorterminal.com/compare/ratehawk-vs-travelport.md (~2,500 tokens)
- Slim: https://www.anchorterminal.com/compare/ratehawk-vs-travelport.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/ratehawk-vs-travelport.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

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.

- 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
- 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

## Which one, for what

### ETG API (RateHawk) (D)

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 | ETG API (RateHawk) | Travelport TripServices APIs | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 45 | 19 | ETG API (RateHawk) +26 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 85 | 84 | ETG API (RateHawk) +1 |
| Agent ergonomics | 13% (16.2 this run) | 69 | 51 | ETG API (RateHawk) +18 |
| Security & auth | 14% (17.5 this run) | 41 | 47 | Travelport TripServices APIs +6 |
| Payments & pricing | 10% (12.5 this run) | 10 | 20 | Travelport TripServices APIs +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 65 | 56 | ETG API (RateHawk) +9 |
| Transparency & trust | 7% (8.8 this run) | 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)

1. Call `/api/b2b/v3/overview/` first. It lists the endpoints the key may use and each one's request limit.
2. Keep sandbox IDs, keys and hashes inside `api-sandbox.ratehawk.com`. Sandbox region IDs are limited to 2011, 2395, 2734 and 6053839.
3. 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.
4. Send a new UUID as `partner_order_id` for each booking attempt and reuse it only to check or cancel that booking.
5. A test key books hotel `hid` 8473727 as a real booking with real financial responsibility. Cancel it afterwards.

### Travelport TripServices APIs

1. Request one token and cache it for 24 hours. Travelport declines certification for refreshing more often than every 23 hours without a stated reason
2. Send `Accept-Encoding: gzip, deflate` and `XAUTH_TRAVELPORT_ACCESSGROUP` (or `TVP-PCC-CORE`) on every call. Production traffic without compression is refused
3. 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
4. Commit a workbench within 30 minutes or it expires, and read `Result/Error` in the body even on HTTP 200
5. 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.


## For agents

- 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
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "ratehawk", "b": "travelport"}`. From a terminal: `anchor compare ratehawk travelport`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/ratehawk.json and https://www.anchorterminal.com/api/v1/tools/travelport.json

## Other comparisons with ETG API (RateHawk) or Travelport TripServices APIs

- [Booking.com Demand API vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/booking-demand-api-vs-ratehawk.md)
- [Booking.com Demand API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport.md)
- [Duffel Flights and Stays API vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/duffel-vs-ratehawk.md)
- [Expedia Group Rapid API vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/expedia-rapid-vs-ratehawk.md)
- [Expedia Group Rapid API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/expedia-rapid-vs-travelport.md)
- [Hotelbeds Hotel Booking API vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/hotelbeds-vs-ratehawk.md)
- [Hotelbeds Hotel Booking API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/hotelbeds-vs-travelport.md)
- [LetsFG vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/letsfg-vs-ratehawk.md)
- [LiteAPI (Nuitee Connect) vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/liteapi-vs-ratehawk.md)
- [LiteAPI (Nuitee Connect) vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/liteapi-vs-travelport.md)
- [ETG API (RateHawk) vs Skyscanner Travel APIs](https://www.anchorterminal.com/compare/ratehawk-vs-skyscanner.md)
- [Duffel Flights and Stays API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/duffel-vs-travelport.md)
- [FlightClaw vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/flightclaw-vs-travelport.md)
- [Kiwi.com MCP Server vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/kiwi-mcp-vs-travelport.md)
- [LetsFG vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/letsfg-vs-travelport.md)
- [Skyscanner Travel APIs vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/skyscanner-vs-travelport.md)
- [FlightClaw vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/flightclaw-vs-ratehawk.md)
- [Kiwi.com MCP Server vs ETG API (RateHawk)](https://www.anchorterminal.com/compare/kiwi-mcp-vs-ratehawk.md)