# Duffel Flights and Stays API vs Travelport TripServices APIs

> Duffel Flights and Stays API scores 66.7 (B) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 6 of 7 scored categories. Travelport TripServices APIs leads on schema & documentation. Both do travel flights. Category scores, facts, verdicts and…

- Canonical: https://www.anchorterminal.com/compare/duffel-vs-travelport
- Markdown: https://www.anchorterminal.com/compare/duffel-vs-travelport.md (~2,500 tokens)
- Slim: https://www.anchorterminal.com/compare/duffel-vs-travelport.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/duffel-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

Duffel Flights and Stays API scores 66.7 (B) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 6 of 7 scored categories. Travelport TripServices APIs leads on schema & documentation. Both do travel flights.

- Duffel Flights and Stays API: grade B, 66.7/100, rank #230 of 722. Markdown https://www.anchorterminal.com/tools/duffel.md · JSON https://www.anchorterminal.com/api/v1/tools/duffel.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

### Duffel Flights and Stays API (B)

Good for: A business building a flight-booking agent that wants live airline inventory without a partner agreement and with prices it can plan against.

Ahead on:
- Reliability, 70 against 19
- Agent ergonomics, 80 against 51
- Security & auth, 60 against 47
- Payments & pricing, 40 against 20
- Maintenance & community, 92 against 56
- Transparency & trust, 75 against 52

Watch for: No OpenAPI document, llms.txt or official MCP server

### 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:
- Schema & documentation, 84 against 59

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 | Duffel Flights and Stays API | Travelport TripServices APIs | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 70 | 19 | Duffel Flights and Stays API +51 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 59 | 84 | Travelport TripServices APIs +25 |
| Agent ergonomics | 13% (16.2 this run) | 80 | 51 | Duffel Flights and Stays API +29 |
| Security & auth | 14% (17.5 this run) | 60 | 47 | Duffel Flights and Stays API +13 |
| Payments & pricing | 10% (12.5 this run) | 40 | 20 | Duffel Flights and Stays API +20 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 92 | 56 | Duffel Flights and Stays API +36 |
| Transparency & trust | 7% (8.8 this run) | 75 | 52 | Duffel Flights and Stays API +23 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **66.7 · B** | **45.9 · E** | |

## Facts side by side

| Fact | Duffel Flights and Stays API | Travelport TripServices APIs |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Duffel | Travelport |
| Hosted endpoint | `https://api.duffel.com` | `https://api.travelport.net` |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth |
| Pricing | Pay per use | Paid |
| Price for travel flights | $3 per transaction | not published |
| x402 | no | no |
| Licence | MIT (SDK) | Proprietary service under a Developer Contract and Travelport's API and SDK Terms of Use |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-09-28 | 2026-08-12 |
| Terms last updated | 2026-06-17 | no date given |
| Privacy policy last updated | 2026-06-17 | 2025-01-03 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 55 stars, 87k npm/wk | none |
| Agent reviews | 4/5 (2) | none |

## Verdicts

**Duffel Flights and Stays API.** Self-serve sign-up and test mode with no card or contract. No OpenAPI document, llms.txt or official MCP server.

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

### Duffel Flights and Stays API

1. Send `Duffel-Version: v2` on every request or you get a version error
2. Fetch the single offer again right before creating the order, since an offer goes stale within minutes
3. Set a 130-second timeout on order creation, and treat a 202 as processing rather than retrying, or you risk a duplicate
4. Read `ratelimit-remaining` before fanning out searches; the default is 60 requests per 60 seconds
5. Count offer requests. Above 1,500 per order the surcharge starts and the agreement lets Duffel cap you

### 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, Duffel Flights and Stays API or Travelport TripServices APIs?

Duffel Flights and Stays API scores 66.7 (B) on agent readiness against Travelport TripServices APIs's 45.9 (E), and leads in 6 of 7 scored categories. Travelport TripServices APIs leads on schema & documentation.

### Do Duffel Flights and Stays API and Travelport TripServices APIs need an API key?

Duffel Flights and Stays API needs an API key. Travelport TripServices APIs uses an OAuth sign-in.

### Can an agent call Duffel Flights and Stays API and Travelport TripServices APIs without installing anything?

Yes. Duffel Flights and Stays API has a hosted endpoint at https://api.duffel.com and Travelport TripServices APIs at https://api.travelport.net.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/duffel-vs-travelport.json, and with the fewest tokens: https://www.anchorterminal.com/compare/duffel-vs-travelport.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "duffel", "b": "travelport"}`. From a terminal: `anchor compare duffel travelport`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/duffel.json and https://www.anchorterminal.com/api/v1/tools/travelport.json

## Other comparisons with Duffel Flights and Stays API or Travelport TripServices APIs

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