Legacy endpoint. Android only. Geofence configuration is now managed through blueprints. Use the blueprints endpoints (/api/v2/blueprints/) to create and manage geofences going forward.
Returns a paginated list of all geofences defined within the enterprise.Use this endpoint to audit existing legacy geofence definitions — their coordinates, radii, and configured device actions — before migrating configurations to blueprints.
About List Geofences (Legacy)
A geofence in Esper defines a geographic boundary — specified by latitude, longitude, and a radius — that triggers device actions (such as lockdown or beep) when a device crosses it. This endpoint belongs to the original standalone geofence API, which has been superseded by geofence configuration within blueprints. New integrations should use /api/v2/blueprints/ rather than this legacy path.
- Mock serverhttps://api.esper.io/_mock/openapi/v0/enterprise/{enterprise_id}/geofence/
- https://develop-api.esper.cloud/apihttps://develop-api.esper.cloud/api/v0/enterprise/{enterprise_id}/geofence/
curl -i -X GET \
'https://api.esper.io/_mock/openapi/v0/enterprise/{enterprise_id}/geofence/?search=string&limit=0&offset=0' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'{ "count": 0, "next": "string", "previous": "string", "results": [ { … } ] }