Guides · maps · Popular APIs
Sign up for a HERE platform account on the Base Plan (payment method required), optionally create a project, register an app, and create either API keys or OAuth 2.0 credentials for HERE Location Services.
Researched · not yet run liveLast researched 25 October 2026 · HERE Technologies · provider site
A HERE platform account belongs to an organisation (realm). Inside it, projects group resources and access; apps hold credentials (API keys or OAuth 2.0 access keys). Billing is on the Base Plan.
App credentials do not inherit your user permissions or group memberships.
Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.
You sign up via "Get started for free", accept the terms and enter a payment method and billing address. You are not expected to be charged below the free monthly thresholds.
Where: https://www.here.com/get-started/pricing
Verify the email you registered with, then sign in to the HERE platform.
Where: https://platform.here.com/
In Projects Manager, click Create new project, enter a name and a project ID (4–16 characters, unique, cannot be changed), save, then on Resources > Services link the Location Services you need.
Where: https://platform.here.com/
In Access Manager > Apps, click Register new app, optionally pick a default project, and register. HERE recommends "Allow access in only default project" for apps using API keys.
Where: https://platform.here.com/
Open the app > Credentials > API Keys > Create API key. Up to two keys per app (use the second for rotation). Optionally add up to 20 trusted domains and turn on Enable trusted domains.
verapli captures HERE_API_KEY here by plain code: encrypted in your browser, never shown to AI.
Where: https://platform.here.com/
Open the app > Credentials > OAuth 2.0 > Create credentials, then Download credentials.properties. The access key secret is shown only once. Exchange it for bearer tokens valid up to 24 hours.
verapli captures HERE_ACCESS_KEY_SECRET here by plain code: encrypted in your browser, never shown to AI.
Where: https://platform.here.com/
Plain-English summary, not legal advice. Each card links its source.
You may not cache or store Results outside the HERE platform for more than 30 days (HERE Positioning 24 hours; most Japan content 24 hours), except for internal testing, evaluation or audit/legal record retention. Location Services caching is limited to what HTTP caching headers allow. [9]
You are liable for any unauthorised use of your App IDs and must notify HERE promptly. API keys work from any website unless trusted domains are enabled. [9]
You may not remove or obscure HERE marks or copyright notices, and combined content must allow correct attribution. [9]
Once you close the credentials dialog you can no longer see the access key ID and secret; download credentials.properties first. [6]
| Env var | Secret | Format | What it is |
|---|---|---|---|
HERE_API_KEY | secret | <random string>… | API key passed as the apiKey query parameter |
HERE_ACCESS_KEY_ID | not secret | <random string>… | OAuth 2.0 access key ID from credentials.properties |
HERE_ACCESS_KEY_SECRET | secret | <random string>… | OAuth 2.0 access key secret from credentials.properties (shown once) |
HERE_TOKEN_ENDPOINT_URL | not secret | https://…/oauth2/token | Token endpoint URL from credentials.properties |
Source [4]
The same entry as JSON: /api/v1/entries/here/location-services · requirements /api/v1/requirements/here/location-services · terms /api/v1/terms/here/location-services.
claude mcp add --transport http verapli https://verapli.com/mcp
> "What do I need for HERE platform – Location Services (API key or OAuth credentials), and how long will it take?"
→ tools/call requirements { "provider_id": "here/location-services" }Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. HERE Technologies is not affiliated with verapli.