Skip to main content

Fare Range

v1
Air
Intelligence
REST API
Try now

What is it?

In detail: in the request, future departure dates can range from 0–90 days, from the day of the API request. Length of stay is any single value from 0–16 days. The API also returns a rating of high, medium, or low, which represents the quantity of tickets that the API referenced to obtain the published fare values.

The Fare Range API provides information about prices for ticketed published fares within a specific time frame and is not a shopping or booking solution. You can use the response with other tools of your choice to create your own solutions. For example:

  • Online travel agencies can promote a special price for a fare by comparing what others paid, or by stating that their fares are a specific percentage less than fares that others paid.
  • Online travel agencies can encourage consumers to purchase a fare now, with a note that some consumers paid more for the same fare.

How it works?

Published fares and count in the response

The median, highest, and lowest published fares represent ticketed fares from points of sale in every country in which they were ticketed via the Sabre GDS during the previous 4 weeks.

  • MaximumFare–the highest published ticketed fare
  • MinimumFare–the lowest published ticketed fare
  • MedianFare–the median published ticketed fare
  • Count–the rating for the count of ticketed fares that the API used to compute the median, highest, and lowest published fares (based on the range of ticketed fare counts)

If the available data for ticketed published fares is sparse, it is possible for the API to return fares that are all the same.

Ratings for the ticket counts

The ratings for the quantity of tickets that the Fare Range API referenced to obtain the fares are based on the following:

  • low–less than 1000 ticketed fares
  • medium–1000–10,000 ticketed fares
  • high–more than 10,000 ticketed fares

Buckets used to calculate ticketed fares

The calculations for the ticketed fares are based on buckets of advance purchase days and lengths of stay instead of an individual advance purchase window and length of stay. Each calculation uses the buckets that match the data in the request.

Advance purchase bucket in days

  • 0-6
  • 7-13
  • 14-20
  • 21 or more

Length of stay bucket in days

  • 0-3
  • 4-7
  • More than 7

Data used for the Fare Range API

  • Published fares for roundtrip travel in the economy class of service for a single adult. All departure and arrival times of day. All flight types: direct, non-stop, connecting, and flights with stops. Fare must have been ticketed via the Sabre GDS within the 4 weeks before the date of the API request, and must have been ticketed in the country where the origin airport is located. (E.g., if origin airport is located in Germany, fare must have been ticketed in Germany to be included in the data.)
  • All departure and arrival times of day
  • All flight types: direct, nonstop, connecting, and flights with stops
  • Origin: major airports throughout the world that we support.
  • Destination: major airports throughout the world that we support.
  • The ticketed fares are total fares. Total fares include all taxes and fees, however, ancillary fees charged by airlines, such as baggage and preferred seating, are not included.
  • Point of sale: No limitations on locations from which fares are ticketed.

How to use?

Country and airport codes

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 Fare Range API request.

There are multiple endpoints for the City Pairs Lookup API. One endpoint is for city pairs that apply to the Fare Range API. See the City Pairs Lookup API page for the specific HTTP method and endpoint.

InstaFlights Search API

The InstaFlights Search API retrieves roundtrip flight itineraries with published fares and fare breakdowns available from the Sabre® cache for a certain origin, destination, and roundtrip travel dates. The origins and destinations are airport codes.

Low Fare Forecast API

The Low Fare Forecast API forecasts the price range into which the lowest published fare that is available via the Sabre® GDS is predicted to fall within the next 7 days, from a specific origin and destination on specific roundtrip travel dates.

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.

Not every airport code that is associated with a multi-airport city (MAC) is supported by the Fare Range API. Use the City Pairs Lookup API and the endpoint that applies exclusively to the Fare Range API to get a list of supported city pairs.

Example: Within the Fare Range 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.

Resources

Got an error, but unsure what it means? Go to our Errors page.