What is it?
In detail: the API uses the Travel Insight engine to retrieve shopped fare data for a given origin available in the Sabre® cache. In total, each request returns a nonstop lead fare and an overall lead fare available to every destination in the world for which lead fares are found. Numerous optional search preferences are available to sort and filter results, including the ability to specify a region, theme or multiple lengths of stay.
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?
Business use case
You could use this API to offer travelers the ability to compare trips for either 3 or 4 days and thereby select a trip based on price and location. For example, leisure travelers with flexible travel dates could use the API to determine the best destinations for a trip from "DFW" (Dallas/Fort Worth International) based on a specified length of stay of 3 or 4 days.
How it works
Data used by Destination Finder 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
Data used for
The following data is used only with the optional
- Data is derived from flights booked via the Sabre GDS during the 2 weeks before an API request.
- Data is based on combined passenger types.
- From each booking, the final destination of the outbound flight leg is used as input data.
- Data is derived from bookings made by leisure travel agencies throughout the world.
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.
Calculate Air Mileage API
The Calculate Air Mileage API is a SOAP API that calculates the mileage from origin to destination as obtained from IATA. The Destination Finder API invokes this service to calculate the cost-per-mile when a
pricepermile value is specified 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 Destination Finder 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.
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 (MAC) codes can be used with applicable REST APIs.
Example: Within the Destination Finder 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.
When a top destination is a multi-airport city (MAC)
If a top ranked destination is a multi-airport city, lead fares to any destination airport(s) belonging to that MAC might be in the response. The destination airport(s) will be assigned the same
DestinationRank unless the destination airport(s) was already defined to a different top destination location rank.
QDF, the MAC code for Dallas - Fort Worth, is a top destination with a
5, the lead fares to airports that belong to that MAC, including
DFW (Dallas Fort Worth International) and
DAL (Dallas Love Field), may both be included in the response. Both
QDF would be assigned the same
5, only if
DFW (Dallas Fort Worth International) is not yet defined in the top destination location rank.
Custom Region API
The Custom Region API enables you to modify and customize regions. You can create a custom region and associate that region with country or airport code(s). You can then pass your custom region as a filter in a request with any REST API that supports a region. The response will be destinations that are associated with your region.
Region Lookup API
To get a list of Sabre regions, use the Region Lookup API. The response will be a list of valid Sabre regions, such as NORTH AMERICA.
Region Details Lookup API
To get a list of airport codes associated with a given Sabre region, use the Region Details Lookup API. The response will be a list of airport code(s), such as DFW, LAX, JFK.
Custom Theme API
The Custom Theme API enables you to modify and customize themes. You can create a custom travel theme and associate that theme with airport and multi-airport city (MAC) codes. You can then pass your custom theme as a filter in a request with any REST API that supports a theme. The response will be destinations that are associated with your theme.
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
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
Got an error, but unsure what it means? Go to our Errors page.