Returns paginated statistics on blueprint usage within a specific geofence — which blueprints are applied to devices inside that geofence and how many devices use each. Use it to understand how blueprint-driven configuration correlates with a location-based boundary.
Scoped to a single geofence_id; each result identifies a blueprint and the count of devices in that geofence currently using it.
About Geofences
A geofence is a virtual geographic boundary that can be tied to blueprint-based device configuration, so devices entering or leaving the boundary can be managed differently depending on which blueprint they're running. This endpoint gives visibility into that blueprint-to-geofence relationship.
Key Fields / Query Parameters
- geofence_id — path parameter identifying the geofence to report on
Common Use Cases
- Auditing which blueprint versions are in use across devices within a specific geofence
- Verifying blueprint rollout coverage for a location-restricted device population
- Mock serverhttps://api.esper.io/_mock/openapi/geofence/v1/geofences/{geofence_id}/blueprints
- https://develop-api.esper.cloud/apihttps://develop-api.esper.cloud/api/geofence/v1/geofences/{geofence_id}/blueprints
curl -i -X GET \
'https://api.esper.io/_mock/openapi/geofence/v1/geofences/f5316a75-f186-4769-970e-28d6a1a0e110/blueprints?offset=0&limit=10' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'X-Caller-Id: string' \
-H 'X-Esper-Tenant-Id: 497f6eca-6276-4993-bfeb-53cbbbba6f08'{ "content": { "next": "/v1/geofences/f5316a75-f186-4769-970e-28d6a1a0e110/blueprints?offset=10&limit=10", "previous": null, "results": [ … ] } }