Low Fare History

Heads Up! - This API is powered by the Travel Insight Engine. Check the City Pairs Supplemental API to see the city pairs that are currently supported.

The Low Fare History API returns each day of the past two weeks' lowest published fares for a given city/date pair.

In detail: the API uses the Travel Insight Engine to retrieve shopped fare data for a given city pair/date pair combination available in the Sabre® cache. In total, each request yields 15 shop dates and two fares per shop date: a nonstop lead fare and an overall lead fare. For the day of the request, which is always "today," it returns the then current nonstop lead fare and overall lead fare. Then, for each of the last 14 consecutive days from this shop date, it yields the lowest nonstop lead fare and overall lead fare available at any point during that day.

Examples

Chart daily historical flight price trends

You could use this API to create a graphical user interface to chart 2 weeks of daily historical flight price trends for a popular domestic city pair, such as "SFO" (San Francisco International) to "SEA" (Seattle-Tacoma International). From this chart, customers can see what the lead fare was every day of the past two weeks. If the fare has been trending up, it may give them an incentive to buy.

List top 10 trending beach destinations

You could use this API to compile a list of "top 10" trending beach destinations with the greatest drop in airfare, such as "MIA" (Miami International) to "OGG" (Kahului Airport, Hawaii). From this list, customers can see what the lead fare was for each city pair every day of the past two weeks. If the fare has increased by 10% over the past 2 days, it may give them an incentive to buy now before prices continue to increase.

See usage notes: for more information on retrieving a list of themes using the Travel Theme Lookup API or to retrieve airport codes associated with a theme using the Theme Airport Lookup API.

Data used by the Low Fare History API

  • Data is refreshed on a regular basis using pre-configured points of sale for pre-configured sets of city pairs, pre-configured advance purchase windows, and pre-configured lengths of stay, all as determined by Sabre in its discretion.
  • In addition to the pre-configured data determined by Sabre, this Travel Insight Engine API is supplemented with an enriched subset of organic shopped fare data (subject to change).
  • All fares are for single adult, roundtrip travel 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 throughout the world that we support
  • Destination: major airports throughout the world that we support
  • Advance fares: a maximum of 192 days

HTTP method and endpoint

GET /v1/historical/shop/flights/fares

Request

origin

string, required

3-letter IATA code of the origin airport or multi-airport city (MAC) code

Only one value is accepted

Sample value: origin=ATL

If a multi-airport city (MAC) code is used, then only the lowest fare associated with any of the airports belonging to the MAC will be returned.

See usage notes: for more information on retrieving a list of our supported city pairs of origin and destination airports using the City Pairs Lookup API, multi-airport city (MAC) codes using the Multi-Airport City Lookup API, or to identify the airports associated with a MAC using the Airports at Cities Lookup API.

destination

string, required

3-letter IATA code of the destination airport or multi-airport city (MAC) code

Only one value is accepted

Sample value: destination=LAS

If a multi-airport city (MAC) code is used, then only the lowest fare associated with any of the airports belonging to the MAC will be returned.

See usage notes: for more information on retrieving a list of our supported city pairs of origin and destination airports using the City Pairs Lookup API, multi-airport city (MAC) codes using the Multi-Airport City Lookup API, or to identify the airports associated with a MAC using the Airports at Cities Lookup API.

departuredate

string, required

Date of departing flight in the time zone of the origin airport

Only one value is accepted

Sample value: departuredate=2015-10-30

Maximum value: current date + 192 (days)

returndate

string, required

Date of returning flight in the time zone of the destination airport

Only one value is accepted

Sample value: returndate=2015-10-31

Maximum value: departuredate + 16 (days) length of stay

pointofsalecountry

string, optional

2-letter ISO 3166 country code

Retrieves data specific to a given point of sale country

Only one value is accepted

Default value: US

Sample value: pointofsalecountry=DE

See usage notes: for more information on point of sale and supported point of sale countries.

Response

The response is organized by shop date in descending rank order, starting with the day of the request, which is always "today."

OriginLocation

string

Returns the specified 3-letter IATA origin airport or multi-airport city (MAC) code

DestinationLocation

string

Returns the specified 3-letter IATA destination airport or multi-airport city (MAC) code

DepartureDateTime

string

Returns the specified departure date in the time zone of the origin airport

Data format: YYYY-MM-DDTHH:MM:SS

Note: time zones are specific to departure and arrival airports.

ReturnDateTime

string

Returns the specified return date in the time zone of the destination airport

