Skyscanner API API
Skyscanner's API is documented at developers.skyscanner.net: flight, hotel, and car-hire prices over REST. Access is partner-gated; the Affiliates Link API is the light tier, and the full Travel API is manually approved for established partners only. Caching price data is forbidden.
Frequently asked questions
Skyscanner API scores C on the API Report Card. Skyscanner's API is documented at developers.skyscanner.net: flight, hotel, and car-hire prices over REST. Access is partner-gated; the Affiliates Link API is the light tier, and the full Travel API is manually approved for established partners only. Caching price data is forbidden.
Skyscanner API has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood.
Skyscanner is a global travel meta-search engine, flights, hotels, and car hire, headquartered in Edinburgh, Scotland and founded in 2003 by Gareth Williams, Bonamy Grimes, and Barry Smith.
Vertical: Travel meta-search (flights + hotels + car hire). Sub-vertical: consumer OTA / travel content publisher API. White-label flight, hotel, and car-hire search inside partner OTAs, airlines, super-apps, and travel-media properties.
Very high in consumer brand awareness. Skyscanner is one of the top three globally-recognized flight-search brands alongside Google Flights and Kayak (Booking Holdings).
Flight itinerary search criteria (origin, destination, dates, cabin, pax composition). Live flight pricing (fare + taxes + total) per carrier and OTA agent. Indicative / cached flight pricing for browse and SEO. Carrier / airline metadata (IATA codes, names, logos).
Founded in 2003; ~23 years old as of 2026. One of the original flight meta-search engines. Cloud-native rebuilds over the years; modern web/mobile UIs; native iOS/Android apps with millions of downloads.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.