iam.users.cli-access

A member's CLI devices (Touch ID keys) and their CLI sessions in this organization

GET /iam/api/users/{id}/cliIAM iam:ListUserSessionsRead

Each device says whether this organization blocked it.

Request syntax

GET /iam/api/users/{id}/cli

Path parameters

  • idRequired

    string

    Constraints: uuid

Response

200 with `data`: `deviceKeys` (each live device: id, name, keyType, enrolledVia, createdAt, lastUsedAt, blocked — whether this organization blocked it) and `sessions` (each live CLI session in this organization: id, clientName, signInMethod, signInVerified, deviceKeyId, createdAt, expiresAt, lastUsedAt, lastIp). 404 when the user is not of this organization or is not a person (a service user has no CLI devices).

A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.

Errors

  • 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
  • 401No credentials, or an access key that is unknown, revoked or expired.
  • 403The caller's policies do not allow iam:ListUserSessions on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
  • 404The resource does not exist in your organization.

Examples

The required parameters only, with example values. Replace id and the other placeholders with your own.

dcloud iam users cli-access id

Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_iam_users_cli-access.