Data format: YYYY-MM-DDTHH:MM:SS

Note: time zones are specific to departure and arrival airports.

FareInfo

array

Returns fifteen (15) shop dates (ShopDateTime) and 2 fares per shop date (LowestFare and LowestNonstopFare)

Repeats associated lead fare and date/time information:

  • LowestFare, string or number
  • LowestNonstopFare, string or number
  • CurrencyCode, string
  • ShopDateTime, string
FareInfo.LowestFare

string or number

The overall lead fares for the specified city pair/date pair combination

For the day of the request, always "today": the then current overall lead fare from the Sabre cache is returned.

For each of the last 14 consecutive days from the day of the request: the API yields the lowest overall lead fare at any point during that day.

If shopped fare data is found for overall lead fare, then the API returns a number.

If no shopped fare data is found, then the API returns a string (N/A).

FareInfo.LowestNonstopFare

string or number

The nonstop lead fares for the specified city pair/date pair combination

For the day of the request, always "today": the then current nonstop lead fare from the Sabre cache is returned.

For each of the last 14 consecutive days from the day of the request: the API yields the lowest nonstop lead fare at any point during that day.

If shopped fare data is found for overall lead fare, then the API returns a number.

If no shopped fare data is found, then the API returns a string (N/A).

FareInfo.CurrencyCode

string

3-letter currency code

If no lead fares are found, then the API returns a string (N/A).

FareInfo.ShopDateTime

string

The shop date when the respective shopped fare was available

Format: YYYY-MM-DDTHH:MM:SS

Overall response links

Link nodes

array

See usage notes: for more information on link nodes.

shop

object

Invokes InstaFlights Search API request for flight itineraries and pricing

If a multi-airport city (MAC) code is used as origin, then the shop link will contain the MAC.

See usage notes: for more information on the InstaFlights Search API.

self

object

Returns the URL of the request that generated the response

linkTemplate

object

Formats a Low Fare History request with placeholders for every request parameter

Examples: request and response

This example demonstrates a request for the past two weeks' lowest published fares from "DFW" (Dallas/Fort Worth International) to "ORL" (Orlando Executive) as of "today." In this case, the past two weeks from today, June 1, 2015, the day the request was executed.

GET https://api.sabre.com/v1/historical/shop/flights/fares?origin=DFW&destination=ORL&departuredate=2015-08-23&returndate=2015-08-30&pointofsalecountry=US HTTP/1.1
{
    "OriginLocation": "DFW",
    "DestinationLocation": "ORL",
    "DepartureDateTime": "2015-08-23T00:00:00",
    "ReturnDateTime": "2015-08-30T00:00:00",
    "FareInfo": [{
        "ShopDateTime": "2015-06-01T00:00:00",
        "LowestFare": 206.2,
        "LowestNonStopFare": 206.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-31T00:00:00",
        "LowestFare": 206.2,
        "LowestNonStopFare": 206.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-30T00:00:00",
        "LowestFare": 206.2,
        "LowestNonStopFare": 206.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-29T00:00:00",
        "LowestFare": 206.2,
        "LowestNonStopFare": 206.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-28T00:00:00",
        "LowestFare": 206.2,
        "LowestNonStopFare": 206.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-27T00:00:00",
        "LowestFare": 206.2,
        "LowestNonStopFare": 206.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-26T00:00:00",
        "LowestFare": 206.2,
        "LowestNonStopFare": 206.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-25T00:00:00",
        "LowestFare": 206.2,
        "LowestNonStopFare": 206.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-24T00:00:00",
        "LowestFare": 206.2,
        "LowestNonStopFare": 206.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-23T00:00:00",
        "LowestFare": 206.2,
        "LowestNonStopFare": 206.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-22T00:00:00",
        "LowestFare": 199.7,
        "LowestNonStopFare": 206.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-21T00:00:00",
        "LowestFare": 193.2,
        "LowestNonStopFare": 206.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-20T00:00:00",
        "LowestFare": 193.2,
        "LowestNonStopFare": 206.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-19T00:00:00",
        "LowestFare": 176.2,
        "LowestNonStopFare": 176.2,
        "CurrencyCode": "USD"
    }, {
        "ShopDateTime": "2015-05-18T00:00:00",
        "LowestFare": 176.2,
        "LowestNonStopFare": 176.2,
        "CurrencyCode": "USD"
    }],
    "Links": [{
        "rel": "shop",
        "href": "https://api.sabre.com/v1/shop/flights?origin=DFW&destination=ORL&departuredate=2015-08-23&returndate=2015-08-30&pointofsalecountry=US"
    }, {
        "rel": "self",
        "href": "https://api.sabre.com/v1/historical/shop/flights/fares?origin=DFW&destination=ORL&departuredate=2015-08-23&returndate=2015-08-30&pointofsalecountry=US"
    }, {
        "rel": "linkTemplate",
        "href": "https://api.sabre.com/v1/historical/shop/flights/fares?origin=<origin>&destination=<destination>&departuredate=<departuredate>&returndate=<returndate>&pointofsalecountry=<pointofsalecountry>"
    }]
}

