Tools
approvals_decide
Record an approver's verdict on a pending request.
Record an approver’s verdict on a pending request. Only users the org’s rule names as approvers (with approval:decide) may call this — an agent acting for a non-approver is refused. Approving unblocks arming; rejecting sends the post back to its author with the optional comment explaining why.
Input
| Field | Type | Required | Description |
|---|---|---|---|
organization | string | no | Organization slug to act in (see organizations_list). Optional: API keys are bound to one organization; OAuth connections default to your active organization. |
request_id | string | yes | Approval request id |
verdict | "approved" | "rejected" | yes | The decision: approve or reject |
comment | string | no | Why — shown to the post’s author |
Result
JSON on success. A refusal comes back as an error prefixed with its code (NOT_FOUND, FORBIDDEN, TOO_MANY_REQUESTS, …) and a message written to be acted on — read it before retrying.
The same operation elsewhere
This tool and the REST operation approvalsDecide and the CLI command inklate approvals decide run the same guarded procedure the dashboard uses — same permissions, same validation, same tenant isolation.