Skip to main content
POST
Search Approval Requests

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-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.

Authorizations

Authorization
string
header
required

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

Body

application/json
teamId
string

The ID of the team. Required.

resourceType
enum<string> | null

Filter by resource type (allocation or workflow run).

Available options:
APPROVAL_REQUEST_RESOURCE_TYPE_UNSPECIFIED,
APPROVAL_REQUEST_RESOURCE_TYPE_ACCESS_ALLOCATION,
APPROVAL_REQUEST_RESOURCE_TYPE_WORKFLOW_RUN
results
enum<string>[]

Filter by result statuses (multiple allowed).

Available options:
APPROVAL_REQUEST_RESULT_UNSPECIFIED,
PENDING,
APPROVED,
DENIED,
TIMEDOUT,
CANCELED
createdAfter
string | null

Filter by requests created after this timestamp (RFC3339 format).

createdBefore
string | null

Filter by requests created before this timestamp (RFC3339 format).

pageSize
integer<int32> | null

Maximum number of results to return. Default is 1000, maximum is 5000.

pageToken
string | null

Token for pagination. Leave empty for the first request.

Response

200 - application/json

Success

data
ApprovalRequest · object[]

A runtime approval request tracking the approval workflow for an access request or workflow run.

nextPageToken
string | null

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