Rensei docs
API ReferenceApprovals

Submit a typed answer on a human_query gate.

Validates the payload against the gate's declared form schema and records it via submitHumanQueryResponse; when the answer resolves the gate the suspended run resumes with the answer on the gate output. The answer 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.

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

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 human_query gate id.

Request Body

application/json
  1. body
answer?

Typed answer payload — validated against the gate form schema.

payload?

Alias for answer (either key carries the payload).

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.

Lengthlength <= 4000

Response Body

Answer recorded; includes resolution state and any workflow resume.

application/json
  1. response

The submitHumanQueryResponse result, plus an optional workflowResume block.

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

Create an approval gate for the authenticated organization.

Create an approval gate for the authenticated organization. - Rensei REST API operation reference.

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.