Search Travelport JSON API (uAPI) for multi-segment itineraries and retrieve branded fare bundles
domain: developer.travelport.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with Travelport Universal API using HTTP Basic Auth with target branch credentials
POST an AirSearchAvailability request to the JSON endpoint specifying SearchModifiers with MaxSolutions
Parse the AirSegmentList and AirPricingInfo collections from the response envelope
Send a secondary AirPricingSolution request to retrieve BrandList and BrandInfo for each fare family
Map BrandedFareIdentifier to the corresponding BrandAttribute list for display
Use the resulting ProviderReservationInfo key to initiate a CreateReservation call
Known gotchas
Travelport JSON API uses a proprietary envelope with TypeSearchLocation objects; coordinate keys must match the correct namespace or the GDS will return a schema validation fault
Branded fare data is not returned in the initial availability search; a second AirPricingSolution call with a BrandModifiers element is required
Branch codes (TargetBranch) control which GDS content is accessible; wrong branch codes yield empty results without an error
Give your agent this knowledge — and 15,800+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?