Odessia vs Travelport TripServices APIs

Odessia

Odessia is a free travel concierge that books as a registered travel agent, watches prices and award seats, and keeps a public status page with a clean record since July. No outside agent can call it, standing authorisations let it pay without asking each time, and no changelog was found.

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.

Odessia

1. Don't plan to call Odessia from another agent. It answers only its signed-in owner on the web, by message or by email.
2. Check whether the owner has set a standing authorisation before assuming a booking will wait for approval.

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