iam.access-keys.listList access keys, optionally for one IAM user
GET /iam/api/access-keysIAM iam:ListAccessKeysRead
Request syntax
GET /iam/api/access-keysQuery parameters
iamUserIdOptionalstring
Only the keys of this IAM user; omitted: every key of the organization
Constraints: uuid
Response
200 with the keys, newest first: id, accessKeyId, status, iamUserId, lastUsedAt, expiresAt, createdAt, description, scopePolicy and s3 (whether the key also signs S3 requests). Never a secret.
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 listcurl -X GET "https://console.platform-development.deutschecloud.app/iam/api/access-keys" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"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_list.