Low Fare Forecast (beta)

The Low Fare Forecast (beta) API forecasts whether the lowest published fare will rise, fall or stay the same within the next 7 days.

API Information

Target Audience
Sabre Travel Network
Current Version
v2
Authentication
Sessionless Token
Method/Endpoint
GET /v2/forecast/flights/fares

In detail: the API predicts the direction of the lowest published fare and returns a ("Buy Now" "Buy Soon" or "Wait") recommendation of whether to purchase, based on:

  • historical price changes—the API uses the Travel Insight engine to retrieve 13 months of historical shopped fares for a given city pair/travel date available in the Sabre® cache to compare to the lowest published fare.
  • direction coupled with percent probability—the API predicts a direction that the then-current lowest published fare is predicted to go–increase, decrease, or stay within $20 of the lowest published fare in the next 7 days—and returns a percent probability that the fare will go in that direction.

For example, if a value of 95 is returned for percent Probability, with a Direction of Increase, then there is a 95% probability that the lowest published fare will go up $20 or more in the next 7 days. Therefore, there is a very strong indication that fares will go up and a Recommendation of "Buy Now" will be returned.

Ready to try the APIs?

Ready to get your hands dirty?

 Register Try the APIs

Ready to launch?

Ready to step up to the production level service? We're standing by to fit you for your spacesuit.

Request Production Key

Business use case

You could use this API to notify travelers that a flight price is predicted to go up/down and the percent probability that the change in direction will occur. For example, when the service returns a Buy Now recommendation, an indication of Increase, and a Probability of 95, the client app can notify the end user with a message and recommendation. The message could say "Buy now and avoid a projected price increase. Our algorithm projects a 95% probability that fares to San Francisco will rise more than $20 in the next 7 days."

Data used for predicted and lowest published fares

The API uses the same data for the predicted probability and lowest published fares, with these minor differences:

  • The predictions are based on 13 months of historical shopped fares. If 13 months of data are not available, the API uses the maximum months available. The last date for the shopped fare data ends on the Sunday before an API request is submitted. The API retrieves the shopped fares from Sabre GDS shopping responses to shopping requests made from points of sale in the U.S. and Canada.
  • The lowest published fare is retrieved from shopping responses from the Sabre GDS to shopping requests for fares made from points of sale in the U.S.

The API uses this data for the predictions and the lowest published fares available via the Sabre GDS:

  • Published 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, direct, and flights with stops
  • All departure and arrival times of day
  • Departure and return dates are a maximum of 60 days into the future
  • Certain origins and destinations located in the United States, Puerto Rico, and the U.S. Virgin Islands

Request

origin

string, required

3-letter IATA code of the origin airport

Sample value: origin=ATL

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. Use the specific HTTP method and endpoint applicable to the Low Fare Forecast API.

destination

string, required

3-letter IATA code of the destination airport

Sample value: destination=LAS

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. Use the specific HTTP method and endpoint applicable to the Low Fare Forecast API.

departuredate

string, required

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

Only one value is accepted

Maximum value: current date + 60 (days)

Sample value: departuredate=2016-10-30

returndate

string, required

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

Only one value is accepted

Maximum value: current date + 60 (days)

Sample value: returndate=2016-10-31

Response

OriginLocation

string

Returns the specified 3-letter IATA origin airport code

DestinationLocation

string

Returns the specified 3-letter IATA destination airport code

DepartureDateTime

string

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

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

ReturnDateTime

string

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

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

Recommendation

string

The recommendation of whether to purchase the lowest published fare, based on:

  • Direction–the direction that the lowest published fare is predicted to go (increase, decrease, stay)
  • Probability–the percent probability that the fare will go in that direction

Return values:

  • Buy Now–there is a strong indication that the lowest published fare will go up $20 or more in the next 7 days
  • Buy Soon–there is some indication that the lowest published fare may go up $20 or more in the next 7 days
  • Wait–there is a strong indication that the lowest published fare will go down $20 or more in the next 7 days
LowestFare

number or string

The (then-current) lowest published fare available at the time of the API request

This number is compared and analyzed against historical price changes

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

Sample value: 480.6

CurrencyCode

string

3-letter currency code

Sample value: USD

Probability

number

The percent probability that the lowest published fare will go up (or not) by $20 or more in the next 7 days

