What is it?
In detail: the API uses the Travel Insight Engine to retrieve booking data to calculate peak and off-peak travel periods for a given airport or multi-airport city (MAC) code available in the Sabre® cache. If a MAC is used as a destination, results will represent all airports belonging to the MAC.
In total, each request returns a booked traffic volume rating of low, medium or high for each week (1-52) of the next year for a given destination. Each week is compared with the traffic volume of the other 51 weeks. The API then calculates whether that week is high or low seasonality, e.g., week 32 is compared with the 1st, 2nd, 3rd... 33rd, 34th, 35th... 52nd weeks.
Ratings for past weeks will be for the following year. For example, if at the time of the request, the current week is week #33 in 2015, then the ratings returned for the past (1-32) weeks will be for the weeks in the following year, i.e., 2016. If a week number has not passed, then the remaining week numbers will be for the weeks in the current year, e.g. the current week is #33, then weeks 34-52 will be in 2015.
To get the future weeks that begin after the date of the request, sort the response by
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 heat map for a given destination, e.g., "NYC," the multi-airport city (MAC) code for New York City. From this, travelers can see the peak and off peak travel periods for New York City, and hence, the least expensive week in the month to fly.
How it works
Definition of weeks and a new year
The 12 previous months of bookings have either 52 or 53 weeks, depending on the calendar. The 52 future weeks begin with the week that follows the API request. The travel seasonality rating does not use the current week because the data is not complete. A week is defined as Monday through Sunday. The first day of a week is Monday. A year begins with the first week that includes both January 4 and a Thursday in January. Because a week is defined as Monday through Sunday, it is possible for the first week of a year to include dates from the previous year. In the response, weeks are numbered consecutively from 1 to 52 or 53, beginning with the first week (Week 1) of a year.
Data used for the Travel Seasonality API
- Bookings made via the Sabre GDS for travel to major destination airports throughout the world during the 52 weeks before an API request.
- All passenger types
- All cabin types: economy, first class, business, and premium economy
- All flight types: nonstop, direct, connecting, and flights with stops
- Point of sale: No limitations on locations from which bookings are made.
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.
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 Travel Seasonality API request.
Multi-Airport City 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.
Travel Seasonality Airports Lookup API
To get a list of our supported destination airports, use the Travel Seasonality Airports Lookup API. You can pass any of these destination airports in a Travel Seasonality API request.