Optimize workflows

Learn how you can optimize your workflow to reduce the number of calls to the Sabre APIs production system.

Topics

What are scan charges and limits

A scan charge is any call to the Sabre APIs production system that incurs a fee. A scan limit is the number of scans a customer is allowed to make to the Sabre APIs production system.

See also: the Sabre APIs: environments page for the production system URIs.

Who to contact about scan charges and limits

Scan charges and scan limits vary by customer and the REST or SOAP API you wish to call. Contact your Sabre account manager for details.

How to optimize your workflow to reduce the number of calls

Step 1 – use orchestrated APIs.

Orchestrated APIs are constructed to allow you to make the fewest amount of calls to the Sabre production system (a.k.a. scan charges), and as a consequence reduce the number of scan charges you would incur.

Step 2 – cache your responses.

You may consider caching responses whenever it makes sense to do so. Scan limitations may apply. NOTE you must also consider the length of time for which data is valid.

Step 3 – reuse the same session token.

Opening and closing a session token each time you call the Sabre server will incur additional costs. We recommend you create an in-house token management solution to reuse the same session token for multiple requests and keep it refreshed. And if at all possible, use a sessionless token.

Step 4 – subscribe to travel event notifications.

Event Notification Services is a subscription service (for Travel Network customers) which returns real-time notifications of changes to a passenger name record. Subscribe to travel event notifications (such as airline schedule change notices) to reduce calls to Sabre APIs.


Stack Overflow

Ask a question with the Stack Overflow community.
Ask Questions