Apollo GDS integration
Apollo software for agencies that book on the Apollo GDS
Bring Apollo, the Travelport GDS, into your own booking engine: fare shopping, PNR creation, ticketing and queues on a self-hosted platform, with changes tested in pre-production before your agents see them.
- Apollo on Travelport
- PNRs, ticketing and queues
- Pre-production and production
- Markups and agent rates
How the integration works
From the Apollo terminal to an online booking flow
Many agencies still work Apollo through a terminal. An integration puts the same content behind a search page, an agent portal and an admin. We confirm what your Travelport agreement provisions for Apollo, map fares and booking references into the PHPTRAVELS flights module and release the connection in stages, with logs and a rollback path at each step.
- Confirm your Apollo PCC, markets and the content your agreement covers
- Map fares, fare rules, baggage and PNR references into the admin
- Test sample itineraries and edge cases in pre-production
- Go live in stages, starting with your own agents
- Monitor errors, queues and bookings after go-live
- Environment
- Pre-production
- PCC
- 1V · ••••
- Endpoint
- Travelport API · Apollo host
- API credentials
- User and password: ••••••
- Rollout
- Own agents first
Shopping and booking
Apollo fares, priced and booked in one flow
Apollo responses are normalised into one results list, priced again before payment and booked into a PNR your team can service from the admin.
- 1VEconomy · 06:10 → 10:35Non-stop · personal item only–per adult
- GDSEconomy · 09:45 → 16:201 stop · 1 checked bag–per adult
- First · 13:05 → 17:30Non-stop · 2 checked bags–per adult
Fare shopping and pricing
Availability and fares from Apollo, with a price check before checkout so the fare shown is the fare booked.
PNR creation and retrieval
Bookings stored with the Apollo record locator, traveller details and ticket numbers for later servicing.
Ticketing and queues
Issue tickets or place bookings on queues, with pending and on-hold bookings visible to your team.
Changes and refunds
Controlled change, refund and void flows with notifications and an audit trail for each action.
Release lifecycle
Ship Apollo changes without disrupting sales
New markets, fare rules and booking flow updates follow the same controlled path from test to live.
Scope
Agree what changes: a market, a fare type or a step in the booking flow.
Stage
Run the change in pre-production with real test itineraries.
Approve
Your team signs off on the test results before release.
Release
Go live for your own agents first, then for customers and sub-agents.
Monitor
Watch supplier errors, failed bookings and ticketing queues.
Roll back
Keep the previous configuration ready to restore if results degrade.
Content sources
Apollo alongside your other flight suppliers
Apollo is one source in the flights module, so other GDS and flight APIs can share the same search and checkout.
Travelport: Apollo and Galileo
Apollo and Galileo content through your own Travelport agreement and credentials.
Amadeus and Sabre
Other GDS connections can feed the same results list and booking flow.
Consolidators and NDC
Consolidator contracts and NDC content sold next to Apollo fares.
Flight suppliers you can connect:
Seeru
Amadeus
Duffel
Google Flights
Kayak
Kiwi
Mystifly
PKfare
Sabre
TBO Holidays
Travelport
Back office
Run Apollo sales from one admin
What agents, managers and finance need after the booking is made.
Markups and commissions
By route, airline, cabin, agent or channel, as fixed amounts or percentages.
Agents, branches and roles
Agent, branch, admin and finance accounts, each with its own permissions.
Logs and audit trail
Supplier errors, booking changes and refunds logged with user and time.
Compare
Apollo terminal only vs PHPTRAVELS
A terminal is built for trained agents. An online platform lets customers and sub-agents book the same content.
| Area | Apollo terminal only | PHPTRAVELS |
|---|---|---|
| Who can book | Apollo terminal onlyTrained agents using terminal formats | PHPTRAVELSCustomers online, sub-agents in a B2B portal and your own staff |
| Markups | Apollo terminal onlyTypically worked out by hand or in spreadsheets | PHPTRAVELSRules by route, airline, agent or channel, applied automatically |
| Payments | Apollo terminal onlyTaken separately from the booking | PHPTRAVELSCollected at checkout or charged to agent credit |
| Records | Apollo terminal onlyBooking history kept in the GDS | PHPTRAVELSBookings, invoices and refunds also stored in your own database |
| Changes | Apollo terminal onlyNew workflows mean retraining agents | PHPTRAVELSTested in pre-production and released in stages |
| Ownership | Apollo terminal onlyTerminal access under your Travelport agreement | PHPTRAVELSFull source code under a commercial licence, self-hosted |
Use cases
Who connects Apollo with PHPTRAVELS
Agencies moving online
Agencies that book Apollo in a terminal and want a website and agent portal on the same content.
Consolidators and host agencies
Sub-agents book Apollo fares with their own markups, credit limits and branches.
Corporate travel teams
Apollo flights with traveller profiles and reporting for company travel.
Why PHPTRAVELS
Your platform, your Travelport agreement
Source code included
Self-hosted under a commercial licence, so your developers can extend the integration.
Your own credentials
Bookings run on your Apollo PCC and Travelport agreement, not a shared account.
Separate environments
Pre-production and production kept apart, so changes are tested before agents see them.
24 languages
Sell Apollo content in your markets’ languages and currencies, including right-to-left.
FAQ
Apollo software questions
What agencies and technical teams ask before connecting Apollo.
Talk to salesApollo is a global distribution system owned by Travelport, used by travel agencies to search, book and ticket flights; its host code is 1V. Apollo software usually means the tools agencies use to work with it, from the terminal to an online booking engine connected through the Travelport API. It is sometimes spelt appollo.
Both are Travelport systems, but each runs with its own PCCs and setup. Travelport confirms which one your agency is provisioned on, and the PHPTRAVELS flights module can work with either through the Travelport API.
Yes. Access, pricing and credentials for Apollo come from your agreement with Travelport. We help you plan the scope, environments and certification around it.
Each change is tested in pre-production with sample itineraries, signed off by your team and released in stages, with logs to watch and the previous configuration kept ready if you need to roll back.
It depends on the verticals, servicing needs and certification steps. A lean first release goes live sooner when credentials, test cases and business rules are agreed early.
Yes. Sub-agents book with their own markups, commissions and credit limits, and PNR servicing stays in the same admin.
Keep exploring