Galileo and Apollo both run on the Travelport platform, and the large majority of their cryptic commands are identical — the split between the two systems today is mostly a matter of which agency network an office was originally set up on, rather than a fundamentally different command language. This page covers the shared command set, with notes wherever a meaningful difference exists.
Checking Availability
A/15JUNDFWORD
The forward slash after the initial A is the detail that trips up agents coming from Amadeus or Sabre, where no slash is used in the equivalent entry. To restrict to one carrier:
A/15JUNDFWORD/AA
Selling a Segment
04Y2
Sells 2 passengers in Y class from line 4 of the availability display — the same numeric logic as Sabre's sell entry, though the underlying system is unrelated. Direct sell without pulling availability first follows a similar pattern to the other GDSs, referencing the flight number, date, and city pair directly.
Building the PNR
| Element | Entry format | Example |
|---|---|---|
| Name | NM1 | NM1SMITH/JOHN MR |
| Phone/contact | P prefix | P DFW 555-1234-A |
| Ticketing arrangement | TAW or TAU | TAW15JUN/1800 |
| Received from | RF | RF SMITH |
The name field format matches Amadeus closely, since both systems use NM as the element identifier — this is one of the reasons agents who trained on Amadeus tend to pick up Galileo/Apollo name-field syntax faster than Sabre's hyphen-prefixed format.
SSR and OSI Entries
SI.P1.VGML
Requests a vegetarian meal for passenger 1. The dot-separated format (SI. for special item, then passenger reference, then the code) is a distinguishing feature of the Travelport syntax compared to the space-separated formats in Amadeus and Sabre.
SI.P1.WCHR
Wheelchair assistance, using the same three-tier code system as other GDSs (WCHR, WCHS, WCHC) depending on the passenger's actual mobility level.
Pricing the Itinerary
| Entry | What it does |
|---|---|
FQ | Displays a fare quote for the itinerary without storing it |
FXP | Prices and stores the itinerary as a fare quote attached to the PNR |
FQR | Displays the fare rules for a currently stored fare quote |
Ticketing Commands
TTP
Issues the ticket against the stored fare quote, following the same principle as Amadeus and Sabre — a valid, current priced itinerary has to exist in the PNR before this will succeed.
Queue Commands
| Entry | What it does |
|---|---|
Q | Displays queue counts for the current office |
QN | Brings up the next PNR on the selected queue |
QE | Places the displayed PNR onto a specified queue |
Void and Refund
TRDN
Voids a same-day ticket before the reporting cutoff, the same concept as the equivalent entries in Amadeus and Sabre. Refunds on already-issued tickets are processed through a separate refund entry and depend on the fare rules attached to the original ticket, particularly whether the fare was refundable and whether a penalty applies.
Display and Retrieval
| Entry | What it does |
|---|---|
*[record locator] | Retrieves a PNR by its record locator |
*SMITH | Retrieves by passenger surname |
Common Error Codes
| Error | What it means |
|---|---|
| SOLD OUT | No inventory left in the requested class — check a different class or flight |
| INVALID FORMAT | The entry syntax doesn't match what the system expects — check dots, slashes, and field order |
| FARE QUOTE EXPIRED | The stored fare quote is stale and needs to be re-priced before ticketing |
Worldspan was a separate GDS with its own classic command syntax, distinct from both Galileo/Apollo and Sabre. Travelport has largely absorbed Worldspan's functionality into its platform, and most agencies that historically used Worldspan have transitioned onto shared Travelport infrastructure. If you're working with a genuinely legacy Worldspan terminal, check with your host agency for the current command reference, since remaining Worldspan-specific setups vary by agency.
Turn Any Galileo or Apollo PNR Into a Client-Ready Itinerary
Paste the raw PNR text and get a clean, branded itinerary in seconds — free, no signup.
Try the Free Converter →