HERE

HERE Associations API

An association is a link between a device and a geofence, a sensor rule or a rule. Device events get generated for existing associations only.

GitHub OpenAPI

Operations 17

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 /associations/v3/health Check the Associations service health · Gets service health #
Ask an LLM
“Is the HERE Tracking Associations service up right now?”
“Can I ping the Associations service before sending it requests?”
Tell an agent
Check the health of the Associations service.
Tell me whether the Associations service is healthy.
GET /associations/v3/version Get the Associations service version · Gets service version #
Ask an LLM
“What version of the Associations service is deployed?”
“Which build of the Associations service am I talking to?”
Tell an agent
Get the version of the Associations service.
Show me which Associations service version is running.
GET /associations/v3/sensors/{sensorRuleId} List devices linked to a sensor rule · Gets all devices associated with a sensor rule #
Ask an LLM
“Which devices are using a particular sensor rule?”
“Can I see every tracker associated with one sensor rule?”
Tell an agent
List the devices associated with sensor rule {sensorRuleId}.
Show which trackers sensor rule {sensorRuleId} applies to.
GET /associations/v3/geofences/{geofenceId} List devices linked to a geofence · Gets all devices associated with a geofence #
Ask an LLM
“Which devices are associated with a specific geofence?”
“What trackers generate events for one geofence?”
Tell an agent
List the devices associated with geofence {geofenceId}.
Show which trackers are watched by geofence {geofenceId}.
GET /associations/v3/rules/{ruleId} List devices linked to a rule · Gets all devices associated with a rule #
Ask an LLM
“Which devices are associated with a given tracking rule?”
“Can I find all trackers a detention or dwelling rule applies to?”
Tell an agent
Find all trackers bound to tracking rule {ruleId}.
Show which trackers rule {ruleId} is attached to.
PUT /associations/v3/{trackingId}/sensors/{sensorRuleId} Attach a sensor rule to a device · Associates a device with a sensor rule #
Ask an LLM
“How do I activate a sensor rule on a tracker?”
“Can a device have more than one sensor rule of the same sensor type?”
Tell an agent
Associate device {trackingId} with sensor rule {sensorRuleId}.
Apply sensor rule {sensorRuleId} to tracker {trackingId}.
DELETE /associations/v3/{trackingId}/sensors/{sensorRuleId} Detach a sensor rule from a device · Disassociates a device and a sensor rule #
Ask an LLM
“Can I stop a sensor rule from applying to one tracker?”
“What removes the link between a device and a sensor rule?”
Tell an agent destructive · confirm first
Disassociate device {trackingId} from sensor rule {sensorRuleId}.
Remove sensor rule {sensorRuleId} from tracker {trackingId}.
PUT /associations/v3/{trackingId}/geofences/{geofenceId} Attach a geofence to a device · Associates a device to a geofence #
Ask an LLM
“How do I get enter and exit events when a tracker crosses a geofence?”
“Can I link one device to a specific geofence?”
Tell an agent
Associate device {trackingId} with geofence {geofenceId}.
Start watching tracker {trackingId} against geofence {geofenceId}.
DELETE /associations/v3/{trackingId}/geofences/{geofenceId} Detach a geofence from a device · Disassociates a device and a geofence #
Ask an LLM
“Can I stop geofence events for one device without deleting the geofence?”
“What unlinks a tracker from a geofence?”
Tell an agent destructive · confirm first
Disassociate device {trackingId} from geofence {geofenceId}.
Stop watching tracker {trackingId} against geofence {geofenceId}.
PUT /associations/v3/{trackingId}/rules/{ruleId} Attach a rule to a device · Associates a device to a rule #
Ask an LLM
“How do I make a tracking rule generate events for a device?”
“Can I link one tracker to a single rule?”
Tell an agent
Associate device {trackingId} with rule {ruleId}.
Apply rule {ruleId} to tracker {trackingId}.
DELETE /associations/v3/{trackingId}/rules/{ruleId} Detach a rule from a device · Disassociates a device and a rule #
Ask an LLM
“Can I stop one rule from firing for a single device?”
“What removes a single rule association from a tracker?”
Tell an agent destructive · confirm first
Disassociate device {trackingId} from rule {ruleId}.
Remove rule {ruleId} from tracker {trackingId}.
GET /associations/v3/{trackingId}/sensors List sensor rules on a device · Gets sensor rules associated with a device #
Ask an LLM
“Which sensor rules are active on a given tracker?”
“What temperature or battery sensor rules apply to my device?”
Tell an agent
List the sensor rules associated with device {trackingId}.
Show tracker {trackingId}'s sensor rules.
GET /associations/v3/{trackingId}/geofences List geofences on a device · Gets geofences associated with a device #
Ask an LLM
“Which geofences is a particular device associated with?”
“Can I filter a device's associated geofences by geofence type?”
Tell an agent
List the geofences associated with device {trackingId}.
Show tracker {trackingId}'s geofences of type {type}.
GET /associations/v3/{trackingId}/rules List rules on a device · Gets rules associated with a device #
Ask an LLM
“Which rules are attached to a given tracker?”
“What rules will generate events for this device?”
Tell an agent
Find the tracking rules, not sensor rules, bound to {trackingId}.
Show tracker {trackingId}'s associated rules.
POST /associations/v3/devices/{trackingId}/batchCreate Attach several rules and geofences to a device · Associates rules with a device #
Ask an LLM
“Can I associate many rules and geofences with one device in a single call?”
“Is there a bulk way to link a tracker to rules and geofences?”
Tell an agent
Associate device {trackingId} with rules {ruleIds} and geofences {geofenceIds}.
Bulk-link tracker {trackingId} to rules {ruleIds} and geofences {geofenceIds}.
POST /associations/v3/devices/{trackingId}/batchDelete Detach several rules and geofences from a device · Disassociates rules from a device #
Ask an LLM
“Can I unlink many rules and geofences from one device at once?”
“Is there a bulk way to remove a tracker's rule and geofence associations?”
Tell an agent destructive · confirm first
Disassociate device {trackingId} from rules {ruleIds} and geofences {geofenceIds}.
Bulk-unlink tracker {trackingId} from rules {ruleIds} and geofences {geofenceIds}.
PUT /associations/v3/devices/batchUpdate Swap rule associations across many devices · Updates rules associations for devices #
Ask an LLM
“Can I replace one set of rules with another on many devices at once?”
“What's the way to move a fleet of trackers from old rules to new ones?”
Tell an agent
On devices {trackingIds}, replace rules {oldRules} with {newRules}.
Switch trackers {trackingIds} from rules {oldRules} to rules {newRules}.

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-associations-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-associations-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-associations-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  version: 2.6.11
  title: HERE Tracking Associations 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 (148 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/here/refs/heads/main/openapi/here-associations-api-openapi.yml