list_statements with
approver_id set to your own id to find what awaits you, then call this tool
with those ids, at most 50 per call. Approving takes no write permission: you
approve as yourself, on the statements you can see where you are one of the
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. A stage completed by your approval moves the
workflow on, and Qobra notifies the approvers whose turn comes, as in the web
app. There is no rejection: an approval is the only decision a stage takes.
Once no mandatory stage awaits approval, pay the statement with
update_statements_status.
The whole call is refused before anything is approved when one id names no
statement you can see.
Available only where the Qobra write tools beta is enabled and 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
string[]
required
Ids of the statements to approve — list_statements with
approver_id set to
your own id lists those awaiting you. At most 50 per call.integer
The 1-based position of one stage to approve, as get_statement shows it
under validation_workflow, with a single statement id. Omit it to approve
the stage awaiting you on each statement: your mandatory one first, else
your first optional one.
Example
Response
Body
Body
object[]
One row per statement, in the order first sent: an id sent twice is approved
and reported once.