Creates a new device group within the enterprise. Device groups organize devices into logical collections for policy assignment, app deployment, Blueprint application, and bulk command targeting. Groups can be nested — pass a parent group ID to create a subgroup within an existing group hierarchy.

Request body fields

name (required) — Display name for the new group parent (optional) — UUID of the parent group; omit to create a top-level group device_ids (optional) — Array of device UUIDs to add to the group at creation time

Common Use Cases

Setting up a new group before provisioning a batch of devices into it Creating subgroups to represent locations, departments, or device roles within a larger fleet segment Programmatically building out a group hierarchy as part of an onboarding or deployment Workflow

Best Practices

Group names should be descriptive and consistent with your naming convention — they appear throughout the Console and API responses You can add devices at creation via device_ids, or add them later using the update endpoint Store the id from the 201 response immediately — it's required for all subsequent group operations (policy assignment, commands, Blueprint targeting, etc.) Use GET /enterprise/{enterprise_id}/devicegroup/ first to confirm the group doesn't already exist before creating a duplicate