Get a Operations for a device

Retrieves the Dispatch operations that have targeted a specific device, giving a device-centric view of Converge, install, and uninstall activity.

Use this endpoint when you already have a device_id and want to see which fleet-wide dispatch operations it was included in, rather than starting from the operation and looking up its devices. Returns the same OperationWithStats objects used elsewhere in the Operations API, each including the operation's type, current state, and aggregate device counts.

About Operations for a Device

Operations, also called Dispatch commands, are Esper's mechanism for issuing large fleet actions such as Converge and group-level app installs and uninstalls to many devices in a single request. Every operation that includes this device appears in this list, regardless of when it was created or how many other devices it targeted. This is the reverse lookup of GET /v0/operations/{operationsId}/devices/, which starts from the operation instead of the device.

Common Use Cases

Auditing every dispatch operation a device has participated in

Troubleshooting a device that appears out of sync by checking whether a recent Converge operation reached it

Confirming whether a device was included in a bulk install or uninstall operation

Best Practices

Cross-reference the operation IDs returned here with GET /v0/operations/{operationId}/ for full operation-level context, including overall success and failure counts

Check the most recent entries first when troubleshooting a device that just failed to Converge

Workflow

Identify the device_id from a device listing endpoint

Call this endpoint with that device_id to list the operations that targeted it

Use the returned operation id with GET /v0/operations/{operationsId}/devices/{deviceId}/ to see this device's specific status within that operation