Approve an action
Approves and replays the exact frozen action, once: approving it again answers 422. An action raised outside a chat (over the API, or by a script run) runs now, and the approval comes back executed (with result) or failed (with error). One raised in a chat comes back approved: the agent runs it on its next turn, so poll the approval for the outcome. The Crevio agent can never approve: its calls are refused with 403 approval_requires_user. A user who may not answer the approval gets 403 permission_denied: an admin answers any approval, a teammate the ones raised in a chat they can see, and a card fill only an admin. An approval nobody answers outside a chat is denied after 7 days.
Authorizations
API key in the format: Bearer {api_token}
Headers
Makes this write safe to retry: a repeat with the same key replays the first response instead of creating a second resource. Scoped to the account, remembered for 24 hours; reusing a key with a different payload is an error.
255Path Parameters
Approval id (apr_...)
Response
Success
approval pending_approval waits for a person. It ends executed (see result), failed (see error) or denied (see reason).
draft, pending_approval, approved, executed, failed, denied pipedream, composio, rest, mcp, native, saved_tool, vault, elicitation 
