list_statements with
approver_id set to your own id to find what awaits you, then call this tool
with those ids (the id of the statement rows, not user ids), at most 50 per
call. Approving needs no write permission: you approve as yourself, on the
statements you can see where you are one of a stage’s approvers.
Each statement sent gets one row:
approved: your approval is recorded on one stage.skipped, with the reason inreason: you are not one of its approvers, your stage waits on an earlier mandatory stage, your stages are already complete, it is already paid, no validation is requested on it, or it changed while the call ran.failedon Qobra’s side, in which case the approval may be recorded.reasonsays what to do.
warning says so, and another call approves it. To
approve a specific stage, pass its stage_position with a single statement id.
An approval cannot be undone and there is no rejection: an approval is the
only decision a stage takes. A stage your approval completes moves the workflow
on, and Qobra notifies the approvers whose turn comes, as in the web app.
Once no mandatory stage awaits approval, pay the statement with
update_statements_status.
The whole call is refused before anything is approved when an id names no
statement you can see.
Available only where the validation workflow is switched on. Every approval in
the live environment is recorded in the audit trail as the Qobra MCP agent.
Parameters
Body
Body
The
id of rows of list_statements, not user ids: list_statements with
approver_id set to your own id lists those awaiting you. At most 50.