The API Report CardAPI Index
Travelport

Travelport API

Global Distribution System (GDS) / Travel Retailing / NDC Aggregation · travelport.com

Travelport publishes two API stacks: the legacy SOAP/XML Universal API and JSON REST Travelport+ APIs (Flights, Stays, Pay). Production requires provisioning, mandatory certification, and 15 business days' notice, with every credential locked to a PCC Access Group's content.

Last verified: July 2026Hospitality & Travel
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceGOODTwo parallel stacks: the long-standing SOAP/XML Universal API and newer JSON REST APIs for air, hotel, and payments.
AccessFAILContract-based provisioning, then mandatory certification with captured logs and 15 business days' notice before production.
CoveragePOORCredentials are bound to a PCC Access Group; you only see the points of sale, currencies, and carriers it is provisioned for.
AuthFAILThe SOAP uAPI still runs HTTP Basic auth scoped to a Target Branch; OAuth2 tokens on the JSON stack last 24 hours.
Docs & DXGOODPublic portal at developer.travelport.com with DevKits, Postman collections, and mirrored support docs; sandbox requires provisioning.
StabilityMIXEDThe SOAP monolith remains load-bearing while the JSON stack matures; integrations straddle two API generations.
Supergood: Travelport has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Travelport scores F on the API Report Card. Travelport publishes two API stacks: the legacy SOAP/XML Universal API and JSON REST Travelport+ APIs (Flights, Stays, Pay). Production requires provisioning, mandatory certification, and 15 business days' notice, with every credential locked to a PCC Access Group's content.

Tried to integrate with Travelport?