git.ssh-keys.listList your registered SSH keys
GET /git/api/ssh-keysIAM git:ListAccessTokensRead
Guarded by git:ListAccessTokens rather than a key-specific read action — the git descriptor has no ListSshKeys.
Request syntax
GET /git/api/ssh-keysResponse
200 with your keys: id, name, publicKey, fingerprint, lastUsedAt and createdAt.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Fields of data
[].idAlwaysstring
The key id[].orgIdAlwaysstring
The organization[].iamUserIdAlwaysstring
The IAM user it identifies[].nameAlwaysstring
Its name[].publicKeyAlwaysstring
The public key, as registered[].fingerprintAlwaysstring
Its SHA256 fingerprint[].lastUsedAtAlwaysstring, may be null
When it was last used (ISO 8601); null if never[].createdAtAlwaysstring
When it was registered (ISO 8601)
Checked against the handlers: every route test validates their answers against this schema.
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 git:ListAccessTokens 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 git ssh-keys listcurl -X GET "https://console.platform-development.deutschecloud.app/git/api/ssh-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_git_ssh-keys_list.