Sabre API
An extensive developer program at developer.sabre.com spans parallel SOAP/XML and REST/JSON stacks with OAuth 2.0 and NDC endpoints. Production access is contract-bound: PCC provisioning, mandatory certification, and an agreement amendment for each new API or region.
Frequently asked questions
Sabre scores F on Supergood's API Report Card. An extensive developer program at developer.sabre.com spans parallel SOAP/XML and REST/JSON stacks with OAuth 2.0 and NDC endpoints. Production access is contract-bound: PCC provisioning, mandatory certification, and an agreement amendment for each new API or region.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Sabre Corporation (NASDAQ: SABR), headquartered in Southlake, Texas, is one of the three legacy Global Distribution Systems (GDS) that intermediate the world's travel inventory between suppliers (airlines, hotels, car rental, rail, cruise) and the travel-seller channel (OTAs, TMCs, consolidators, corporate booking tools, leisure agencies).
Vertical: misc, Travel & Expense / Global Distribution System / Airline IT / Travel Retailing (no native Supergood vertical maps perfectly; closest neighbors are Travel & Expense and POS/Hospitality). Air shopping (low-fare search across GDS, NDC and LCC content via Bargain Finder Max, the single most-called Sabre API). Air pricing (fare confirmation, fare rules, ancillary pricing, branded fare attributes).
9/10 within travel. Sabre is the #2 GDS globally with roughly 30-35% of global GDS air-transaction share, behind Amadeus (~40%) and ahead of Travelport (~20-22%).
Yes, for every Sabre customer, Sabre is the system of record for mission-critical operating data: PNRs (Passenger Name Records): record locator, traveler profile (name, contact, frequent-flyer numbers, special service requests), segments (air, hotel, car, rail), form of payment, fare, ticket numbers, queue placement, full PNR history.
Sabre is one of the oldest production systems in commercial computing: the original Sabre (Semi-Automated Business Research Environment) was launched by American Airlines and IBM in 1960, making it 65+ years old in its underlying lineage.
SOAP/XML payload size and parsing overhead, OpenTravel Alliance messages are large, namespace-heavy XML; encoding/decoding burden is a perennial complaint vs. modern JSON APIs. Developers commonly misuse token refreshes, skip session closures, mix CERT and PROD credentials, or overload APIs with redundant requests, leading to failed bookings, API throttling, or 'Sabre penalties'. Full sourced list under Sources below.
Common alternatives include Amadeus, Travelport, Duffel, Kyte, Verteil Technologies, Direct NDC (American, United, Delta, Lufthansa Group, IAG, Air France-KLM, Qantas, Singapore). Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Sabre has partial MCP support. Sabre advertises an official MCP server as part of its SabreMosaic platform, but it is enterprise-only with no public registry listing or public install docs. A community server, sabre-blade-mcp, exposes flight, hotel, and PNR tools against Sabre APIs.
Partially. MCP support for Sabre exists but is incomplete, so what MCP clients like Claude, Cursor, and Codex can reach depends on what the available server covers.