List Geofences in Enterprise
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.
Path parameters
A UUID string identifying the enterprise.
Query parameters
A search term.
Number of results to return per page.
The initial index from which to return the results.
Response
successful operation