📄️ 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 data you will need to provide responses with localization by market, locale (language), and currency, so these three parameters must be added to every request.
📄️ 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 and entity ID
For places and locations the Skyscanner APIs use iata or entityId. You can choose which type you wish to use as the location object will accept either to be passed to it.
📄️ Create and poll
In the Skyscanner searches we use a concept of create and poll within our endpoints. This is due to the amount of data that we need to gather for a full search. The latency for getting travel information from our supplier APIs can vary. To minimise the time to the first result, we provide partial results until all the supplier information was loaded. To enable this partial results, you will need to create a search session and then keep polling it until all the results loaded.
📄️ Sustainability data
Aviation Emissions data (sustainabilityData) is now available through the API!
📄️ 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.