Rensei docs
API ReferenceApprovals

Submit an approve / reject / escalate decision on an approval gate.

The decision actor identity and role are derived from the authenticated context, never trusted from the request body (SR 11-7). API-key callers without a user identity are rejected 403; a claimed actorRole that does not match the caller's real org role is rejected 403. When the decision resolves the gate, an escalate-to-live-session workflow gate is resumed with the server-derived approver as driver.

POST
/api/approval-gates/{id}/decide

Authorization

headerAuthorizationBearer <rsk_live_*>

Rensei API key presented as Authorization: Bearer rsk_live_. Required API-key scopes are recorded per operation in x-rensei-required-scopes.

Path Parameters

id*string

The approval gate id.

Request Body

application/json
  1. body
decision*string

The decision to record.

Value in"approved""rejected""escalated"
actorType?string

Defaults to human for session / user-token callers.

Value in"human""agent"
actorRole?string

Optional; must match the caller's authenticated org role if supplied.

reason?string

Optional free-text rationale.

Response Body

Decision recorded; includes resolution state and any workflow resume.

application/json
  1. response

The submitDecision result, plus an optional workflowResume block.

resolved*boolean
[key: string]?unknown
Example Request
curl -X POST 'https://app.rensei.ai/api/approval-gates/string/decide' \  -H 'Content-Type: application/json' \  -d '{  "decision": "approved"}'
Example Response
{  "resolved": true,  "property1": null,  "property2": null}