Advanced features

Sabre ® has introduced new capabilities to help developers deal with large volumes of data, including pagination and personalized responses via configurable views. By making use of these new features, client applications can specify the number of assets (e.g., itinerary options), as well as the individual data elements to be returned. The response is reduced payload sizes, and consequently, faster and more efficient processing on the client-side.

Response Views

Sabre ® response views allow client applications to use preformatted Sabre ® response views that have been modified to include or exclude certain response paths by default. These default views can be used by any Pseudo City Code (PCC).

  • See the Response View Lookup API for a list of Sabre ® response views. Multiple methods and endpoints are available for this suite of APIs.
  • To use a Sabre ® response view, pass the view as a filter in the request URI, e.g., view={view name} to format the response.

Response views can be used with the following APIs: Advanced Calendar Search, Alternate Airport Shop, Alternate Date, Bargain Finder Max, and InstaFlights Search.

Custom Response Views

Custom response views allow client applications to specify individual data elements to be returned within a response payload. A custom response view is a view defined by a single Pseudo City Code (PCC).

  • To create a custom response view, define the response paths to include or exclude using the Custom Response View API. Multiple methods and endpoints are available for this suite of APIs.
  • To use a custom response view, pass the view as a filter in the request URI, e.g., view={view name} to format the response.

Custom response views can be used with the following APIs: Advanced Calendar Search, Alternate Airport Shop, Alternate Date, Bargain Finder Max, and InstaFlights Search.

Pagination Request

Pagination requests allow client applications the ability to request only a subset of assets, rather than the complete API response. This allows client applications to select the information needed at each step of the workflow, cutting down bandwidth required, and improving processing times for each request (versus returning all itineraries, for example).

  • The query parameter enabletagging=true needs to be used in the initial request in order to return a request ID for subsequent pagination requests. This returns and stores Request IDs for subsequent calls to the Sabre ® cache.
  • A RequestID will be included in the response, and can be used in subsequent pagination requests.

The following parameters are supported, for pagination purposes:

  • offset: this offsets the start of each page by the number specified
  • limit: this is the number of individual assets that are returned in each page
  • A limit of 0 will return no results.
  • A limit of none will return all results.

A unique method and endpoint is available for pagination requests. See documentation for details. Pagination requests can be used with the following APIs: Advanced Calendar Search, Alternate Airport Shop, Alternate Date, Bargain Finder Max.

Tagging

Tagging allows client applications to receive a unique identifier (TagID) for each asset in a response. The identifier can be used in a subsequent request, to get all the information behind the associated asset, e.g., to retrieve the detailed itinerary.

  • The query parameter enabletagging=true needs to be used in the initial request in order to return a tag ID for each item.
  • A TagID will be included in the response, and can be used in subsequent requests.

A unique method and endpoint is available for tagging requests. See documentation for details. Pagination requests can be used with the following APIs: Advanced Calendar Search, Alternate Airport Shop, Alternate Date, Bargain Finder Max, and InstaFlights Search.

Docs Navigation