iam.access-keys.legacy-limits

Legacy limited keys of the organization, with what each can do and the migration that would replace it (a dry run)

GET /iam/api/access-keys/legacy-limitsIAM iam:ListAccessKeysRead

Nothing changes. Platform-made purpose keys (Error Tracking tokens, cloud shell keys) keep their limits and are not listed.

Request syntax

GET /iam/api/access-keys/legacy-limits

Response

200; data is a list of { id, accessKeyId, description, status, lastUsedAt, createdAt, account, limit, works, replaced, proposal }. proposal (null when the key can do nothing: delete it) is { serviceAccountName, policyName, policyDocument }: a dedicated service account whose policy is the account’s policies narrowed by the key’s limit, never more.

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:ListAccessKeys 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 access-keys legacy-limits

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