Update Approval Delegation
Update an existing approval delegation rule.
Authentication and permissions
Token requirements: User-based token (OAuth) or Organization-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
- Manage a named user’s delegation: API keys must supply delegator_user_id when creating or listing delegations. Omitting it selects the current user. A team-restricted public key cannot authorize against a user.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The ID of the approval delegation rule to update.
Body
The delegates who can approve on behalf of the delegator.
The priority of the delegation rule (lower values are higher priority).
A description of the delegation rule.
A timestamp in RFC 3339 format (e.g., "2025-01-15T01:30:15Z").
"2025-01-15T01:30:15.000Z"
A timestamp in RFC 3339 format (e.g., "2025-01-15T01:30:15Z").
"2025-01-15T01:30:15.000Z"
Clears both active_from and active_until, making the rule permanent. Cannot be combined with active_from/active_until in the same request.
Response
Success
An approval delegation rule that allows a user to delegate their approval responsibilities.

