What is it?
In detail: the API uses the Travel Insight engine to retrieve shopped fare data for a given city pair/departure date available in the Sabre® cache. When you include required parameters only, each request returns a nonstop lead fare and an overall lead fare for each of the next 192 consecutive days from the API request.
Note: This API requires activation and Sabre Dev Studio/Travel Insight Engine Amendment to be signed. Please contact your Sabre Account Representative for assistance.
Why use it?
You could use this API to create a graphical user interface to chart up to 192 days of the lowest published fares for a popular European destination or international city pair, such as "LAX" (Los Angeles International) to "LHR" (London Heathrow). This can then be combined with multiple length of stay functionality. From this chart, leisure travelers with flexible travel dates and longer advance purchase windows can compare flight prices up to 192 days from a specified departure date.
How it works
Data used by Lead Price Calendar API
- The in-scope shopping responses used by Sabre to generate the lead fares for this API are the shopping responses to shopping requests from a PCC (a Pseudo City Code) operated by Sabre.
- All fares are for single adult, who is traveling one-way or roundtrip in the economy class of service.
- Total fares: All taxes and fees are included; however, ancillary fees charged by airlines, such as baggage and preferred seating, are not included.
- Flight types: nonstop, connecting, and flights with stops
- Origin: major airports and multi-airport cities throughout the world that we support
- Destination: major airports throughout the world that we support
- Advance fares: A maximum of 192 days
How to use
Country and airport codes
- For ISO 3166 country codes, see ISO 3166.
- For IATA airport codes, see IATA's Airline and Airport Code Search.
Point of sale
The point of sale is the geographic location in which the fare itinerary is eligible to be ticketed. The default point of sale (US) can be overridden with any supported point of sale country specified in the pointofsalecountry parameter. For example, the following will retrieve fare data specific to the Germany (DE) point of sale:
pointofsalecountry=DE. The response will be fares eligible for sale in Germany.
Airports at Cities Lookup API
To identify the airports associated with a multi-airport city (MAC) code, use the Airports at Cities Lookup API and pass one of the MACs in the request. The Airports at Cities Lookup API retrieves our list of major airport, rail station and other codes that are associated with a single multi-airport city (MAC) code in the request.
City Pairs Lookup API
To get a list of our supported city pairs of origin and destination airports, use the City Pairs Lookup API. You can pass any of these origin and destination airport codes in a Lead Price Calendar API request.
InstaFlights Search API
The InstaFlights Search API retrieves one-way/roundtrip flight itineraries with published fares and fare breakdowns available from the Sabre® cache for a certain origin, destination, and one-way/roundtrip travel dates. The origins and destinations are airport codes.
Multi-Airport City Lookup API
To get a list of city codes that are served by more than one airport, use the Multi-Airport City Lookup API. These multi-airport codes can be used with applicable REST APIs.
Example: Within the Lead Price Calendar API, to search for the lead fares from DFW to any airport associated with New York City, use "DFW" for origin and "NYC" for destination. The response will include the lowest fare and lowest nonstop fare. The lowest fare will be from DFW to any one of the airports that belong to NYC, e.g., DFW to LGA. The lowest nonstop fare will be from DFW to any one of the airports that belong to NYC, but may not be the same airport associated with the lowest fare, e.g., DFW to JFK.
Got an error, but unsure what it means? Go to our Errors page.