---
title: "Get device group information"
method: GET
path: "/enterprise/{enterprise_id}/devicegroup/{group_id}/"
tags: ["esper_cloud_api_Device Group"]
---

# Get device group information

`GET /enterprise/{enterprise_id}/devicegroup/{group_id}/`

Retrieves full details for a single device group by its UUID.

Use this endpoint to fetch group metadata — including name, device count, child group count, hierarchy path, and associated blueprint — when you have a specific group_id and need its current state rather than a paginated list.
About Get Device Group Information
Device groups in Esper are hierarchical collections of devices used to organize and apply policies at scale. Each group can have a parent group, child groups, and an associated blueprint that defines the configuration applied to devices in that group. This endpoint returns a snapshot of a single group's metadata and is commonly used to validate group structure before performing bulk operations or blueprint assignments. To retrieve a group_id, use the List Device Groups endpoint first.

Key Fields

id — The group's UUID; use this as group_id in subsequent group-scoped requests
path — The full hierarchy path of the group within the enterprise's group tree
parent — URL reference to the parent group, if the group is nested
device_count — Number of devices directly in this group
children_count — Number of child groups nested under this group
blueprint — URL reference to the blueprint currently associated with this group

**Common Use Cases**

Confirm a group exists and retrieve its metadata before applying a blueprint or running a pipeline
Inspect a group's position in the hierarchy (path, parent) when managing nested group structures
Verify device_count before initiating bulk device operations against a group

**Best Practices**

Use List Device Groups to discover group_id values; avoid hardcoding UUIDs across environments
Check children_count before deleting a group — child groups must be removed first, and groups containing devices cannot be deleted until devices are moved or removed
Cache group metadata conservatively; group structure can change as devices are enrolled or moved

**Workflow**

1. Call List Device Groups (GET /enterprise/{enterprise_id}/devicegroup/) to find the target group and retrieve its group_id
2. Call this endpoint with the group_id to fetch full group details
3. Use the returned blueprint, path, and device_count to inform downstream operations such as blueprint updates, pipeline targeting, or group deletion

## Path parameters

- `group_id` string, uuid, required
- `enterprise_id` string, required

## Response `200`

successful operation

- EsperCloudApiDeviceGroup
  - `id` string, uuid — Group id
  - `name` string, required — Group name
  - `created_on` string, date-time — Date and time of when the group was created
  - `enterprise` string, url — Enterprise url
  - `parent` string, url — Parent group url
  - `device_count` integer — Count of devices in the group
  - `path` string — Path of the group
  - `children_count` integer — Count of child groups
  - `thumbnail` string, uuid — thumbnail associated with the group
  - `blueprint` string, uuid — Blueprint associated with the group.

## 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)