Revoke a principal
POST/api/v1/iam/principal-revocations
Revokes, for good, a principal the caller's IAM tokens or On-Behalf-Of assertions act for in the project. Work started for it (a generation, a session turn, a task dispatch, an orchestration run, a trigger firing) resolves no caller from then on: its next step, a resume included, fails WORK_AUTHORITY_MISSING. Revoking a principal already revoked is 204 too.
Request
Responses
- 204
- 400
- 401
- 403
- 413
- 429
- 500
- 502
- 4XX
The principal is revoked
Invalid request — a query parameter or body field the operation does not declare, or a value that fails validation
Unauthorized
Insufficient permissions
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Unexpected server error — INTERNAL_ERROR, with the raw message never forwarded
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there