ecr.auth.revoke-login-tokenRevoke one of your own login tokens; the registry refuses it at once
DELETE /ecr/api/login-tokens/{id}IAM ecr:GetAuthorizationTokenChanges state
Request syntax
DELETE /ecr/api/login-tokens/{id}Path parameters
idRequiredstring
Constraints: uuid
Response
200 with { id } of the revoked token. 404 when it is not one of your own live tokens.
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 ecr:GetAuthorizationToken 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 ecr auth revoke-login-token idcurl -X DELETE "https://console.platform-development.deutschecloud.app/ecr/api/login-tokens/id" \
-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_ecr_auth_revoke-login-token.