HERE Shadows API
The Shadows service provides an effective way to manage configurationsfor devices that are only intermittently online.The device shadow contains `reported` and `desired` state objects of a device,referred to as `reported` and `desired` shadows.The `desired` shadow contains configuration settings that the device should use and possibly alsosome optional custom settings.The device receives the `desired` shadow from HERE Tracking as a response to the ingestion request.The `reported` shadow contains the most recent position, sensor readings and settings that thedevice has sent. The reported shadow may also contain additional properties generated by HERETracking based on the device-ingested telemetry. Such properties are stored in the `system.computed`property.In case the most recent telemetry did not contain all the possiblefields, the last known information will remain in the shadow. This means that one cansee, for example, the last reported temperature or tracker firmware information in the reported shadow,even if the device did not send that information in the latest telemetry.> **IMPORTANT**> Devices should not communicate directly with this service, but should instead send the telemetry to> the ingestion endpoint, which updates the `reported` shadow and returns the `desired` shadow.> Applications should only write to the `desired` shadow and only read from the> `reported` shadow.
HERE Shadows API is one of 139 APIs that HERE publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Shadows. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 9 operations across 7 paths. It is described by OpenAPI 3.2.0, at version 2.6.11.
Requests are made against 2 base URLs: https://tracking.hereapi.com/, https://tracking.api.here.com/.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 6
HERE Shadows API declares
6 security schemes
for authenticating requests.
An API key is passed in the query as apiKey (ApiKey).
It accepts HTTP bearer tokens (JWT) (Bearer).
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).
ApiKey— A key generated specifically to authenticate API requests. For more information on how to get an API key, see the [Identity & Access Management Developer Guide…Bearer— A token obtained from a separate endpoint using client credentials and an OAuth 1.0a HMAC-SHA256 signed request. Users are authenticated using an OAuth 1.0 bea…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 9
Across 7 paths, the API surfaces 9 operations — 1 DELETE, 6 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
The Shadows service provides an effective way to manage configurations for devices that are only intermittently online.
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 Shadows 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.