Skip Navigation

City Pairs Lookup

Air
Utility
REST API
Travel Agency
Try Now

What is it?

Sabre® creates and maintains the file of city pairs in the Sabre cache. These city pairs are origins and destinations that we support for various REST APIs. For example, City Pairs Lookup retrieves the SJU-MIA city pair (San Juan International, Puerto Rico to Miami International). You can pass this city pair for any applicable air search API request, e.g., Lead Price Calendar.

Note: Destinations differ when you add a theme. See usage notes: for more information on the Theme Airport Lookup API.

Note: This API requires activation and Sabre Dev Studio/Travel Insight Engine Amendment to be signed. Please contact your Sabre Account Representative for assistance.

How to use

If you want origins and destinations in specific countries, you can combine country codes (e.g., https://api.cert.platform.sabre.com/v1/lists/supported/shop/flights/origins-destinations?origincountry=PR&destinationcountry=VI).

Identifying our pairs of origin and destination airports

Pass these city pairs with our air shopping REST APIs.

  1. Decide which combinations of origin (departure) and destination (arrival) airports that you want your solution to support. Origins and destinations vary by API, so read about using city pairs data.
  2. Call the City Pairs Lookup API and verify that the response includes your desired airport codes as combinations of origins and destinations.
  3. Provide your combinations of origin and destination airport codes in any of our air shopping APIs that support them.

Country and airport codes

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

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.

Sample scenarios

Getting and using origins and destinations

Florida Vacations, an imaginary company based in Chicago, Illinois in the U.S., has a solution to present lowest fares for a range of calendar dates with departure from ORD (Chicago O'Hare) and arrivals to FLL (Ft. Lauderdale), MIA (Miami), and MCO (Orlando). The team reviews Lead Price Calendar in the online Sabre REST API doc. They then link to the City Pairs Lookup API and learn that Lead Price Calendar supports origin airports located in the U.S., Puerto Rico, and the U.S. Virgin Islands. Supported destination airports can be anywhere in the world. These locations fit the requirements for their solution.

The team develops an application to call the City Pairs Lookup API:

/v1/lists/supported/shop/flights/origins-destinations?origincountry=US&destinationcountry=US

The application parses these origin and destination combinations from the response: ORD > FLL, ORD > MIA, and ORD > MCO.

{
  "OriginDestinationLocations": "ORD-FLL",
  "OriginLocation": {
    "AirportCode": "ORD",
    "AirportName": "CHICAGO O'HARE",
    "CountryCode": "US",
    "CountryName": "UNITED STATES",
    "RegionName": "NORTH AMERICA"
  },
  "DestinationLocation": {
    "AirportCode": "FLL",
    "AirportName": "FT. LAUDERDALE",
    "CountryCode": "US",
    "CountryName": "UNITED STATES",
    "RegionName": "NORTH AMERICA"
  },
  "TripType": "Return"
}

The app calls Lead Price Calendar with each of these combinations, and retrieves lowest fares with departure dates on the next 192 days, for a 10-day trip.

GET /v1/shop/flights/fares?origin=ORD&destination=FLL&lengthofstay=10&departuredate=2017-04-15

The app presents the lowest fares to these destinations, with options for end-users to choose the destination airport code.