How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

HERE Largedata API

The Largedata service is used for storing large data blobs from devices toHERE Tracking and retrieving the resulting assembled data from HERE Tracking by the users.The data upload from a device follows the multipart data upload pattern:* Create a new data upload.* Check that the upload status is no longer ***preparing***.* For each part:** Upload the part.* Complete the upload after all parts have been uploaded.A data upload state can be one of the following:* ***preparing***: The storage for the data is being prepared.* ***pending***: Data upload has been succesfully created but no parts have been uploaded yet.* ***ongoing***: Data upload is ongoing.* ***completed***: Data upload has been successfully completed.* ***failed***: Data upload has failed.Data parts can be uploaded only if the upload state is one of the following: ***pending***, ***ongoing***, ***failed***.Note that the state will be changed to ***failed*** if uploading a part fails,but if the part is uploaded again successfully, the upload state is changed back to ***ongoing***.The data can be downloaded only if the upload state is ***completed***.

HERE Largedata API is one of 139 APIs that HERE publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Largedata. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 10 operations across 9 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/.

10 operations 9 paths 0 schemas 1 DELETE6 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.6.11
Base URL
https://account.api.here.com
Authentication
API Key, HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Oauth
Resource Areas
1

Authentication & Security 6

HERE Largedata 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 10

Across 9 paths, the API surfaces 10 operations — 1 DELETE, 6 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Largedata 10

The Largedata service is used for storing large data blobs from devices to HERE Tracking and retrieving the resulting assembled data from HERE Tracking by the users.

GET
/largedata/v4/health
Gets service health
getLargedataV4Health → 200500
GET
/largedata/v4/version
Gets service version
getLargedataV4Version → 200500
POST
/largedata/v4
Creates a new data upload
postLargedataV4 1 param body → 200400401403404
PUT
/largedata/v4/{dataId}/parts/{partNumber}
Uploads a part of a large data
putLargedataV4ByDataIdPartsByPartNumber 4 params body → 204400401403404409
POST
/largedata/v4/{dataId}
Completes data upload
postLargedataV4ByDataId 3 params → 204400401403404
DELETE
/largedata/v4/{dataId}
Deletes large data
deleteLargedataV4ByDataId 2 params → 204400401403404
GET
/largedata/v4/{dataId}/data
Gets large data object
getLargedataV4ByDataIdData 4 params → 200400401403404
GET
/largedata/v4/{dataId}/metadata
Gets metadata for a large data object
getLargedataV4ByDataIdMetadata 2 params → 200400401403404
GET
/largedata/v4/{dataId}/parts
Gets parts information listing for a large data object
getLargedataV4ByDataIdParts 4 params → 200400401403404
GET
/largedata/v4/devices/{trackingId}/metadata
Gets metadata listing for all large data for a device
getLargedataV4DevicesByTrackingIdMetadata 4 params → 200400401403404

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

here-largedata-api-openapi.yml Raw ↑

Other APIs HERE publishes across the network.

HERE Geocoding and Search API
HERE Autosuggest API
HERE Tour Planning API
HERE Public Transit API
HERE Destination Weather API
HERE Map Tile API
HERE Map Image API
HERE Tracking API
HERE Positioning API
HERE Parking API
HERE Platform Data API
HERE HD Live Map
Where this information came from

This is an independent, third-party profile of HERE Largedata 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.