Record Reviewer Decision

POST /v2/workflow/steps/recordReviewerDecision

Record Reviewer Decision

cURL

curl --request POST \
  --url https://api.velt.dev/v2/workflow/steps/recordReviewerDecision \
  --header 'Content-Type: application/json' \
  --header 'x-velt-api-key: <x-velt-api-key>' \
  --header 'x-velt-auth-token: <x-velt-auth-token>' \
  --data '
{
  "data": {
    "executionId": "<string>",
    "stepId": "<string>",
    "reviewerId": "<string>",
    "decision": "<string>",
    "reason": "<string>"
  }
}
'

{
  "result": {
    "recorded": true,
    "aggregatorStatus": "resolved",
    "resumeScheduled": true
  }
}

Use this API to record a single reviewer’s decision against a human step. When all mandatory reviewers approve (or any reviewer rejects), the step’s aggregator transitions terminal and the step resumes.

Endpoint

POST https://api.velt.dev/v2/workflow/steps/recordReviewerDecision

Headers

x-velt-api-key · string · required

Your API key.

x-velt-auth-token · string · required

Your Auth Token.

Body

Params

data · object · required

Show properties

executionId · string · required

The execution containing the step.

stepId · string · required

Must reference a human step in waiting.

reviewerId · string · required

Must match a userId declared on the node’s reviewers[].

decision · string · required

approve / reject.

reason · string

≤ 2000 chars.

Example Requests

Approve as a reviewer

{
  "data": {
    "executionId": "exec_1777374504255_xzy43k9q",
    "stepId": "step_agent-draft_..._lwofay__to__human-legal",
    "reviewerId": "u_legal_01",
    "decision": "approve",
    "reason": "looks good"
  }
}

Reject as a reviewer

{
  "data": {
    "executionId": "exec_1777374504255_xzy43k9q",
    "stepId": "step_agent-draft_..._lwofay__to__human-legal",
    "reviewerId": "u_legal_01",
    "decision": "reject",
    "reason": "compliance issue on line 3"
  }
}

Response

Success Response

{
  "result": {
    "recorded": true,
    "aggregatorStatus": "resolved",
    "resumeScheduled": true
  }
}

recorded: false only on idempotent replay. aggregatorStatus: pending / resolved / rejected. resumeScheduled: true when this decision triggered the resume task.

Failure Response

{
  "error": {
    "message": "ERROR_MESSAGE",
    "status": "FAILED_PRECONDITION"
  }
}

Errors:

Code	Cause
FAILED_PRECONDITION	Step is not in waiting, step is not a human node, or the step is the legacy comment-resolution variant (use the comment-reply flow instead).
NOT_FOUND	executionId or stepId does not exist.
INVALID_ARGUMENT	Schema validation (missing field, wrong type).

A reviewerId not listed on the node’s reviewers[] does not throw — the aggregator records the response as an unknown responder, and the response payload’s aggregatorStatus reflects whether quorum has shifted.

{
  "result": {
    "recorded": true,
    "aggregatorStatus": "resolved",
    "resumeScheduled": true
  }
}