Approve a task

post

https://api.qfp.quantnetwork.net/api/approvals/tasks/{taskId}/approve

Runs under a row lock on the owning request, so a request resolves
exactly once.

Checks, in order:

The task's approverIds contain the caller's sub (403); a task
with no approverIds never matches.
The caller is not the request's initiatedBy (403, four-eyes).
The task is PENDING (409).
No task at a lower step is still PENDING (409).

The task becomes APPROVED with actedBy the caller's sub; when
every task is, the request does too and the resolution is published
to policy.decided.

Recipes

Read approval tasks and submit a decision

Open Recipe

Responses

Language

Credentials

Bearer

JWT

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200The request with updated task states

403The caller's sub is not in the task's approverIds, or it matches the request's initiatedBy (four-eyes).

404No such resource in the caller's tenant. A resource that exists in another tenant is also reported here.

409The task is already acted on, or an earlier step is still pending