Skyscanner Travel APIs vs Travelport TripServices APIs

Skyscanner Travel APIs

Thirteen documented search APIs cover flights, hotels and car hire behind one x-api-key header, with default rate limits published per endpoint and no usage fee. Access needs an approved application, an audience above 100,000 monthly users and a commercial agreement, and the usage guidelines bar live-price calls made without a user action. Booking happens on supplier sites.

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.

Skyscanner Travel APIs

1. Send the key in the x-api-key header on every call to https://partners.api.skyscanner.net. CORS is not supported, so call from a server
2. Create a live search only when a user has given origin, destination and exact dates. Use the indicative price endpoints for open-ended questions
3. Poll /search/poll/{sessionToken} until status is RESULT_STATUS_COMPLETE, and replace earlier results only when action is RESULT_ACTION_REPLACED
4. Start a new session when a poll returns 400. Flight session tokens last about an hour and hotel sessions at most 15 minutes
5. Pass each deepLink to the traveller unchanged, since altered encoding breaks Impact tracking, and never put personal data in subid2

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