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 while being 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 of an 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 radio measurements 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 indoors and 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.

Operations 10

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 /geofences/v2/health Check the Geofences service health · Gets service health #
Ask an LLM
“Is the HERE Tracking Geofences service up right now?”
“Can I ping the Geofences service before sending it requests?”
Tell an agent
Check the health of the Geofences service.
Tell me whether the Geofences service is healthy.
GET /geofences/v2/version Get the Geofences service version · Gets service version #
Ask an LLM
“What version of the Geofences service is deployed?”
“Which build of the Geofences service am I talking to?”
Tell an agent
Get the version of the Geofences service.
Show me which Geofences service version is running.
POST /geofences/v2 Create a geofence · Creates a geofence #
Ask an LLM
“How do I draw a circular or polygon geofence?”
“Can I create a geofence around a point of interest?”
Tell an agent
Create a geofence in project {projectId}.
Add a new circle geofence to my project.
GET /geofences/v2 List all geofences in a project · Gets all geofences #
Ask an LLM
“Which geofences have I defined in my tracking project?”
“Can I list only the geofences inside a bounding box?”
Tell an agent
List all geofences in project {projectId}.
List geofences of type {type} inside {bbox}.
DELETE /geofences/v2 Delete every geofence in a project · Deletes all geofences #
Ask an LLM
“Can I wipe all geofences in a project at once?”
“Does deleting all geofences also remove the stock rules tied to them?”
Tell an agent destructive · confirm first
Delete all geofences in project {projectId} with x-confirm {confirm}.
Remove every geofence from my project, confirming with {confirm}.
GET /geofences/v2/{geofenceId} Get one geofence's details · Gets a single geofence #
Ask an LLM
“What is the shape and definition of a specific geofence?”
“Can I fetch a single geofence by its ID?”
Tell an agent
Get geofence {geofenceId}.
Show the definition of geofence {geofenceId}.
PUT /geofences/v2/{geofenceId} Replace a geofence's definition · Updates a single geofence #
Ask an LLM
“Can I change an existing geofence's shape or name?”
“Do I have to send every geofence property when updating one?”
Tell an agent
Update geofence {geofenceId} with a new definition.
Replace geofence {geofenceId}, forcing the change with {force}.
DELETE /geofences/v2/{geofenceId} Delete one geofence · Deletes a geofence #
Ask an LLM
“Can I remove a single geofence and keep the others?”
“What deletes one geofence by ID?”
Tell an agent destructive · confirm first
Delete geofence {geofenceId}.
Remove the single geofence {geofenceId}.
POST /geofences/v2/{geofenceId}/poiTraining Train a POI geofence from device telemetry · Trains a POI geofence #
Ask an LLM
“How do I define a POI geofence boundary from radio measurements?”
“Can I train an indoor POI geofence using a device's ingested data?”
Tell an agent
Train POI geofence {geofenceId} from device telemetry.
Run POI training on geofence {geofenceId}.
POST /geofences/v2/trainingTest Test whether POI geofence training will work · Checks if a POI geofence training is possible with the given parameters #
Ask an LLM
“Can I check if a POI geofence can be trained before actually training it?”
“Is my telemetry sample good enough to train a POI geofence?”
Tell an agent
Check whether a POI geofence training is possible with this data sample.
Dry-run POI geofence training on this telemetry.

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

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-geofences-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.

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

OpenAPI Specification

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