Places (Search) API Developer's Guide

Localization

Where possible, the Places (Search) API will attempt to present the response data in a language specified by the Accept-Language request header.

The 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

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 München, Deutschland.

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 alternativeNames attribute.

Addresses (and 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
Afrikaans af-ZA
Albanian sq-AL
Arabic ar-SA
Azeri (Latin) az-Latn-AZ
Basque eu-ES
Belarusian be-BY
Bulgarian bg-BG
Catalan ca-ES
Chinese (China) zh-CN
Chinese (Taiwan) zh-TW
Croatian hr-HR
Czech cs-CZ
Danish da-DK
Dutch nl-NL
English (British) en-GB
English (United States) en-US
Estonian et-EE
Farsi fa-IR
Filipino tl, fil, fil-PH
Finnish fi-FI
French fr-FR
French (Canada) fr-CA
Galician gl-ES
German de-DE
Greek el-GR
Hausa ha-Latn-NG
Hebrew he-IL
Hindi hi-IN
Hungarian hu-HU
Indonesian (Bahasa) id-ID
Italian it-IT
Japanese ja-JP
Kazakh kk-KZ
Korean ko-KR
Latvian lv-LV
Lithuanian lt-LT
Macedonian mk-MK
Malay (Bahasa) ms-MY
Norwegian (Bokmål) no, nb, nb-NO
Polish pl-PL
Portuguese (Brazil) pt-BR
Portuguese (Portugal) pt-PT
Romanian ro-RO
Russian ru-RU
Serbian (Latin) sr-Latn-CS
Slovak sk-SK
Slovenian sl-SI
Spanish (Mexico) es-MX
Spanish (Spain) es-ES
Swedish sv-SE
Thai th-TH
Turkish tr-TR
Ukrainian uk-UA
Uzbek (Latin) uz-Latn-UZ
Vietnamese vi-VN

You cannot use this account to purchase a commercial plan on Developer Portal, as it is already associated to plans with different payment methods.

To purchase a commercial plan on Developer Portal, please register for or sign in with a different HERE Account.

Something took longer than expected.

The project should be available soon under your projects page.

Sorry, our services are not available in this region.

Something seems to have gone wrong. Please try again later.

We've detected that your account is set to Australian Dollars (AUD).
Unfortunately, we do not offer checkouts in AUD anymore.
You can continue using your current plan as normal, but to subscribe to one of our new plans,
please register for a new HERE account or contact us for billing questions on selfservesupport@here.com.