List operation approvals
GET/v1/operation-approvals
The operation approvals a destructive MCP tool asked for, newest first, page-based. Only the caller's own approvals — the person behind the token — in the token's organization and the call's workspace. Requires reach — any inbox/… scope or a bare all — but no specific resource scope: the data is the person's own. A token with no reach gets 403 INSUFFICIENT_SCOPE with details.required: ["inbox/all"]; only /v1/me answers any valid token. A token without a person has none. The approval link, its token and the stored card are never returned.
Request
Responses
- 200
- 400
- 401
- 403
Page of approvals.
A query parameter is invalid.
Authentication failed (missing or invalid JWT).
Authenticated but the scope is insufficient or the resource is out of reach. On INSUFFICIENT_SCOPE, error.details.required is the one minimal set of scopes that, added to the token's, would let the request through: the resource scope (inbox/<resource>, or inbox/all outside the catalogue) when the token does not reach the resource, then the bare verb when a non-read lacks it. Never all, never a list of alternatives.