---
title: "List Geofences in Enterprise"
method: GET
path: "/v0/enterprise/{enterprise_id}/geofence/"
tags: ["esper_cloud_api_Geofence"]
---

# List Geofences in Enterprise

`GET /v0/enterprise/{enterprise_id}/geofence/`

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

- `enterprise_id` string, uuid, required

## Query parameters

- `search` string
- `limit` integer
- `offset` integer

## Response `200`

successful operation

- object
  - `count` integer, required
  - `next` string, url, nullable
  - `previous` string, url, nullable
  - `results` EsperCloudApiGeofence[], required
    - `id` string, uuid — id of the geofence
    - `name` string, required — Name of the geofence
    - `description` string — A description about the geofence
    - `enterprise` string, uuid — id of the enterprise resource
    - `latitude` string, decimal, required — Latitude corresponding to the geofence
    - `longitude` string, decimal, required — Longitude corresponding to the geofence
    - `radius` integer — The radius within which the geofence should be applied
    - `radius_unit` 'KILOMETERS' | 'METERS' | 'MILES' — The unit in which the radius is taken, eg - kilometers, meters etc
    - `device_actions` string[] — The actions to be performed on the device
    - `device_count` integer — Number of devices
    - `created_by` string — The user who created the geofence
    - `created_on` string, date-time — Date and time of when the geofence was created
    - `updated_on` string, date-time — Date and time of when the geofence was updated

## Other responses

- `401` — Authorization information is missing or invalid.
- `404` — Not Found.
- `500` — Internal server error

---

[API](https://skmtc.net/esper/apis/esper-api-reference.md) · [All operations](https://skmtc.net/esper/apis/esper-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/esper/esper-api-reference/versions/e1f64cbb488e/schema)