Skip to main content
POST
Create Approval Delegation

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.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access.
  • 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

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
delegates
ApprovalDelegate · object[]
required

The delegates who can approve on behalf of the delegator.

delegatorUserId
string | null

The ID of the user who is delegating their approvals. When omitted, defaults to the authenticated user.

priority
integer<int32>

The priority of the delegation rule (lower values are higher priority).

description
string

A description of the delegation rule.

activeFrom
string<date-time> | null

A timestamp in RFC 3339 format (e.g., "2025-01-15T01:30:15Z").

Example:

"2025-01-15T01:30:15.000Z"

activeUntil
string<date-time> | null

A timestamp in RFC 3339 format (e.g., "2025-01-15T01:30:15Z").

Example:

"2025-01-15T01:30:15.000Z"

Response

200 - application/json

Success

data
data · object

An approval delegation rule that allows a user to delegate their approval responsibilities.