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

AuthorizationBearer <token>

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

In: header

Path Parameters

id*string

The approval gate id.

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

curl -X POST "https://example.com/api/approval-gates/string/decide" \  -H "Content-Type: application/json" \  -d '{    "decision": "approved"  }'
{
  "resolved": true,
  "property1": null,
  "property2": null
}
Empty
Empty
Empty
Empty
Empty
Empty