Migration quick guide
This guide gives you a quick breakdown of all the changes on one page so you can convert over a lot faster than following the stepped guide.
info
What are the variables
- {vertical} : flights | carhire | hotels
Get a list of places matching a query string
| Step | v1.0 (before) | v3 (after) |
|---|---|---|
| 1. Endpoint | GET https://partners.api.skyscanner.net/apiservices/autosuggest/v1.0/{country}/{currency}/{locale}?query={query}&apiKey={apiKey} | POST https://partners.api.skyscanner.net/apiservices/v3/autosuggest/`{vertical}` |
| 2. API key | Add apikey as a query parameter | Add x-api-key header in request |
| 3. Query data | country, currency, locale are in the url as path params, query as a query parameter | Add all the parameters in JSON format. Find more about the Query object |
For a step-by-step walk through please use the full migration guide.
Get information about the nearest place using an IP address or lat-long coordinates.
This feature is now under the nearest flights endpoint of the Geo API.
| Step | v1.0 (before) | v3 (after) |
|---|---|---|
| 1. Endpoint | GET "https://partners.api.skyscanner.net/apiservices/autosuggest/v1.0/{country}/{currency}/{locale}?id={ipAddress}&apiKey={apiKey}" | POST https://partners.api.skyscanner.net/apiservices/v3/geo/hierarchy/flights/nearest |
| 2. API key | Add apikey as a query parameter | Add x-api-key header in request |
| 3. Query data | country, currency, locale are in the url as path params, id as a query parameter | Add the locale and locator in the JSON request body. The locator takes in either coordinates or and an ipAddress |
For a step-by-step walk through please use the full migration guide.
Get information about a specific country, city or airport using a Skyscanner Place ID
Skyscanner place IDs are no longer supported.
To find out more information about a specific place, please search using the query string instead (above).
For a full list of all possible entities, please use the Geo API reference.
JSONP callbacks
JSONP callbacks are no longer supported due to security and legacy reasons.
It is recommended to make calls to our Travel APIs via a server rather than directly from the browser, for security reasons.