Airline Lookup

The Airline Lookup API returns the airline name associated with a specified IATA airline code. If no code is specified, the API returns all codes and their corresponding names.

This API can be used with any API that accepts or returns an airline code: Bargain Finder Max, Alternate Date, Advanced Calendar Search and InstaFlights Search. See usage notes: for more information about these APIs.

API Information

Target Audience
Sabre Travel Network
Current Version
v1
Authentication
Sessionless Token
Method/Endpoint
GET /v1/lists/utilities/airlines/ HTTP/1.1

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

Sample use case

You could use this API to create a search filter that allows customers to specify an airline. From this data, brand-loyal customers can sort and filter search results by airline.

Request

airlinecode

string, optional

2-character IATA airline code

Multiple values are accepted

Default: all codes and their corresponding names

Sample value: airlinecode=AC,A2,A9

Response

AirlineInfo

array

Repeats associated airline information:

  • AirlineCode, string
  • AirlineName, string
  • AlternativeBusinessName, string
AirlineInfo.AirlineCode

string

Returns the specified airline code(s)

Sample value: AI

AirlineInfo.AirlineName

string

The proper business name of the specified airline code

Sample value: Air India Limited

AirlineInfo.AlternativeBusinessName

string

The common business name of the specified airline code

Sample value: Air India

Overall response links

Link nodes

array

See usage notes: for more information on link nodes.

self

object

Returns the URL of the request that generated the response

linkTemplate

object

Formats an Airline Lookup API request with placeholders for every request parameter

Examples: request and response

The following example demonstrates a request for the airline name associated with an IATA airline code.

GET https://api.sabre.com/v1/lists/utilities/airlines?airlinecode=AI
{  
   AirlineInfo:[  
      {  
         AirlineCode:"AI",
         AirlineName:"Air India Limited"
         AlternativeBusinessName: "Air India"
      }
   ],
   Links:[  
      {  
         rel:"self",
         href:"https://api.sabre.com/v1/lists/utilities/airlines?airlinecode=AI"
      },
      {  
         rel:"linkTemplate",
         href:"https://api.sabre.com/v1/lists/utilities/airlines?airlinecode=<airlinecode>"
      }
   ]
}

Usage notes

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.

Advanced Calendar Search (beta) API

The Advanced Calendar Search API returns up to 200 of the lowest published fares across a 6 month window from the Sabre cache for a given city pair. Numerous travel date preferences are available, including the ability to limit flight options to specific days of the week.

Alternate Date API

The Alternate Date API returns the lowest available priced itineraries within +/- 1-3 days of a specified travel date.

Bargain Finder Max API

The Bargain Finder Max API returns the lowest available priced itineraries for a specified travel date.

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.

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.

Status 400 BAD REQUEST

400 Parameter 'airlinecode' must be a valid value

Value must be a valid airline code.

{specified code} is not a valid airline code.

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.

Docs Navigation