Services · GDS, NDC & airline
GDS integration that runs on your own GDS contract
GDS integration is the engineering work of connecting a booking platform to Amadeus, Sabre or Travelport so that shopping, pricing, PNR creation and ticketing happen through code instead of a terminal. Voraal connects your existing GDS credentials to Rezencia and Avunzo, so the fares, office set-up and agreements you already have keep working.
Built for
- IATA-accredited agencies
- Flight consolidators
- OTAs adding a GDS
- Tour operators with air desks
- In-house tech teams
In brief
What is GDS integration?
GDS integration connects a travel platform to a global distribution system such as Amadeus, Sabre or Travelport through the GDS's web-services APIs. The platform can then search availability, price itineraries, create PNRs and issue tickets automatically. Voraal integrates using the agency's own PCC, Office ID or SID credentials, so the commercial agreement with the GDS stays with the agency.
By the Voraal team · Updated
What a GDS integration actually connects
A GDS contract gives an agency a pseudo city code (PCC) on Sabre or Travelport, or an Office ID on Amadeus, plus access to published fares, negotiated fares filed to that office, and the airline inventory the GDS distributes. On its own, that contract is used through a terminal or the GDS's desktop product. GDS integration is what turns it into a programmable connection: the platform authenticates as your office, sends structured requests and receives structured responses it can price, store and display.
The work is more than an HTTP client. Each GDS has its own session model, message set, error vocabulary and rate behaviour. Some flows are stateful (a session holds the itinerary while it is priced and stored), others are stateless. A production integration has to manage sessions safely, retry only what is safe to retry, and keep a full log of what was sent and received, because when a ticket or a fare is disputed, the message log is the evidence.
How a single-GDS integration works, request by request
The core booking path is the same on every GDS, even though message names and structures differ.
- 01
Authenticate as your office
The platform signs in with the credentials tied to your PCC, Office ID or SID. Every request after that is made as your office, so your filed fares and agreements apply.
- 02
Shop availability and fares
A low-fare search returns itineraries with booking classes, fare basis codes and taxes. The response is normalised into Voraal's flight model so it can be priced and compared.
- 03
Re-price the chosen option
Before booking, the itinerary is priced again because seats and fares move. The re-price confirms the fare basis, taxes and any change since the search.
- 04
Create the PNR
Segments are sold, passenger names, contacts and travel documents are added, and the PNR is ended to receive a record locator and a ticketing time limit.
- 05
Store the fare and issue
The priced fare is stored in the PNR and, when payment and rules allow, the ticket is issued. Ticket numbers are written back to the booking in Rezencia.
- 06
Listen for changes
Queue messages and PNR changes posted by airlines are read back so that schedule changes and cancellations reach the booking record.
Key features of Voraal's GDS connection
Your credentials, unchanged
Existing Amadeus, Sabre or Travelport accounts connect as they are. Nothing is migrated or re-registered with the GDS.
Normalised flight model
GDS responses become one internal structure, so the same itinerary looks the same whether it came from one GDS or, later, from three.
Message logging
Requests and responses are stored against the booking for troubleshooting, ADM disputes and audit.
Safe retries
Search calls can be retried; booking and ticketing calls are guarded so a timeout does not create a duplicate PNR or a second ticket.
Queue reading
Airline-posted changes arriving on queues are matched to bookings, feeding schedule-change alerts.
Platform or API
Use it inside Rezencia's booking engine, or consume the same connection through Avunzo's REST/JSON endpoints.
Who provides what in a GDS integration
A common source of confusion is the line between the GDS contract and the integration. This is how it splits.
| Item | Your GDS agreement | Voraal integration |
|---|---|---|
| PCC / Office ID / SID | Issued by the GDS to your business | Used to authenticate every request |
| Negotiated and private fares | Filed by airlines to your office | Returned in search and priced automatically |
| Ticketing authority | Through your IATA accreditation or host arrangement | Issuance triggered by rules you configure |
| Segment and booking fees | Set in your GDS commercial terms | Not changed by the integration |
| Search, book, ticket flows | Not included | Built, maintained and logged |
| Display, markup, agent pricing | Not included | Handled in Rezencia or per API channel in Avunzo |
Voraal does not provide GDS contracts or ticketing authority. Fees and incentives remain between your business and the GDS.
Business applications
An agency moving off the terminal
Staff who quote from cryptic screens get a graphical search and booking flow on the same office, with the integrated GDS terminal still available for edge cases.
An OTA launching flights
A consumer site or app gets GDS content through Avunzo without the team learning a GDS message set.
A consolidator opening a B2B channel
One GDS office feeds every sub-agent portal, with the consolidator's markup on top. See flight consolidator software.
Implementation process
- 01
Confirm the GDS account
We check which GDS, which office codes and which web-services access your contract includes. API access is sometimes a separate request to the GDS.
- 02
Connect in a test environment
Credentials are connected to a non-production environment where searches, PNRs and cancellations can be exercised without issuing real tickets.
- 03
Map your fares and fees
Private fares, corporate codes and your service fees are mapped so priced results match what your staff would quote manually.
- 04
Go live and monitor
The production office is switched on, response times and errors are monitored, and the first live tickets are checked against the GDS record.
Common challenges and how they are handled
Where single-GDS projects go wrong
- Fares in the search differ from the fare at booking because the re-price step was skipped
- A timeout during ticketing leads to a retry and a duplicate ticket
- Private fares do not appear because the wrong office is used
- Queues are never read, so schedule changes are discovered at the airport
How the Voraal integration avoids them
- Every booking path re-prices before the PNR is ended
- Booking and ticketing calls are idempotent and checked against the PNR before any retry
- Searches run on the office that holds your filed fares
- Queue messages are read and matched to bookings continuously
When one GDS is no longer enough
Many agencies start with one GDS and add a second when an airline deal or a fare filed only to another system makes it worthwhile. Because Voraal normalises every GDS response into the same model, adding a second connection is a configuration and testing exercise rather than a rebuild. The routing, de-duplication and fallback that a second GDS requires are covered on our multi-GDS integration page; for a plain comparison of channels, read GDS vs NDC.
How Voraal delivers this
The products behind it.
Do we need API access in our GDS contract, or is terminal access enough?
Programmatic access is usually a separate entitlement from terminal access. During onboarding we confirm with you what your contract includes and, if needed, what to request from your GDS account manager.
Will our negotiated fares appear through the integration?
Yes, provided searches run on the office the airline filed them to. We configure the integration to use that office, so private and corporate fares are returned and priced like any other fare.
Can we keep using the GDS terminal after integration?
Yes. The connection does not replace terminal use. Rezencia also includes a GDS terminal inside the admin, governed by your own GDS agreement.
Does Voraal change our GDS segment fees or incentives?
No. Segment fees, productivity incentives and any other commercial terms stay between your business and the GDS. The integration only uses your access.
Which GDS should a new agency integrate first?
It depends on which airlines you sell most, which system holds the fares you have negotiated, and your local support. We discuss that with you rather than recommending a GDS by default.
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.