Travelport API Integration: A 2027 Guide for Agencies
Travora Hub · November 22, 2026
Reviewed by Muhammad Uzair, Founder and CEO, Travora Hub
What a Travelport API integration gives a travel agency, what you need first, and how flight and hotel search and booking work on TripServices.
A Travelport API integration connects your booking website or back office to Travelport, so customers and staff can search flights and hotels, see live prices and book, without an agent typing into a GDS screen. Travelport's current API platform is called TripServices. It covers flights, stays and payments, uses OAuth 2.0 for sign-in, and gives you a pre-production environment to test in before you go live.
This guide explains what a travel agency gains from the integration, what you need before you start, and how the search and booking steps work. It is based on Travelport's public developer documentation as we read it in November 2026 while building our own connection.
A note on us: Travora Hub is independent and not affiliated with Travelport. Our Travelport connection is still being built and is not available to customers yet. Nothing here should be read as saying it is live.
What an agency gets from a Travelport integration
- GDS and NDC fares on your own website. Customers search and see the same airline content your agents see, with your markup added.
- Your own fares online. Private and negotiated fares attached to your Travelport account can appear in website results.
- Fare families. Branded fares can be shown side by side, which helps sell the fare with bags or free changes.
- Hotels from the same supplier. The Stays API returns hotel content from the Travelport GDS and Booking.com.
- Less manual work. Bookings made online create the reservation directly, so staff do not retype them.
- One record for servicing. Staff can open the same reservation in Smartpoint to handle changes.
For what Travelport offers in general, and who can get an account, start with Travelport for travel agencies.
What you need before you start
- A Travelport customer agreement. Travelport's developer portal offers trial access for exploring. To build for real you become a customer through its sales team.
- A PCC. Your pseudo city code identifies your agency, and Travelport provisions API access against it.
- API credentials. Travelport issues production and pre-production credentials at provisioning, and you manage them in its credentials access manager.
- A plan for ticketing. An IATA-accredited agency tickets under its own authority. An agency without accreditation needs a consolidator arrangement. Settle this before development, because it decides how payment to the airline works.
- A developer who has worked with flights. Fare rules, schedule changes and refunds take longer than the first successful booking.
The APIs in short
| API | What it covers |
|---|---|
| TripServices Flights | Search, price, book, ticket and service flights from GDS and NDC sources |
| TripServices Stays | Hotel search, availability, rates and booking |
| TripServices Pay | Payment within the booking flow |
| Universal API | Travelport's older XML API, which many existing integrations still use |
Travelport announced TripServices as its cloud-native API platform in June 2026. You will also see the name "JSON APIs" in older documentation for the same family. For a new build, ask Travelport which API it will provision for you.
How sign-in works
TripServices uses OAuth 2.0. Your server sends the credentials Travelport gave you and receives a token, then sends that token with every request. Travelport's documentation says a new token is required every 24 hours. Store the token on your server and reuse it until it expires. Do not request a new one for each search, and never put the credentials in the browser or a mobile app.
The flight flow, step by step
- Search. Send the route, dates, passengers and cabin. Travelport returns a catalogue of offers. Each offer points to its flights, fare brand and terms, so your server has to join these parts into a simple result card for the customer.
- Price. When the customer picks an offer, confirm the price and availability again. Fares move, and the search result is not a guarantee.
- Start a booking. Travelport uses a "workbench", a working session where you build the reservation piece by piece.
- Add the offer and travellers. Add the chosen offer to the workbench, then the passenger names, dates of birth, contact details and passport details where the route needs them.
- Add payment. Take the customer's money through your own payment gateway first. Then add the form of payment that Travelport and the airline will accept for your agency.
- Commit. Committing the workbench creates the reservation and returns the record locator. Depending on your setup, the ticket is issued at this point or within the time limit the fare allows.
- After the sale. Retrieve the booking, cancel it, or void the ticket within the void period. Travelport documents exchange steps for NDC bookings. What is possible varies by airline.
The hotel flow
Hotels follow a shorter path: search by location and dates, open a property for its rooms and rates, check the chosen rate again, then book. Travelport's Stays guide names three guarantee types, "guarantee required", "deposit required" and "prepay required", and the API checks whether the type changed between search and booking. Show the customer which one applies before they pay. More detail is in Travelport hotels: what agencies can book.
Mistakes that slow teams down
- Showing the raw response to the browser. Search responses are large. Have your server reduce them to the fields a result card needs.
- Trusting the search price. Always price again before booking and tell the customer if the fare changed.
- Skipping pre-production. Complete a full test booking and ticket in the test environment before you ask for production access.
- Booking before the customer has paid. Capture payment first, then commit, and have a refund path ready for the rare case where the commit fails.
- No trace of what happened. Log an identifier for every request so Travelport's support team can find it when you raise a case.
- Treating NDC and GDS as the same. Seats, bags and changes differ between the two and between airlines. Test each airline you plan to sell.
The same lessons apply to any supplier, and our travel API integration guide walks through them in general terms.
Cost and time
Travelport does not publish API pricing. Ask its sales team about fees per booking or per search, minimum volumes and any charge for the API itself. On your side, budget for the build, for testing each airline, and for ongoing upkeep. A simple search-and-book flow for one content source is the smaller part. Changes, refunds and schedule updates are where most of the work goes.
Build it yourself or use a platform?
Building gives you control and suits an agency with developers and steady flight volume. A platform suits an agency that wants to sell online without a technical team, but check which suppliers it truly has live.
On Travora Hub today, flights are live through Duffel and PKFARE on the agency's own accounts, as described on the flight booking software page. Travelport is in development and not yet available. We will update this article when that changes.
Frequently asked questions
What is the Travelport API called?
The current platform is Travelport TripServices, with APIs for flights, stays and payments. The older XML service is the Universal API.
How does Travelport API authentication work?
It uses OAuth 2.0. You exchange your credentials for a token and send the token with each request. Travelport says a new token is required every 24 hours.
Does Travelport have a test environment?
Yes. Travelport provides pre-production credentials alongside production ones, so you can test searches and bookings before going live.
Can I get Travelport API access without being a customer?
The developer portal offers trial access for exploring the APIs. To sell real travel you need a Travelport agreement and a PCC.
Do I need IATA accreditation to integrate Travelport?
Not always. Travelport has a package for non-IATA agencies that ticket through consolidators. How ticketing and payment work for your agency should be agreed with Travelport before you build.
Is Travelport live on Travora Hub?
No. The connection is being built and is not available to customers yet.
To see a flight and hotel booking flow from the customer's side, open the live demo.