Skip to main content
GET
List Approval Delegations

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.

Query Parameters

delegatorUserId
string

Optional user ID to list delegations for a specific user.

pageSize
integer<int32>

Maximum number of results to return.

pageToken
string

Token for pagination. Leave empty for the first request.

Response

200 - application/json

Success

data
ApprovalDelegation · object[]
nextPageToken
string | null

Token for retrieving the next page of results. Empty if no more results.