Overview
Introduction
All of our Travel API responses are localized by market, locale (language), and currency, so these three parameters must
be added to every request.
You can use the Culture API to get all the markets, locales and currencies we support.
How it's used in Skyscanner
We use the culture parameters to localise our website. You can find the culture selector at the top of all our pages, which allows travellers to change the localisation settings.
We associate markets with the top level domains of our website. The locale is associated with the language we display our pages in. The currency is associated with format we use to display the prices.
The market used can influence the search results and their prices, because suppliers can treat countries of purchase differently. The locale and currency, however, do not influence the results.
Endpoints
/markets
You can use the /markets endpoint to retrieve the market countries that we support.
Most suppliers (airlines, travel agents, and car hire dealers) set their fares based on the market (or country of purchase). It is therefore necessary to specify the market country in every query.
The names of the markets returned are localised based on a locale passed as a parameter.
See Markets guide for more details
/locales
You can use the /locales endpoint to retrieve the locales that we support to translate your content.
The names of the locales returned are in the native language associated with the locale.
See Locales guide for more details
/currencies
You can use the /currencies endpoint to retrieve the currencies that we support and information about how we format
them in Skyscanner.
See Currencies guide for more details
/nearestculture
You can use the /nearestculture endpoint to retrieve the most relevant culture information for a user,
based on an IP address.