HERE Geofences API
The Geofences service creates and manages geofences.A geofence is an area boundary that users can define and associate with their devices.The area that the geofence encloses can be defined using geographic coordinates or radio measurements.Geographic geofences can be `circular` or `polygonal`.A circular geofence is defined by geographic coordinates of its center and a radius,while polygonal geofences are defined as a set of geographic coordinates.`POI geofence` (Point Of Interest) is a geofence, which is defined using radio measurements.POI geofences need to be trained separately using a telemetry that a device has recorded whilebeing at the desired point of interest.Once created, a geofence can be associated to a device.Every time a position or a radio measurement update is received from a device,HERE Tracking would evaluate whether the device has transitioned across the boundary ofan associated geofence.If such a transition has happened, a transition event will be recorded.For the geographic geofences, the evaluation is based on the coordinates of the trace.For POI geofences, the device is considered to be inside a trained POI geofence when the radiomeasurements of the device-ingested telemetry and the training data match.Indoor geofences can be created by adding the floor properties to the geofence definition.Circular and polygonal geofences can be both outdoors and indoors.POI geofences should only be used indoors.For indoor geofences a device transition is recorded only if the position of the device is indoorsand the floor details of the position match the geofence floor definition.NOTE: A geofence can also be referred to as a geozone, and these two terms are interchangeable.
HERE Geofences API is one of 139 APIs that HERE publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Geofences. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 10 operations across 6 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 Geofences 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 6 paths, the API surfaces 10 operations — 2 DELETE, 4 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
The Geofences service creates and manages geofences.
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 Geofences 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.