Travelport API Integration
Add the airlines Travelport distributes to your platform through one REST flight API. FlightOTA queries Travelport Galileo alongside Amadeus, Sabre and direct airline connections, so your integration speaks JSON once instead of Travelport's own interfaces.
Travelport Galileo without the Universal API build
Travelport's Galileo system distributes full-service airline content to agencies worldwide, reached through Travelport's Universal API. A direct build means XML development, a Travelport agreement and certification before your first ticket, and then keeping the integration current.
FlightOTA already queries Travelport Galileo as one of the sources behind POST /flights/search, next to Amadeus MasterPricer, Sabre Bargain Finder Max and our NDC and low-cost direct connects. Travelport offers arrive in the same JSON shape as every other: integer minor-unit prices in your billing currency, airport-local flight times, baggage per segment and fare rules on request. A booking held in Travelport returns its record locator as gds_reference.
Choose this integration when your agencies work with Galileo PNRs, when you want Travelport content beside other sources without running separate booking flows, or when you are replacing an XML integration with one JSON API.
Moving a Travelport flow onto one JSON API
The same five calls as every other airline source, with the Travelport record locator on the booking.
- 01
Map your search to one request
Where Universal API needs its own request structure, FlightOTA takes slices, passengers, cabin and fares in one JSON body and shops Travelport Galileo with every other source.
- 02
Read offers in one shape
Travelport offers arrive like all others: money as integer minor units in your billing currency, flight times local to the airport, baggage per segment and fare rules on request.
- 03
Book, hold, issue
The booking is held with hold_expires_at and issued from your deposit before then; gds_reference carries the Travelport record locator for your back office.
- 04
Keep one after-sales flow
Void, refund and reissue requests use the same calls as for Amadeus, Sabre, NDC and LCC bookings, so your service desk learns one process.
What the Travelport integration covers
Travelport Galileo content through the Flights API, paid from your deposit.
- Travelport Galileo content inside the unified flight search
- gds_reference: the Travelport record locator on bookings held there
- One JSON offer shape shared with Amadeus, Sabre, NDC and LCC sources
- Money in integer minor units, flight times local to the airport
- Fare rules, baggage per segment and fare families on request
- Held bookings issued from your deposit before hold_expires_at
- Void, refund and reissue through the same booking
- Errors in one envelope you can branch on by code
Travelport integration questions
Related integrations and APIs
Replace the XML build with one JSON flight API
Walk us through your current Travelport flow and we will show the same booking made through the API on the sandbox.