Travel Localization API - Supported Markets & Currency Codes

Request the documented supported-code configuration without query parameters. The documented response groups markets, currencies and locales, intended to supply codes for the corresponding flight, hotel and location inputs; actual entries and accepted combinations have not been independently verified. Read the returned configuration before populating selectors or validating saved travel profiles, and do not infer that every currency, language or market can be combined arbitrarily. Market is a search context, locale controls language/region formatting where supported, and currency is the quote denomination; this lookup does not itself return flight or hotel prices.

API Features

Parameter-free code discovery This configuration lookup has no query inputs and is intended to supply supported travel-search codes, not results for a particular route.

Market configuration choices Use actual returned market entries to populate search-region choices rather than assuming a universal set of accepted country codes.

Locale and denomination separation Keep language/region locale choices distinct from currency choices so application labels do not confuse formatting with price conversion.

Saved-profile code validation Check a stored travel-search profile against the retrieved configuration before reusing its market, locale or currency settings.

Live API Demo

GET /api/project/skyscanner/config-get-locale

No parameters required. Click Query to call the API.

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/skyscanner/config-get-locale?key=<API_KEY>'

curl -X GET 'https://api.opendata-api.com/api/project/skyscanner/config-get-locale?key=<API_KEY>'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Populate supported travel-search settings from the configuration response instead of hard-coding unverified option lists.
Validate the market, language and currency codes in a saved travel profile before a traveler reruns a search.
Explain the difference between a search market, display locale and quote currency in an international travel application's settings.
Check whether an application's existing localization choices still correspond to currently returned configuration codes.

Frequently asked questions

Are parameters required, and how do market, locale and currency differ?

This lookup has no query parameters. Market identifies search-region context, locale identifies supported language and regional formatting, and currency identifies quote denomination. The documented markets/locales/currencies groups need inspection in the actual response; configuration lookup itself does not return travel quotes.

Can any country, language and currency be combined?

No universal combination support has been established. Actual codes and accepted combinations remain unverified, so inspect configuration and use only inputs exposed by each endpoint. Revalidate saved travel settings; a language change is not automatically a currency conversion or an identical-market price comparison.

Related operations

Guides

View Subscription Plans →

Look Up Supported Markets, Languages and Currencies