This page documents the canonical HTTP contract for this endpoint.
Requires a user session and the account owner or an admin. The account must support send when a nonempty capabilities list is present; managed-fleet senders also require the actor’s current allocation and mailbox access. The path accepts the delegate’s user ID or exact email; the API resolves it within the current organization. Revocation marks active matching delegation records as revoked and returns the number changed.
Revocation affects future authorization. Existing tasks may already have sender bindings persisted.
Path parameters
sender_account_idrequiredstring
Sender account ID.
delegate_user_idrequiredstring
User ID or exact email of a user in the current organization whose active delegation should be revoked.
| Name | Type | Description |
|---|---|---|
| sender_account_idrequired | string | Sender account ID. |
| delegate_user_idrequired | string | User ID or exact email of a user in the current organization whose active delegation should be revoked. |
Errors
| Status | Meaning |
|---|---|
| 401 | Authentication failed or a user session is required. |
| 403 | Developer API keys are blocked; only the account owner or an admin user session can revoke delegation. |
| 404 | Sender account or delegate user not found in the current organization. |
| 409 | Sender account does not support the send scope required to manage delegation. |
