📄️ Authentication
For all of the Skyscanner API we use API keys to allow access to the APIs so that we know who is requesting the data.
📄️ Requests and responses
The Travel APIs request and response bodies use JSON format.
📄️ Culture information
When calling our API you will need to provide queries with localisation parameters. The following parameters must be added to every request: market, locale and currency.
📄️ Rate limits
We use rate limiting to protect our service's from strain on web servers, malicious attacks and caps on API calls per app.
📄️ IATA codes and Entity IDs
For places and locations, our Travel APIs use iata, or entityId. You can choose which type you wish to use, as the location object will accept either of these identifiers.
📄️ Create and poll
We're using examples of Flights vertical but the concept is similar to other verticals such as Car hire
📄️ Flights emissions data
Introduction
📄️ What is Impact?
Impact is a third party tool we use for tracking our partner's redirects so that we can calculate payments to partners. See Impact's Website for more details.
📄️ Enums
Below is a list of all the enums in use by the API.
📄️ Usage Guidelines
Skyscanner's market leading suite of search APIs provide globalised content and localised coverage to over 250 partners around the world. By using our API, you agree to adhere to our UX, design and usage guidelines as outlined below and which form the Technical Requirements. Failure to comply with these requirements could result in your API access being revoked.