Migration overview
Overview
This API documentation is a step-by-step guide to support you with the migration from v1.0 to v3 of Flight Indicative Prices API.
We try to make this as easy as possible, and provide a step by step guide to migration.
info
Why is it v3 and not v2
We are moving from v1.0 to v3, as v2 changes include internal updates with no external changes.
What’s changing?
We have completely rebuilt the Flight Indicative Prices API with a simpler setup. The new version of the Flights API is built on top of Skyscanner’s own services, giving you access to the same features and functionality we offer our own travellers.
These are the big changes in v3:
- Browse Dates (grid) is not supported anymore
- Consolidated quotes, routes, and dates endpoints into one endpoint
v1.0 to be decommissioned
As we will be decommissioning v1.0 of the Flights API by January, we ask that you migrate to v3 by 31st January 2023. If you fail to do so, you will not be able to access our Flights API.
Any new features will be released on v3 of the Travel API only.
v3 API Differences
Before getting through the migration guide, here are some things to note on what will be changing:
- Different endpoints
- API key is now passed via header
- API Response status codes
- Request / response data has a different structure
v3 follows a similar flow to v1.0 but has breaking changes so you will need to change endpoints, and map to different data to migrate across.
Api Key
If you are an existing partner, we will be using the same API key for the new version of the Travel API
If you are not an existing partner and would like to access our Travel APIs, you will have to raise an application request for an API key. Please note that applications are subject to approval, and you’ll be notified of the outcome within a month.
tip
If you want a quick guide of the migration, please go to the Migration Quick Guide.