Getting started
To get started with Sabre APIs, refer to our Quick Start Guide.
The Sabre Offer and Order APIs are implemented as RESTful JSON services. To gain access to these services, you must request an access token using valid Sabre credentials. Submit a request through your Sabre Account Manager to obtain your credentials.
There are two types of tokens: ATK (stateless) and ATH (stateful).
Important! If your application requires work with an open session or if it works in different points of sale or uses multiple Pseudo City Codes, it may be more efficient to use an ATH token as it supports the “Change of Context” capability. If your application does not meet any of these conditions, then an ATK token may be used.
Depending on your needs, proceed with one of the following services:
- Request an ATK stateless token using the OAuth Token Create REST API.
- Request an ATH stateful (session-based) token using the Create Session API.
In addition to an access token, some APIs also require an Application Identifier. This identifier can be obtained from your Sabre Account Manager and its usage is described in a separate Customer Application IDs guide on Dev Studio.
The following APIs require an Application ID to perform respective operations:
- Get Seats API (/offers/getSeats) – to display the seat map with pricing. If an Application ID is not included, you will only receive informational offers.
- Order Management API (/orders/change) – to book a pre-reserved seat.
- Order Management API (/orders/change) – to cancel or modify a pre-reserved seat.
Sabre Offer and Order APIs User Guide
The Sabre Offer and Order APIs expose NDC content in a consistent manner irrespective of the NDC schema version being used by the airline or the NDC technology partner providing the NDC solution to the airline. Some nuances do exist between the airline implementations, these are highlighted in the below document.
This user guide provides descriptions of the APIs along with examples of requests and explanations of responses from various airlines. These examples are presented in a logical flow to assist developers as you expand capabilities within your applications. Most servicing functions are optional and apply to specific use cases and in some circumstances may be applied in any order, for example a seat assignment may be added before or after payment and fulfilment has occurred, but a re-shop and ticket exchange may only occur after fulfillment.
Sabre Offer and Order APIs User Guide
Need help?
We are happy to assist with any questions you may have about these APIs. Visit our Stack Overflow channel, or contact us directly.