Integrations · GDS
Travelport integration for Galileo-heritage agencies and new builds
Many agencies still say 'Galileo' when they mean Travelport. The brand changed, the host codes and habits did not. Voraal's Travelport integration connects your existing Travelport credentials to Rezencia and Avunzo, so the content you already sell becomes part of one booking engine with your other channels.
Built for
- Galileo-heritage agencies
- Consolidators
- OTAs
- TMCs
- Umrah operators
In brief
How does Travelport integration work with Voraal?
Voraal connects your agency's existing Travelport credentials and PCC to its core, so your fares, office set-up and agreements carry over. Travelport content is then normalised with Amadeus, Sabre, NDC and low-cost results in Rezencia, ticketed by rule and serviced through automated voids, refunds and reissues. Developers reach the same content through Voraal's Avunzo API instead of integrating Travelport's APIs directly.
By the Voraal team · Updated
Travelport, Galileo and Travelport+
Travelport is a GDS headquartered in Langley, in the UK. It was formed around the Galileo GDS, acquired Worldspan in 2007 and also operated Apollo, the system long used in North America. In 2021 Travelport unified these under Travelport+, replacing the three legacy brands; the former Galileo designator, 1G, is used for the new system. Travelport has been privately held since 2019, when affiliates of Siris Capital Group and Elliott Management acquired it.
Developers have two families of Travelport APIs. The Universal API is a long-established SOAP/XML set of services for air, hotel, car and rail. The newer JSON APIs are RESTful, versioned and documented, grouped into flights, stays and payments, with authentication through OAuth 2.0 credentials tied to the agency's access group and PCC. A Travelport integration today has to decide which family fits the workflow, particularly for NDC.
Travelport API options at a glance
| Universal API | JSON APIs | |
|---|---|---|
| Style | SOAP and XML | REST and JSON |
| Coverage | Air, hotel, car and rail, with supporting services | Flights, stays and payments families |
| Credentials | User ID, password and branch code linked to the PCC | OAuth 2.0 client credentials and an access group linked to the PCC |
| NDC | Limited | Primary route for NDC booking |
| Through Voraal | Your team does not call it directly | Your team does not call it directly; content arrives via Rezencia or Avunzo |
Technical details summarise Travelport's public documentation and integration guides; Travelport's current terms apply.
How Voraal connects Travelport
- 01
Review your agreement and PCC
Your agency's Travelport agreement, PCC and credentials are reviewed, including which content and ticketing rights they carry.
- 02
Connect existing credentials
Rezencia works with existing Travelport credentials, so current fares, office set-up and agreements carry over.
- 03
Normalise Travelport data
Fares, availability, PNRs and NDC orders are mapped into the single model used for every other channel.
- 04
Configure distribution
Set markups, commissions and credit for each agent and sub-agent selling Travelport content through portals.
- 05
Ticket and service by rule
Rule-based ticketing selects the issuing GDS per airline; servicing runs through one void, refund and reissue flow.
Key features with Travelport connected
Content beside other channels
Travelport results merged with Amadeus, Sabre, NDC and LCC content in one response.
Branded agent portals
Sub-agents sell your Travelport content under their own brand within your rules.
Rule-based ticketing
Issue on Travelport for the airlines where it is your best option.
PNR import and queues
Bring existing PNRs in and work queues and time limits from the admin.
Terminal access
A GDS terminal inside the admin for staff who prefer commands.
Margin visibility
Folio6 shows revenue, supplier cost and margin by route, supplier and agent.
Travelport in Pakistan
Galileo has a long history in Pakistan, where Travelport has worked with a local distribution partner for the Galileo GDS, and many agency staff learned their trade on it. Agencies that issue tickets do so through BSP Pakistan under their IATA accreditation, or rely on a consolidator. The practical result is that a lot of Pakistani flight inventory, PNRs and ticketing habits still sit in Travelport.
Moving that operation onto a platform does not mean giving up Travelport. Rezencia connects to it, imports existing PNRs, and adds the agent portals, credit control and ledgers that a terminal does not provide. Teams building their own front end reach the same Travelport content through the Avunzo API. For consolidators, B2B flight booking platform shows how this content is distributed to agents, and how to integrate multiple airline suppliers explains combining Travelport with other channels.
Direct Travelport API build vs connecting through Voraal
Integrating Travelport APIs yourself
- Choose between Universal API and JSON APIs, possibly both
- Certification scenarios and move-to-production with Travelport
- Your own mapping for PNRs, NDC orders and servicing
- Other GDS and LCC content built separately
Connecting through Rezencia or Avunzo
- One REST/JSON API or a ready platform on top
- Supplier changes and certifications handled by Voraal
- One order model for every channel
- Ticketing, servicing, ledgers and portals included
How Voraal delivers this
The products behind it.
Is Travelport the same as Galileo?
Galileo was one of Travelport's three GDS systems, alongside Apollo and Worldspan. Since 2021 they have been unified under Travelport+, and the former Galileo designator 1G is used for the new system. Many agents still call it Galileo.
Do we need a Travelport agreement to sell Travelport content through Voraal?
Yes, for GDS access through Rezencia your agency connects its own Travelport credentials and agreement. Voraal is the technology platform and does not resell Travelport subscriptions.
Do we have to choose between Universal API and the JSON APIs?
Not if you connect through Voraal. Your team works with Rezencia or the Avunzo API, and Voraal manages the connection to Travelport underneath.
Can Travelport NDC content be booked through Voraal?
Where NDC content is enabled for your Travelport set-up and connected, it is mapped into the same order model as classic bookings. Availability varies by airline and agency configuration.
Can we migrate existing Travelport PNRs into Rezencia?
Yes. PNR import and transfer bring active bookings into Rezencia, so servicing, ledgers and reconciliation continue on the platform.
Sources and further reading
- Travelport (Wikipedia)
- Travel Weekly: Travelport unifies services in new Travelport+ platform
- Travelport RESTful/JSON APIs documentation
- AltexSoft: Travelport API integration
- Business Travel News Europe: Travelport safeguards Pakistan distribution
- IATA: Billing and Settlement Plan (BSP)
Regulations, airline programmes and supplier terms change. Confirm requirements with the relevant authority or supplier before acting. Contact [email protected] if you spot something out of date.
Let’s build what comes next.
Tell us how your travel business works. We’ll recommend the right products and walk you through them on your own use case.