GDS API Integration
Connect your agency, OTA or booking engine to Amadeus, Sabre and Travelport content through one REST flight API. One search shops every source at once, bookings are ticketed from your deposit, and voids, refunds and reissues run through the same calls, without a GDS contract or terminal integration of your own.
Global distribution system content without the terminal
A global distribution system (GDS) is where most full-service airlines still file their fares and where agencies have booked them for decades, through terminals and XML contracts that each take months to integrate. FlightOTA already holds those connections. Our flight distribution core queries Amadeus MasterPricer, Sabre Bargain Finder Max and Travelport Galileo, and returns their offers in the same JSON shape as every other airline source we carry.
For you that means one integration instead of three. You search with POST /flights/search, read offers that carry fare rules, baggage and fare families, and book with the same calls whether the fare came from a GDS, an NDC direct connect or a low-cost carrier. A booking held in a GDS reports its record locator there as gds_reference, so your back office can still find it in the GDS when it needs to.
GDS integration suits consolidators and agencies that need the breadth of full-service airline content, corporate programmes with negotiated fares, and OTAs that want GDS inventory beside direct connects without running two booking flows.
From a search to a ticketed GDS booking
The flight booking flow is the same for every source. These are the points where the GDS shows through.
- 01
Search every source at once
One POST /flights/search shops Amadeus, Sabre and Travelport beside our direct airline connections and answers in 5 to 30 seconds. Ask for branded fares and each fare family comes back as its own offer.
- 02
Price and read the rules
Re-price the chosen offer with the airline, then read its fare rules, baggage and the passenger details it needs. Offers stay bookable for 15 minutes.
- 03
Hold, then issue from your deposit
Booking a GDS fare creates a held booking with a hold_expires_at. Issue it before then and the tickets are paid from your FlightOTA deposit; the booking carries both our reference and the gds_reference.
- 04
Service it through the API
Void, refund and reissue requests go through the same booking. Where the airline does not answer by itself, our desk handles the request and quotes by hand.
What the GDS integration covers
Everything below is part of the Flights API; nothing needs a GDS login on your side.
- Low-fare search across Amadeus, Sabre and Travelport in one request
- One-way, round-trip and multi-city itineraries with up to six slices
- Standard fares or every branded fare family, each as its own offer
- Fare rules, baggage allowances and refund terms on every offer
- Held bookings issued from your deposit before hold_expires_at
- gds_reference on every booking held in a GDS, beside our own reference
- Void, refund and reissue requests on ticketed bookings
- Seats, bags and meals where the airline sells them
- Your selling price returned next to your cost when markup rules are set
GDS integration questions
Related integrations and APIs
Add Amadeus, Sabre and Travelport content to your platform
Tell us which products and airlines your business sells and we will walk you through the GDS integration on the sandbox.