Sabre API Integration
Sell the airlines Sabre distributes through one REST flight API. FlightOTA queries Sabre Bargain Finder Max beside Amadeus, Travelport and direct airline connections, so Sabre fares reach your agents and customers without a Sabre development project of your own.
Sabre fares, served as plain JSON
Sabre's Bargain Finder Max is the low-fare search that many agencies and OTAs rely on for full-service airline coverage. Reaching it directly means Sabre's own APIs, a contract and a certification before you can ticket.
FlightOTA already queries Bargain Finder Max as one of the sources behind POST /flights/search. Sabre offers come back in the same JSON as every other: a total your deposit pays, passenger prices, baggage per segment, fare rules, and a sell price when you have markup rules. When a booking is held in Sabre, its record locator is returned as gds_reference.
Choose the Sabre integration when your agents compare Sabre content against NDC and low-cost fares on one screen, or when a mid-office that already works with Sabre PNRs needs them created through an API.
How a Sabre fare moves through the Flights API
Five calls, the same as every airline source. These steps call out where Sabre shows through for an agent.
- 01
Search once for the agent
A single POST /flights/search shops Bargain Finder Max with the other sources, so an agent sees a Sabre fare beside NDC and low-cost offers in one list. Narrow it with filters.carriers or filters.nonstop.
- 02
Show the terms before booking
Fare rules, baggage and refund terms are read on the offer_id, and with fares set to branded every fare family is its own offer. Nothing is reserved until you book.
- 03
Hold, then issue from the deposit
The booking comes back held with hold_expires_at; issue it from your deposit before then. The Sabre record locator is returned as gds_reference.
- 04
Quote and track after-sales
Void, refund and reissue requests return quotes and a status you can show the agent. Our desk handles what the airline does not answer by itself.
What the Sabre integration covers
Sabre content, booked through the Flights API and paid from your deposit.
- Sabre Bargain Finder Max low-fare search inside the unified search
- gds_reference: the Sabre record locator on bookings held there
- One-way, round-trip and multi-city itineraries, up to six slices
- Fare rules, refund terms and baggage per segment on every offer
- Held bookings issued from your deposit before hold_expires_at
- Void, refund and reissue with quotes and status through the API
- Safe retries with an Idempotency-Key, so a timeout never books twice
- Sandbox bookings on test systems before your live key is switched on
Sabre integration questions
Related integrations and APIs
Bring Sabre content into your agents' search
Book a demo and we will run your routes through the sandbox so you can see Sabre offers, holds and tickets in the API.