Record an approval or rejection

Records one approver's decision on one stage.

Authority is derived, never trusted. The approver must already be on the chain at the active stage. Anyone else is refused with APPROVER_NOT_IN_CHAIN, whatever the caller claims. An approver who is no longer active cannot decide either: they get USER_NOT_ACTIVE, and the resolve endpoint shows each approver's user_status, so a connector can see it before trying.

A member of a group or user group on the active stage counts as an approver on it: name the member as approver, not the group. List them with GET /ext/groups/{group_id}/members.

The API key identifies your organization, not a person, so this check confirms that the person named may decide, not that they did. Your system must authenticate its own user and name only that user.

Take approver and stage_index from the resolve endpoint.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The request's request_id (REQ-1042) or its id — both are accepted.

Body Params
integer
required
≥ 1

1-based, from the resolve response.

string
enum
required
Allowed:
string
required
^[a-fA-F0-9]{24}$

Zluri user id. Must be on the chain at this stage.

string
length ≤ 400

Recorded against the decision itself.

Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json