Preview — pending review
This reference is generated from the platform API contract and is still under review. Operations, fields, and descriptions can change before publication.
Revoke a role binding from a service account
Revokes a single role binding from the service account (UI "Remove" on the detail Bindings tab). The grant is
deleted and the revoked access stops taking effect immediately (an iam.assignment.changed event converges the
enforcement caches). A terminal SUCCEEDED audit Operation is recorded and the account's bindingCount counter
updates immediately.
Validation: the account must exist and be visible in the scope, and the binding id must be one the account
holds in the active tenant (else 404 NOT_FOUND); caller must hold a role-management role (owner|admin) else 403
FORBIDDEN.
Async & state: synchronous command — 204 No Content. Naturally idempotent: a repeat delete of an
already-removed binding is a 404.
Errors: 401 unauthenticated; 403 lacks role-management permission; 404 unknown account or binding; 500
revoke failure.
bearerTokenAuthorizationBearer <token>An API token (pc_live_…) or a service-account key (sak_live_…), created in Identity & Access Management and sent as Authorization: Bearer <token>. Requests are rate limited per credential and per tenant: every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, and a refused request gets 429 RATE_LIMITED with Retry-After.
scopeId*stringOpaque ownership+authorization scope resolving to tenant + subscription + project.
serviceAccountId*stringService account identifier.
bindingId*stringRole-binding identifier.
Binding revoked.
curl -X DELETE "https://example.com/scopes/string/iam/service-accounts/string/bindings/string"