---
title: "Get geofence information"
method: GET
path: "/v0/enterprise/{enterprise_id}/geofence/{geofence_id}/"
tags: ["esper_cloud_api_Geofence"]
---

# Get geofence information

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

⚠️ 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.

## Path parameters

- `geofence_id` string, uuid, required
- `enterprise_id` string, uuid, required

## Response `200`

successful operation

- EsperCloudApiGeofence
  - `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/revisions/e1f64cbb488e/schema)