Skyscanner API Access: Requirements and Alternatives

You need partner approval to use the Skyscanner Travel API. Its current application page lists a minimum of 100,000 monthly active users, and meeting that number does not guarantee access. Skyscanner reviews each business separately.

Who can get a Skyscanner API key?

The API is for established commercial businesses. Skyscanner's application criteria exclude non-commercial students and individuals, startups without both a robust business plan and a pre-developed product, websites below the traffic minimum, and web development agencies.

If your business fits, apply through that page with details of your product and audience. The API key guidance explains how to use the key after approval. Reading the docs or joining an affiliate program does not by itself give you Travel API access.

For a travel site with an audience and people ready to book, it can be worth applying. For a prototype or a small app, the published criteria make it a difficult starting point.

Can you use it for price alerts?

Skyscanner's Live Pricing usage guidelines require a user action, a specific route, and exact travel dates before starting a search. They rule out automated Live Pricing calls without user action. A job that checks saved routes every morning is a different use case, even if a user originally saved those routes.

For browsing without exact dates, Skyscanner points partners to its Indicative Prices API. That is not permission to run scheduled live searches. Confirm a monitoring use case with Skyscanner before building around it. For an Ignav implementation, see the price tracker guide.

Where Ignav fits

Ignav gives you a REST API for live flight prices and booking links. Use GET /api/airports to resolve user input, POST /api/fares/one-way or POST /api/fares/round-trip for ordinary trips, POST /api/fares/search for one or two ordered legs, including open-jaw trips, and POST /api/fares/booking-links when the user selects an itinerary.

• 1,000 one-time free requests to test with real API calls.
• $2.00 per 1,000 successful requests after that.
• Failed requests are not billed.
• No monthly minimums and no per-account authenticated rate limits.

Try an Ignav fare search

Create an account with the Get API key button below, verify your email, then copy your key from the dashboard. Replace YOUR_API_KEY in the example. Run cURL in your terminal, Python after installing requests, or JavaScript in Node.js 18 or later as an .mjs file. Keep your key on your server. You can also open the example in the playground without an account.

curl -X POST "https://ignav.com/api/fares/one-way" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"origin":"SFO","destination":"JFK","departure_date":"2026-11-23"}'

This searches one route on one departure date. Choose a future date when you reuse the example. In Python, read the response with response.json(); in JavaScript, use await response.json(). Results are in the itineraries array, which can be empty. To get booking URLs, send a selected itinerary to the booking-links endpoint. Fare search does not return booking URLs.

What Ignav does not cover

Ignav is not an affiliate network and does not provide Skyscanner branding, partner attribution, cached explore-destination products, commissions, or affiliate reporting. It also does not issue tickets or manage bookings. Your app handles search and sends users elsewhere to book.

If referral income is the main goal, look at Skyscanner's affiliate program or the Aviasales options through Travelpayouts. A booking URL from Ignav does not pay a commission.

Ignav uses its own request and response formats, so it is not a drop-in replacement for a Skyscanner integration. Test the routes, dates, and markets your app needs; coverage is not identical. Booking links can be unavailable, and some open a search page where the traveler still needs to select the flight. Prices and availability can change before checkout; a search result does not reserve a seat or guarantee the final price.