Where possible, the Places (Search) API will attempt to present the response data in a language specified by the
Accept-Language request header.
Accept-Language header should contain the user's language preferences according to the HTTP 1.1 specification. These preferences are used 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 place reviews and editorials and extended attributes of a place will be returned in the requested language if translations are available for it. If there are no translations available, the Places (Search) API will fall back to the next best alternative given the preferences chosen.
Places (Search) API aggregates content from different sources. Depending on the availability of translations for each content source, it may be the case that a resource contains content in different languages. In this case, the Places (Search) API will make a selection that best satisfies 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 would 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 would be returned as the place name and the original name would be 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 will be translated into the requested language, if a translation is available. Otherwise the default is English. There are currently translations 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|