Usage notes

Country and airport codes

Links nodes

  • Sabre® REST APIs have one or more links nodes that combine related URI resources in a response. For more information, see the links nodes page.

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.

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 request.

There are multiple endpoints for the City Pairs Lookup API. One endpoint is for city pairs that apply to the Low Fare Forecast 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.

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 city codes can be used with applicable REST APIs.

Theme Airport Lookup API

To get a list of destination airport codes that are associated with the optional theme parameter, use the Theme Airport Lookup API. The response will be a list of valid themes that we associate with that destination, e.g., Las Vegas would be associated as a GAMBLING  destination.

Travel Theme Lookup API

To get a list of valid themes, use the Travel Theme Lookup API. The response will be a list of themes, such as BEACH, GAMBLING .

Errors

A general HTTP status code is always returned.

Errors that are specific to this API follow. For information about the error response format, see the: status codes and errors page.

Note — Optional parameters are checked for errors when a value is supplied.

404 NOT_FOUND

No results were found

The service cannot find data to fulfill the parameters in the request. For example, data is not available for the origin or dates.

An origin or destination in the request is not a valid IATA airport code.

The origin or destination are not supported.

Status 413 FULL head

The API returns this error when a request URI is too long. For example, the HTTP request’s query string exceeds the server limit.

The response will be empty as a result.

Please consider reducing the number of request parameters in the URI or separating parameters into multiple HTTP requests.

Status 400 BAD REQUEST

Parameter 'origin' must be specified

origin is missing.

origin is missing a value.

Parameter 'destination' must be specified

destination is missing.

destination is missing a value.

Parameter 'departuredate' must be specified

departuredate is missing.

departuredate is missing a value.

Parameter 'returndate' must be specified

returndate is missing.

returndate is missing a value.

Parameter 'origin' must have exactly one value

This API permits a single value for origin.

Parameter 'destination' must have exactly one value

This API permits a single value for destination.

Parameter 'departuredate' must have exactly one value

This API permits a single value for departuredate.

Parameter 'returndate' must have exactly one value

This API permits a single value for returndate.

Parameter 'departuredate' must have a format of 'yyyy-MM-dd' and be a valid date

The date is not valid, for example, yyyy-02-29 when the year is not leap year.

The month is not valid, for example, 13.

The day is not valid for the month, for example yyyy-04-31.

The date has an incorrect format, for example, a hyphen character is omitted.

Although the data type is string, the service detected non-numeric characters for yyyy, mm, or dd.

A date is formatted as yyyy-dd-mm instead of yyyy-mm-dd.

The value in dd is a single digit.

The value in mm is a single digit.

Parameter 'returndate' must have a format of 'yyyy-MM-dd' and be a valid date

The date is not valid, for example, yyyy-02-29 when the year is not leap year.

The month is not valid, for example, 13.

The day is not valid for the month, for example yyyy-04-31.

The date has an incorrect format, for example, a hyphen character is omitted.

Although the data type is string, the service detected non-numeric characters for yyyy, mm, or dd.

A date is formatted as yyyy-dd-mm instead of yyyy-mm-dd.

The value in dd is a single digit.

The value in mm is a single digit.

Parameter 'departuredate' must be today or a future date

departuredate uses a past date.

Parameter 'returndate' must be today or a future date

returndate uses a past date.

Date range in 'departuredate' and 'returndate' exceeds the maximum allowed

For the maximum days between departuredate and returndate, see returndate.

Parameter 'departuredate' exceeds the maximum days allowed

For the maximum parameter value, see departuredate.

Parameter 'returndate' exceeds the maximum days allowed

For the maximum parameter value, see returndate.

Parameter 'departuredate' must be before 'returndate'

A date range is not valid, for example, departuredate is later than returndate.

Parameter 'pointofsale' has an unsupported value

The value provided in pointofsale is not a valid or supported country code. See also: point of sale.

Docs Navigation