Fetch all devices in an enterprise

⚠️ Android only. This endpoint applies exclusively to Android-managed devices enrolled in Esper. For other devices, use the other device management endpoints.

Lists all devices enrolled in an enterprise, with rich filtering options.

Returns a paginated collection of DeviceInfo records with filters for device name, group, IMEI, serial number, state, brand, GMS support, tags, blueprint assignment, and more. Default page size is 20.

About List Enterprise Devices

Devices in Esper represent Android endpoints enrolled under enterprise management. Each device record contains hardware identifiers (IMEI, serial), current state, group membership, blueprint assignment, and status metadata. The group filter traverses the full subtree — filtering by a parent group will include all devices in its subgroups. This endpoint is the primary entry point for fleet-wide device discovery and inventory.

Key Query Parameters

name — filter by device display name group — filter by group UUID; returns all devices in that group and all of its subgroups imei — filter by IMEI number serial — filter by device serial number state — filter by enrollment state (see DeviceStateEnum) brand — filter by device manufacturer/brand is_gms — filter for GMS (Google Mobile Services)-capable devices search — free-text search across device name, IMEI, and MAC address tags — partial text search across device tags assigned_blueprint_id — filter devices by their assigned blueprint UUID current_blueprint_id — filter devices by the blueprint currently applied current_blueprint_version_id — filter by the specific blueprint version currently applied limit — results per page (default: 20)

Common Use Cases

Enumerate all devices in a specific group (including subgroups) for bulk operations or reporting Search for a device by serial number or IMEI when responding to a field support request Filter by blueprint assignment to identify devices running a specific configuration or a stale blueprint version

Best Practices

Use the group filter to scope operations to a target group's subtree rather than processing the full enterprise list Combine search with state to quickly isolate enrolled-but-offline devices in large fleets Use assigned_blueprint_id vs. current_blueprint_id deliberately — a device may have a new blueprint assigned but not yet applied

Workflow

Call this endpoint with relevant filters (group, state, blueprint) to identify the target device set Collect device_id values from the paginated results Use individual device IDs for detail lookups, command dispatch, or app queries