HERE Metadata API
Get information about catalogs, layers, and partitions
HERE Metadata API is one of 139 APIs that HERE publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Metadata. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 29 operations across 22 paths, and defines 76 schemas. It is described by OpenAPI 3.2.0, at version 1.0.
Requests are made against 5 base URLs: https://use.apilookup.for.a.base.url/, https://image.maps.hereapi.com/mia/v3, https://maps.hereapi.com/v3, https://tracking.hereapi.com/, https://tracking.api.here.com/.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 6
HERE Metadata API declares
6 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (Bearer).
An API key is passed in the query as apiKey (ApiKey).
It accepts HTTP bearer tokens (JWT) (UserToken).
It accepts HTTP bearer tokens (JWT) (ClientToken).
It accepts HTTP bearer tokens (JWT) (DeviceToken).
It uses HTTP oauth authentication (signedRequest).
Bearer— A token obtained from a separate endpoint using client credentials and an OAuth 1.0a HMAC-SHA256 signed request. For more information on how to get a bearer to…ApiKey— A key generated specifically to authenticate API requests. For more information on how to get an API key, see the [Identity & Access Management Guide - API Key…UserToken— This token is obtained using user's realm, username and password and then further scoped to a specific project. First obtain access token from [/users/v2/login…ClientToken— This token is obtained using application's OAuth 2.0 credentials (key + secret) and then scoped to a specific project. Follow [instructions here](https://www.h…DeviceToken— This access token is obtained from [/v2/token endpoint](tag/Ingestion/paths/~1v2~1token/post) using a signed request. Note: Only a small subset of our endpoint…signedRequest— HERE Tracking requires that you sign your requests for tokens. The signature method uses the OAuth 1.0 standard. For more information on this standard, see the…
Paths & Operations 29
Across 22 paths, the API surfaces 29 operations — 3 DELETE, 18 GET, 5 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.
Get information about catalogs, layers, and partitions
Schemas 76
The contract defines 76 schemas that model the data the API accepts and returns. The most detailed are InfoSchema (10 properties), Partition (8 properties), ErrorResponseSchema_2 (7 properties), InternalServerErrorResponseSchema (7 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from HERE 12
Other APIs HERE publishes across the network.
This is an independent, third-party profile of HERE Metadata API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.