Travelport integration
Travelport API integration for agencies and OTAs
A Travelport API integration puts Travelport flights and hotels inside your own booking engine. PHPTRAVELS handles the search page, branded fares, PNR booking, ticketing and servicing, on your own Travelport agreement.
- TripServices Flights and Stays
- Branded fares and upsells
- PNR, ticketing and servicing
- Markups and agent rates
Travelport platforms
Which Travelport platform does a new integration use?
Travelport has offered several ways in over the years. Each stop on this rail says what the platform is and what it means if you start a Travelport project now. Pick a stop to read more.
Galileo · What it is
One of the Travelport GDS host systems. Agencies book air, read fares and work queues on it through a pseudo city code (PCC).
For a new integration today
You do not connect to the host itself. Galileo bookings, PNRs and queues are reached through the Travelport APIs your agreement provisions.
In PHPTRAVELS
Galileo fares, PNRs and queues show in the flights admin like any other source.
Apollo · What it is
Another Travelport host system, with its own agency base, PCCs and booking formats.
For a new integration today
Treat it like Galileo: the host sits behind the API. Confirm with Travelport which host your PCC is on before scoping the work.
In PHPTRAVELS
Same booking flow and the same screens. The host behind your PCC is a setting, not a rebuild.
Worldspan · What it is
The third Travelport host system, with its own PCCs and formats.
For a new integration today
Ask Travelport which API products your Worldspan PCC is provisioned for, since coverage can differ by product and market.
In PHPTRAVELS
Same search, checkout and servicing screens as the other hosts.
Universal API · What it is
The Travelport XML family of APIs, delivered with WSDL and schema files, an SDK and code samples.
For a new integration today
Many live agencies still run on it. For a new build, ask Travelport first, because its developer portal now leads with TripServices.
In PHPTRAVELS
An existing Universal API connection can keep running while a newer one is built beside it.
Travelport+ JSON APIs · What it is
The Travelport JSON family, built as smaller REST services. One search can return GDS and NDC content, and branded fares arrive as brands with upsell offers.
For a new integration today
Earlier releases ran as an early adopter programme, as Travelport's own notes state. The current Flights API reference is version 11.
In PHPTRAVELS
Brands and upsells map straight into the fare family columns shown below.
TripServices · What it is
How the Travelport developer portal presents its APIs today: Flights, Stays and Pay, with OAuth 2.0 sign-in and separate pre-production and production environments.
For a new integration today
The usual starting point for a new build. Travelport issues trial or full credentials at provisioning, and an access token lasts 24 hours, as Travelport states.
In PHPTRAVELS
New Travelport connections are planned on the current Flights and Stays APIs, unless your agreement says otherwise.
Facts from developer.travelport.com and support.travelport.com, checked October 2026. Product names and availability change, so confirm your options with your Travelport account manager.
Branded fares
Fare families, side by side in the search result
Travelport returns branded fares with their own baggage, change and refund terms. PHPTRAVELS lays them out as columns, so a traveller sees what the extra money buys before choosing.
London (LHR) to Dubai (DXB)
14 Nov · 1 adult · Economy
07:55 → 18:40Non-stop · 7h 45m
| Basic–per adult | Standard–per adult | Flex–per adult | |
|---|---|---|---|
| Cabin bag | 1 × 7 kg | 1 × 7 kg | 1 × 7 kg |
| Checked bag | Not included | 1 × 23 kg | 2 × 23 kg |
| Changes | Not allowed | Fee applies | Free |
| Refund | Not refundable | Not refundable | Refundable |
| Seat choice | For a fee | Standard seats | All seats |
Sample data. Brand names, prices and terms come from the airline through Travelport.
Brands from the fare data
Brand names and attributes come from the response, so a fare is never called Flex unless the airline files it that way.
Upsell offers
The next fare up, in another brand or cabin, can be shown as an upgrade at checkout.
Full rules one click away
Agents can open the complete fare rules text before they book or change a ticket.
One layout for every source
Fares from NDC flights booking system and other GDS use the same columns, so travellers compare like for like.
At a glance
Travelport API integration in short
A Travelport API integration is a project, not a switch. You sign an agreement with Travelport, Travelport provisions your credentials, and your booking engine calls its APIs to search, price, book and ticket. PHPTRAVELS is that booking engine: a self-hosted travel platform with a public site, an agent portal and an admin, all ready for the Travelport connection.
If you already run a GDS desk on Galileo, see Galileo software. If your agents work on Apollo, see Apollo GDS software. Travelport is also one source among many in Flight booking software, so it can sit beside Amadeus, Sabre and NDC suppliers.
- API products
- Flights, Stays and Pay under the TripServices name
- Format
- REST with JSON; the older Universal API uses XML
- Sign-in
- OAuth 2.0 access token, renewed every 24 hours
- Environments
- Pre-production and production, each with its own credentials
- Access
- An access group tied to your PCC, sent as a header on each call
- Air content
- GDS, NDC and low-cost carriers; Travelport states 400+ airlines
- Contract
- Your own agreement and fees with Travelport
- In PHPTRAVELS
- Flights and hotels engine, B2C site, B2B portal and admin, ready to connect
Booking flow
How a Travelport booking runs through PHPTRAVELS
Each step pairs a Travelport API task with the screen where your team sees the result, plus the detail that most often goes wrong.
| Step | Travelport task | Where it shows in PHPTRAVELS | Watch out for |
|---|---|---|---|
| 01Search | Shop fares for the route, dates and passengers | Results list with fare family columns | Cache only where it is safe; fares move fast |
| 02Price | Confirm the chosen offer and its taxes | Checkout, with your markup added | Show the confirmed price, not the search price |
| 03Book | Create the reservation with traveller details | Booking record with the PNR locator | Names and dates of birth exactly as in the passport |
| 04Ticket | Issue the ticket, or hold for later | Ticket numbers and e-ticket email | Ticketing time limits on held bookings |
| 05Change | Modify the reservation or exchange the ticket | Servicing panel in the admin | Fare difference and penalties from the fare rules |
| 06Cancel | Cancel the booking and process any refund | Refund record for finance | Void windows and refund rules differ by fare |
Your starting point
Already on Universal API, or starting fresh?
The right plan depends on what you run today. Here is how the two most common cases differ.
You already run Universal API
- Keep the live connection running while the new one is built
- Map your current PCCs, markups and queues before you change anything
- Ask Travelport whether to migrate now or extend what you have
- Run both side by side in pre-production and compare results
You are starting fresh
- Request trial credentials and test realistic flows early
- Plan on the current TripServices APIs from day one
- Start lean: air search, price, book and ticket, then servicing
- Decide early if agents will book too, through a B2B travel portal
Before you start
Travelport go-live checklist
Tick what you already have. The rest is what we plan with you in the first call.
Costs
What a Travelport integration costs
There are three separate bills. Only one of them comes from us, and it is a one-time licence.
PHPTRAVELS licence
One-time, paid to PHPTRAVELS
Full source code, self-hosted, for every plan below.
- StartupOne-time licence
- AgencyOne-time licence
- EnterpriseOne-time licence
Travelport fees
Paid to Travelport
Set in your Travelport agreement. We never see or set these terms.
Integration work
Quoted per project
Scoped once we know your verticals, servicing needs and certification steps.
Comparing suppliers? Read Travel APIs first.
FAQ
Travelport API integration questions
What agencies and technical teams ask before connecting Travelport.
Talk to salesIt connects Travelport content to your own travel platform, so you can search and price fares, create PNRs, issue tickets and service bookings. Hotel content is added where your Travelport agreement covers it.
The Travelport developer portal now leads with TripServices, its REST and JSON APIs for Flights, Stays and Pay, so most new builds start there. If you already run Universal API, ask Travelport whether to migrate or extend, and we plan around their answer.
They are Travelport host systems behind the APIs, not separate integrations. Your PCC sits on one of them, and its bookings, queues and fare rules reach PHPTRAVELS through the Travelport APIs your account is provisioned for.
Yes. Fare families such as Basic, Standard and Flex are shown as columns in the results, with baggage, change, refund and seat rows taken from the fare data, plus upsell offers where Travelport returns them.
Yes. Pricing, documentation and credentials come from your agreement with Travelport. You can ask Travelport for trial credentials to test first. We help you plan the scope, environments and certification around it.
It depends on the verticals, servicing scope and certification steps. A lean first release with search, price, book and ticket goes live sooner when credentials, test cases and business rules are agreed early.
The PHPTRAVELS licence is a one-time payment. Travelport fees come from your own agreement with Travelport, and the integration work is quoted once the scope is clear.
Yes. Sub-agents book with their own markups, commissions and credit limits, and PNR servicing stays in the same admin as your public site.
Keep exploring
More from the platform
- Flights APIGDS, NDC and consolidator flight APIs on one platform
- Galileo reservation systemGalileo holds, ticketing and after-sales in one admin
- Amadeus connector setupKeys, environments and setup for the Amadeus module
- Sabre API integrationSabre APIs for shop, price, book and ticket in your portal
- NDC flights booking systemSell NDC airline offers, ancillaries and servicing
- FlightsGDS and NDC ticketing