List Approver Options
GET/api/approval-policies/approver-options
Search the users and roles that can be listed as approvers on a policy step. Returns up to 100 users (matched on name or email) followed by every matching role with its current member count.
purchase-orders:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token with the purchase-orders scope (read for GET, write for POST/PUT/DELETE).
Requires permission: approval_policies.view
Response fields: type (user | role), id, name; users add email, roles add member_count. Use the type + id pair in tiers.*.steps.*.approvers when saving a policy.
Request
Responses
- 200
- 401
- 403
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.