Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / E Commerce / Sabre Travel API
Sabre Travel API logo

Sabre Travel API

78
AI ReadinessAI-Ready (A-)78/100
See full scorecard
Official vendor OpenAPI document · agent-readyE CommerceOrder Managementoauth239 EndpointsREST

For Agents

Shop flights and NDC offers, create and cancel PNRs and orders, issue or void tickets, search and book hotels, and look up airports, airlines, and cities through the Sabre GDS.

Use for: Find the cheapest flights from JFK to LHR next month, I need to book a flight and create a PNR for two passengers, Get the seat map for my selected flight, Cancel booking ABC123

Not supported: Does not process card payments, track live flight status, or manage loyalty accounts. Use for shopping, booking, ticketing, and cancelling air, hotel, and car travel on the Sabre GDS only.

The Sabre Travel API reaches Sabre's Global Distribution System (GDS) to shop, book, ticket, and cancel travel. Air shopping covers Bargain Finder Max flight offers, lowest fares, alternate dates, NDC offers, revalidation, and seat maps, while bookings are made as passenger name records (PNRs), enhanced trip orders, or NDC orders and can be ticketed or voided. Hotel search, availability, rates, booking, and cancellation sit alongside rental car search, and utility lookups return airlines, alliances, aircraft equipment, airports, cities, countries, and currencies.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Sabre Travel API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sabre Travel API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsabre.com%2Fsabre" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsabre.com%2Fsabre" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Sabre Travel API.

Search flight offers with Bargain Finder Max using an OTA_AirLowFareSearchRQ request, plus alternate-date and lowest-fare searches

Shop NDC air offers and turn one into an order with POST /v4/orders/create

Create a passenger name record, retrieve it by recordLocator, and cancel it

Issue an air ticket for a booking and void it when plans change

Revalidate an itinerary's price and pull its seat map before booking

Search hotels, check availability and rates, book a room, and cancel the reservation

Look up airports, cities, multi-airport cities, airlines, alliances, and aircraft equipment codes

Use Cases

Patterns agents use Sabre Travel API for, with concrete tasks.

★ Travel booking agent through Jentic

A travel startup wants an assistant that finds and books flights for its users. Through Jentic the agent searches for 'search flight offers', receives the Sabre operation with its input schema, and calls POST /v2/shop/flights with an OTA_AirLowFareSearchRQ. It revalidates the chosen itinerary with POST /v3/shop/flights/revalidate, creates the booking with POST /v2/passenger/records, and returns the record locator to the user.

Call POST /v2/shop/flights for JFK to LHR on 2026-12-10, revalidate the cheapest itinerary with POST /v3/shop/flights/revalidate, then call POST /v2/passenger/records to create the PNR and report the recordLocator

Fare discovery and flexible dates

Price-sensitive travellers want options, not one quote. GET /v1/shop/flights/cheapest/fares/{destination} returns the cheapest fares to a destination with origin, departuredate, and returndate, POST /v1/shop/altdates/flights searches across alternate dates, and GET /v1/lists/supported/shop/flights/destinations lists destinations supported from an origin.

Call GET /v1/shop/flights/cheapest/fares/LHR with origin 'JFK', departuredate '2026-12-10', and returndate '2026-12-17', then compare with POST /v1/shop/altdates/flights for nearby dates

Ticketing and post-booking changes

After a booking is confirmed it must be ticketed, and sometimes undone. POST /v1/air/ticket issues the ticket from an AirTicketRQ, POST /v1/air/ticket/void voids it, and POST /v2/passenger/records/{recordLocator}/cancel cancels the PNR. NDC orders follow their own path with GET /v4/orders/{orderId} and POST /v4/orders/{orderId}/cancel.

Call GET /v2/passenger/records/ABC123 to confirm the itinerary, then call POST /v1/air/ticket to issue the ticket and report the result

Hotel and car add-ons

Trips rarely end at the flight. POST /v2/shop/hotels searches hotels from a GetHotelAvailRQ, POST /v2/shop/hotels/rates and POST /v2/shop/hotels/content give rate details and descriptions, POST /v2/hotel/book books the room, and POST /v2/hotel/cancel cancels it. POST /v2/shop/cars searches rental cars for the same trip.

Call POST /v2/shop/hotels for Paris from 2026-12-10 to 2026-12-13, read rates for the top result with POST /v2/shop/hotels/rates, and book it with POST /v2/hotel/book

Key Endpoints

39 endpoints — the sabre travel api reaches sabre's global distribution system (gds) to shop, book, ticket, and cancel travel.

METHOD

PATH

DESCRIPTION

POST

/v2/shop/flights

Search flight offers (Bargain Finder Max)

POST

/v3/shop/flights/revalidate

Revalidate an itinerary

