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 Notification API v2 API

The Notification API v2 API from HERE — 2 operation(s) for notification api v2.

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

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

This API exposes 3 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2.0.1.

Requests are made against a single base URL, https://use.apilookup.for.a.base.url/.

3 operations 2 paths 4 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

HERE Notification API v2 API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer). By default, every request must be authenticated.

  • 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…

Paths & Operations 3

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

Notification API v2 3
POST
/subscriptions
Subscribe for Catalog change notifications
NotificationAPISubscribe 2 params body → 201400403500
GET
/layers/{notificationStreamLayerId}
Get all subscriptions for target layer
NotificationAPIGetSubscriptions 1 param → 200404500
DELETE
/layers/{notificationStreamLayerId}
Delete subscriptions for provided catalogHRN and stream layer ID
NotificationAPIDeleteSubscriptions 1 param body → 200404409500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Attribute (3 properties), SubscribeRequest (3 properties), DeleteRequest (2 properties), SubscriptionArea (1 property). Each schema is shown below with its type and property counts.

DeleteRequest
object
2 properties
SubscribeRequest
object
3 properties
Attribute
object
3 properties
SubscriptionArea
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

here-notification-api-v2-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 Notification API v2 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.