⚠️ Legacy endpoint. Geofence configuration is now managed through blueprints. Use the blueprints endpoints (/api/v2/blueprints/) to create and manage geofences going forward.
Retrieves the full details of a single geofence by its UUID.Returns the complete Geofence object including coordinates, radius, configured device actions, device count, and audit timestamps; useful during migration to read the exact parameters of a legacy geofence before recreating it in a blueprint.
About Get Geofence (Legacy)
This endpoint fetches a single legacy geofence record by geofence_id. Geofences in this legacy system were standalone entities associated with an enterprise and optionally applied to individual devices. The current approach embeds geofence definitions within blueprints via /api/v2/blueprints/, enabling consistent application across device groups rather than per-device assignment.
- Mock serverhttps://api.esper.io/_mock/openapi/v0/enterprise/{enterprise_id}/geofence/{geofence_id}/
- https://develop-api.esper.cloud/apihttps://develop-api.esper.cloud/api/v0/enterprise/{enterprise_id}/geofence/{geofence_id}/
curl -i -X GET \
'https://api.esper.io/_mock/openapi/v0/enterprise/{enterprise_id}/geofence/{geofence_id}/' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'successful operation
The unit in which the radius is taken, eg - kilometers, meters etc
The actions to be performed on the device
Date and time of when the geofence was created
{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "description": "string", "enterprise": "796caaf9-a7de-4817-9ffa-39d04bf83de9", "latitude": "string", "longitude": "string", "radius": 0, "radius_unit": "KILOMETERS", "device_actions": [ "LOCK_DOWN" ], "device_count": 0, "created_by": "string", "created_on": "2019-08-24T14:15:22Z", "updated_on": "2019-08-24T14:15:22Z" }