POST

/v2/passenger/records

Create a PNR

GET

/v2/passenger/records/{recordLocator}

Retrieve a PNR

POST

/v1/air/ticket

Issue an air ticket

POST

/v4/offers/shop

Shop NDC air offers

POST

/v2/shop/hotels

Search for hotels

POST

/v2/hotel/book

Book a hotel

POST

/v2/shop/flights

Search flight offers (Bargain Finder Max)

POST

/v3/shop/flights/revalidate

Revalidate an itinerary

POST

/v2/passenger/records

Create a PNR

GET

/v2/passenger/records/{recordLocator}

Retrieve a PNR

POST

/v1/air/ticket

Issue an air ticket

POST

/v4/offers/shop

Shop NDC air offers

POST

/v2/shop/hotels

Search for hotels

POST

/v2/hotel/book

Book a hotel

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

S

Sabre Travel API

- AI-Ready (A-)
78/100
74
Foundational Compliance
64
Developer Experience & Jentic Compatibility
77
AI-Readiness & Agent Experience
94
Agent Usability
85
Security
78
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
74

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

0%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

64

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4
7%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

77

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: A-Signals: 4
58%

Description Coverage

Coverage of descriptions across API elements.

100%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

85

Security

Trust, risk posture, and security compliance.

Grade: ASignals: 1
85%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

78

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
78%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Sabre by hand means running the OAuth2 client credentials exchange at POST /v2/auth/token, refreshing the token, and building large OTA-style request bodies for shopping, booking, and ticketing. Through Jentic you install once, import Sabre from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Sabre puts the record locator and NDC order id in the URL path (/v2/passenger/records/{recordLocator}, /v4/orders/{orderId}), so a rule can pin your agent to one booking, while shopping and ticketing carry their targets in the body and are bounded by operation. You choose the operations it may call, so ticket issuing, voiding, and cancellations are not included unless you add them.

Credential isolation

Your Sabre client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'search flight offers' or 'issue an air ticket', and Jentic returns the matching Sabre operation with its input schema so the agent calls the right endpoint without reading Dev Studio.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Duffel

→

Flight search and booking with NDC airline content

Choose Duffel for a developer-first flight booking API without a GDS contract; choose Sabre for GDS content, PNRs, and ticketing

Alternative

Flight Create Orders

→

Amadeus flight booking from priced offers

Choose Amadeus when the agency works on the Amadeus GDS; choose Sabre for Sabre-hosted bookings

Alternative

Kiwi Tequila API

→

Flight search with virtual interlining across carriers

Choose Kiwi for low-cost and combined itineraries; choose Sabre for full-service GDS fares and ticketing

Complementary

Aviationstack API

→

Real-time flight status and aviation data

Use Aviationstack to track flight status after booking through Sabre

FAQs

Specific to using Sabre Travel API through Jentic.

What authentication does the Sabre Travel API use?

The Sabre Travel API declares an oauth2 scheme with a client credentials flow in its OpenAPI spec. POST /v2/auth/token takes grant_type client_credentials, needs no prior token, and returns an access token, which the other operations send as a bearer token. Through Jentic the client credentials are held by your own Jentic One instance and the token is attached at call time.

Can I issue and void tickets with the Sabre Travel API?

Yes. POST /v1/air/ticket issues an air ticket from an AirTicketRQ request, and POST /v1/air/ticket/void voids a ticket. To cancel the booking itself, use POST /v2/passenger/records/{recordLocator}/cancel for a PNR, POST /v1/trip/orders/cancelBooking for a trip order, or POST /v4/orders/{orderId}/cancel for an NDC order.

What are the rate limits for the Sabre Travel API?

The OpenAPI spec does not specify rate limits. Check Sabre Dev Studio at https://developer.sabre.com/ for the limits on your account and environment.

How do I search flights through Jentic?

Search Jentic for 'search flight offers', load POST /v2/shop/flights, and execute it with an OTA_AirLowFareSearchRQ body giving origin, destination, dates, and travellers. For a quick price check, GET /v1/shop/flights/cheapest/fares/{destination} takes origin and dates as query parameters. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Sabre MCP server?

You don't need an MCP server to give your agent Sabre. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent finds the shopping, booking, and ticketing operations it needs on demand, without loading extra tool definitions into its context.

Can I limit what my agent is allowed to do with the Sabre Travel API?

Yes. For a fare-research assistant, write a rule that allows POST /v2/shop/flights, POST /v1/shop/altdates/flights, and GET /v1/shop/flights/cheapest/fares/{destination}. The agent can shop and compare fares but cannot create PNRs, issue tickets, or cancel bookings, and each call it makes is logged.

GET STARTED

Start building with Sabre Travel API

Explore with Jentic One
View OpenAPI Document