Duffel Flights and Stays API vs Travelport TripServices APIs

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.

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