HERE

HERE Sensors API

The Sensors service creates and manages sensor rules. The sensor rules generate events and notifications when get triggered by a reported device sensor reading. The following sensor rule types are supported: * battery * humidity * pressure * temperature * acceleration * attach * tamper After a sensor rule has been created, it needs to be associated to a device to get activated. This association means that every time a sensor update is received from the device as a part of its ingestion telemetry, it will be evaluated against the sensor rule condition. As soon as the evaluation changes (for example, from true to false), an event will be recorded.

GitHub OpenAPI

Operations 8

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /sensors/v3/health Check the Sensors service health · Gets service health #
Ask an LLM
“Is the HERE Tracking Sensors service up right now?”
“Can I ping the Sensors service before sending it requests?”
Tell an agent
Check the health of the Sensors service.
Tell me whether the Sensors service is healthy.
GET /sensors/v3/version Get the Sensors service version · Gets service version #
Ask an LLM
“What version of the Sensors service is deployed?”
“Which build of the Sensors service am I talking to?”
Tell an agent
Get the version of the Sensors service.
Show me which Sensors service version is running.
POST /sensors/v3 Create a sensor rule · Creates a sensor rule #
Ask an LLM
“How do I alert when a tracker's temperature leaves a range?”
“Can I create a battery level sensor rule?”
Tell an agent
Create a sensor rule in project {projectId}.
Add a new temperature range sensor rule to my project.
GET /sensors/v3 List all sensor rules · Gets all sensor rules #
Ask an LLM
“Which temperature, humidity or battery sensor rules exist in my project?”
“Can I page through every sensor rule?”
Tell an agent
List all sensor rules in project {projectId}.
Show {count} sensor rules per page.
DELETE /sensors/v3 Delete every sensor rule in a project · Deletes all sensor rules #
Ask an LLM
“Can I wipe all sensor rules from a project at once?”
“What confirmation is needed to delete all sensor rules?”
Tell an agent destructive · confirm first
Delete all sensor rules in project {projectId} with x-confirm {confirm}.
Remove every sensor rule, confirming with {confirm}.
GET /sensors/v3/{sensorRuleId} Get one sensor rule · Gets a single sensor rule #
Ask an LLM
“What range or threshold does a specific sensor rule use?”
“Can I fetch a single sensor rule by ID?”
Tell an agent
Get sensor rule {sensorRuleId}.
Show the range of sensor rule {sensorRuleId}.
PUT /sensors/v3/{sensorRuleId} Update a sensor rule's range or threshold · Updates a single sensor rule #
Ask an LLM
“Can I change the temperature range of an existing sensor rule?”
“Will unspecified sensor rule fields be reset to null on update?”
Tell an agent
Update sensor rule {sensorRuleId} with a new range.
Change the threshold and name of sensor rule {sensorRuleId}.
DELETE /sensors/v3/{sensorRuleId} Delete one sensor rule · Deletes a sensor rule #
Ask an LLM
“Can I delete a single sensor rule?”
“What removes one sensor rule by ID?”
Tell an agent destructive · confirm first
Delete sensor rule {sensorRuleId}.
Remove the single sensor rule {sensorRuleId}.

Documentation

📖
Documentation
https://docs.here.com/identity-and-access-management/docs
📖
APIReference
https://docs.here.com/identity-and-access-management/reference
📖
Documentation
https://docs.here.com/data-api/docs
📖
APIReference
https://docs.here.com/data-api/reference
📖
Documentation
https://docs.here.com/usage/docs
📖
APIReference
https://docs.here.com/usage/reference
📖
Documentation
https://docs.here.com/destination-weather/docs
📖
APIReference
https://docs.here.com/destination-weather/reference
📖
Documentation
https://docs.here.com/ev-products/docs
📖
APIReference
https://docs.here.com/ev-products/reference
📖
Documentation
https://docs.here.com/fuel-prices/docs
📖
APIReference
https://docs.here.com/fuel-prices/reference
📖
Documentation
https://docs.here.com/geocoding-and-search/docs
📖
APIReference
https://docs.here.com/geocoding-and-search/reference
📖
Documentation
https://docs.here.com/routing/docs
📖
APIReference
https://docs.here.com/routing/reference
📖
Documentation
https://docs.here.com/positioning/docs
📖
APIReference
https://docs.here.com/positioning/reference
📖
Documentation
https://docs.here.com/indoor-map/docs
📖
APIReference
https://docs.here.com/indoor-map/reference
📖
Documentation
https://docs.here.com/transit/docs
📖
APIReference
https://docs.here.com/transit/reference
📖
Documentation
https://docs.here.com/map-attributes/docs
📖
APIReference
https://docs.here.com/map-attributes/reference
📖
Documentation
https://docs.here.com/map-rendering/docs
📖
APIReference
https://docs.here.com/map-rendering/reference
📖
Documentation
https://docs.here.com/workspace/docs
📖
APIReference
https://docs.here.com/workspace/reference
📖
Documentation
https://docs.here.com/tour-planning/docs
📖
APIReference
https://docs.here.com/tour-planning/reference
📖
Documentation
https://docs.here.com/tracking/docs
📖
APIReference
https://docs.here.com/tracking/reference
📖
Documentation
https://docs.here.com/traffic-api/docs
📖
APIReference
https://docs.here.com/traffic-api/reference
📖
Documentation
https://docs.here.com/wego-pro/docs
📖
APIReference
https://docs.here.com/wego-pro/reference

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/here/refs/heads/main/openapi/here-sensors-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/here:here-sensors-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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

OpenAPI Specification

here-sensors-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  version: 2.6.11
  title: HERE Tracking Sensors API
  description: 'HERE Tracking is a cloud product designed to address location tracking problems for a wide range of Location IoT industry verticals.


    HERE Tracking also includes end-user mobile and web applications that can be used to demonstrate the product.'
  license:
    name: HERE Documentation License
    url: https://legal.here.com/en-gb/terms/documentation-license
servers:
- url: https://tracking.hereapi.com/
- url: https://tracking.api.here.com/
tags:


# --- truncated at 32 KB (66 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/here/refs/heads/main/openapi/here-sensors-api-openapi.yml