List your operation approvals
GET/v1/operation_approvals
The approval-link approvals of the person the token belongs to, in the token’s organization, most recent first: each destructive MCP tool that waited for confirmation on the approval screen, with what happened next. Any token with a person reads its own approvals, with no resource scope; a token without a person gets an empty list. What each operation returned (result, error, an amount read from the record) comes back only when the token can read that approval’s resource and the person still holds a read permission on it; otherwise it is null with result_hidden: true. Read-only: nothing here approves, cancels or reopens an approval. title comes in the Accept-Language language (pt-BR by default).
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 429
- 500
Paginated list of approvals.
Request body failed validation.
Missing or invalid bearer token.
Token is valid but lacks permission for this operation. With code insufficient_scope, details.required carries the one minimal set of scopes that, added to details.granted, would let the request through: the resource scope (billing/{resource}, or billing/all off the catalogue) then the bare verb — e.g. ["billing/customers", "delete"].
Resource not found in the current organization.
Rate limit exceeded.
Unexpected server error.