Sample value: 95

For example, if a value of 95 is returned for percent probability, with a Direction of Increase, then there is a 95% probability that the lowest published fare will go up. Therefore, there is a very strong indication that fares will go up and a Recommendation of “Buy Now” will be returned.

Direction

string

The direction that the lowest published fare is predicted to go

Valid values:

  • Increase–the API predicts that the lowest published fare will go up
  • Decrease–the API predicts that the lowest published fare will go down
  • Stay–the API predicts that the lowest published fare will stay the same
Links node array

array

See usage notes: for more information on links nodes.

self

object

Returns the URL of the request that generated the response

linkTemplate

object

Formats a Low Fare Forecast API request

shop

object

Invokes an InstaFlights Search API request for flight itineraries and pricing

The InstaFlights Search request uses the values in DepartureDateTime, ReturnDateTime, OriginLocation, and DestinationLocation in the response.

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

Sample code

Request

This example demonstrates a request for a fare forecast from airport code DFW (Dallas Fort Worth International) to LAS (McCarran International, Las Vegas) on roundtrip travel dates.

GET https://api.havail.sabre.com/v2/forecast/flights/fares?origin=DFW&destination=LAS&departuredate=2016-09-22&returndate=2016-09-27

Response

{
  "OriginLocation": "DFW",
  "DestinationLocation": "LAS",
  "DepartureDateTime": "2016-09-22T00:00:00",
  "ReturnDateTime": "2016-09-27T00:00:00",
  "Recommendation": "Buy Now",
  "LowestFare": 166.2,
  "Direction": "Increase",
  "CurrencyCode": "USD",
  "Probability": 55,
  "Links": [
    {
      "rel": "self",
      "href": "https://api.havail.sabre.com/v2/forecast/flights/fares?origin=DFW&destination=LAS&departuredate=2016-09-22&returndate=2016-09-27"
    },
    {
      "rel": "linkTemplate",
      "href": "https://api.havail.sabre.com/<version>/forecast/flights/fares?origin=<origin>&destination=<destination>&departuredate=<departuredate>&returndate=<returndate>"
    },
    {
      "rel": "shop",
      "href": "https://api.havail.sabre.com/v1/shop/flights?origin=DFW&destination=LAS&departuredate=2016-09-22&returndate=2016-09-27&pointofsalecountry=US"
    }
  ]
}

Usage notes

Sabre® does not guarantee that any fares will increase or decrease. Sabre makes no warranties of any kind regarding any predictions or other information provided via the Low Fare Forecast API.

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. The origins and destinations are airport codes.

Errors

An HTTP status code is always returned. For information about the error response format, see the: Sabre APIs: errors page.

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.

400 BAD REQUEST

Parameter 'origin' must be specified

origin is missing.

origin is missing a value.

A request is missing multiple required parameters. The service inserts the first missing parameter that it encounters within ‘ ’.

Parameter 'destination' must be specified

destination is missing.

destination is missing a value.

A request is missing multiple required parameters. The service inserts the first missing parameter that it encounters within ‘ ’.

Parameter 'departuredate' must have a format of 'YYYY-MM-DD' and be a valid date

A date is not valid, for example, yyyy-02-29 for a year that is not leap year.

A month is not valid, for example, 13.

A day is not valid for the month, for example 2013-04-31.

A date has an incorrect format, for example, a hyphen character is omitted, or the format uses slashes instead of hyphens, as in 2013/10/10.

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 specified

departuredate is missing.

departuredate is missing a value.

Parameter 'departuredate' must be before 'returndate'

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

Parameter 'departuredate' must have exactly one value

departuredate passes multiple values. This API allows only one date.

Parameter 'departuredate' must be today or a future date

departuredate includes a past date.

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

A date is not valid, for example, yyyy-02-29 for a year that is not leap year.

A month is not valid, for example, 13.

A day is not valid for the month, for example 2013-04-31.

A date has an incorrect format, for example, a hyphen character is omitted, or the format uses slashes instead of hyphens, as in 2013/10/10.

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 be specified

returndate is missing.

returndate is missing a value.

Parameter '{parameter name}' exceeds the maximum days allowed

Applies to departuredate and returndate

For the maximum parameter values, see Request.

Docs Navigation