Returns a paginated list of devices and their current state relative to a specific geofence. Use it when you need the actual device records, not just aggregate counts.
Supports filtering by inside/outside status and by blueprint version ID, so you can drill into, for example, only the devices currently outside the boundary running a particular blueprint version.
About Geofences
A geofence is a virtual geographic boundary tied to device location tracking, and can be associated with blueprint-driven configuration so a device's blueprint version may factor into how it's managed inside vs. outside the fence. This endpoint exposes the per-device detail behind the aggregate device-summary statistics.
Key Fields / Query Parameters
- geofence_id — path parameter identifying the geofence
- inside/outside status — filters devices by whether they are currently within the geofence boundary
- blueprint version ID — filters devices by the blueprint version they're currently running
Common Use Cases
- Listing devices that have left a geofenced area for follow-up or remediation
- Cross-referencing which blueprint versions are running on devices inside vs. outside a boundary
Security
geofence_bearerAuth
- Mock serverhttps://api.esper.io/_mock/openapi/geofence/v1/geofences/{geofence_id}/devices
- https://develop-api.esper.cloud/apihttps://develop-api.esper.cloud/api/geofence/v1/geofences/{geofence_id}/devices
curl -i -X GET \
'https://api.esper.io/_mock/openapi/geofence/v1/geofences/f5316a75-f186-4769-970e-28d6a1a0e110/devices?offset=0&limit=10&inside=true&blueprint_id=550e8400-e29b-41d4-a716-446655440000&blueprint_version_number=1' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'X-Caller-Id: string' \
-H 'X-Esper-Tenant-Id: 497f6eca-6276-4993-bfeb-53cbbbba6f08'Response
{ "content": { "next": "/v1/geofences/f5316a75-f186-4769-970e-28d6a1a0e110/devices?offset=10&limit=10", "previous": null, "results": [ … ] } }