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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
HERE

HERE Ingestion API

A generic data endpoint to send any kind of data to stream layers. See [Publish Data to a Stream layer](href="https://www.here.com/docs/bundle/data-api-developer-guide/page/rest/publishing-data-stream.html).

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 12 operations across 12 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 3 base URLs: https://use.apilookup.for.a.base.url/, https://tracking.hereapi.com/, https://tracking.api.here.com/.

12 operations 12 paths 9 schemas 5 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 6

HERE Ingestion 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 Developer Guide…
  • 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 12

Across 12 paths, the API surfaces 12 operations — 5 GET, 7 POST. Each is listed below with its method, path, parameters, and response codes.

Ingestion 12

A generic data endpoint to send any kind of data to stream layers. See Publish Data to a Stream layer.

POST
/layers/{layerId}
Endpoint for ingesting generic data
IngestAPIV1IngestData 5 params body → 200400401404413415500
POST
/layers/{layerId}/partitions
Send a list of partitions to a stream layer
IngestAPIV1IngestPartitions 3 params body → 200400401404413415500
POST
/layers/{layerId}/sdiiMessageList
Send a list of SDII messages to a stream layer
IngestAPIV1IngestSDII 5 params body → 200400401404413415500
GET
/v2/health
Gets service health
getV2Health → 200500
GET
/v2/version
Gets service version
getV2Version → 200500
GET
/v2/timestamp
Gets the current timestamp
getV2Timestamp 1 param → 200400401403429
POST
/v2/token
Requests a token for a registered device
postV2Token 2 params → 200400401403404412429
POST
/v2/
Ingests data and receives a shadow
postV2 3 params body → 200204400401403404413429
POST
/v3/
Ingests data for a device and receives a shadow
postV3 3 params body → 200204400401403404413429
GET
/v3/health
Gets service health
getV3Health → 200500
GET
/v3/version
Gets service version
getV3Version → 200500
POST
/v3/batch
Ingests data for multiple devices
postV3Batch 2 params body → 204400401403404413429

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are PublishPartition (8 properties), Response415 (7 properties), Response500 (7 properties), Response404 (7 properties). Each schema is shown below with its type and property counts.

ResponseOkSingle
object
1 property
Response413
object
6 properties
Response415
object
7 properties
Response400
object
7 properties
Response404
object
7 properties
Response500
object
7 properties
ResponseOk
object
1 property
PublishPartition
object
Metadata describing the partition being published.
8 properties 1 required
PublishPartitions
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

here-ingestion-api-openapi.yml Raw ↑

Other APIs HERE publishes across the network.

HERE Geocoding and Search API
AE Profile APIs.io
HERE Autosuggest API
AE Profile APIs.io
HERE Tour Planning API
AE Profile APIs.io
HERE Public Transit API
AE Profile APIs.io
HERE Destination Weather API
AE Profile APIs.io
HERE Map Tile API
AE Profile APIs.io
HERE Map Image API
AE Profile APIs.io
HERE Tracking API
AE Profile APIs.io
HERE Positioning API
AE Profile APIs.io
HERE Parking API
AE Profile APIs.io
HERE Platform Data API
AE Profile APIs.io
HERE HD Live Map
AE Profile APIs.io
#Ingestion
← Back to H APIs
API Details
ID
here:here-ingestion-api
Base URL
https://account.api.here.com
Docs
https://docs.here.com/identity-and-access-management/reference
Provider
HERE
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=here-ingestion-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/here-ingestion-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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