Where possible, the Places (Search) API attempts to present the response data in a language specified by the
Accept-Language request header.
According to the HTTP 1.1 specification, the
Accept-Language header should contain the user's language preferences which the API uses to select the best available translation for the resource information. The sections below describe in more detail how these preferences influence the response.
Content such as reviews, editorials, and extended attributes of a place are returned in the requested language if translations are available in that language. If there are no translations available, the Places (Search) API falls back to the next best alternative, according to the chosen preferences.
The API aggregates content from different sources. Depending on the availability of translations for each content source, a resource may contain content in different languages. In this case, the API makes a selection that best matches the user's request given the available content.
Place Names and Addresses
Where available, exonyms of place names and addresses are returned. For example, if a user's preferred language is English, search results containing places in Munich have addresses using the names
Munich, Germany instead of
If a place, for example in Munich, Germany, has an alternative name in English, the English name is returned as the place name and the original name is present in the
vicinity in search result items are formatted according to the locality of the place.
Labels and Ready-to-Display Strings
Labels, category names and ready-to-display strings such the
attribution attribute are translated into the requested language, if a translation is available. Otherwise the default is English. Currently, there are translations available for the following languages:
|Language name||Accept-Language header value|
|English (United States)||en-US|
|Filipino||tl, fil, fil-PH|
|Norwegian (Bokmål)||no, nb, nb-NO|