Rensei docs
API ReferenceWorker Protocol

Refresh issue lock TTL

Refresh issue lock TTL - Rensei REST API operation reference.

POST
/api/sessions/{id}/lock-refresh

Authorization

headerAuthorizationBearer <JWT>

Short-lived worker runtime JWT minted by the platform. Claims bind the worker, project, organization, registration, and scopes.

Path Parameters

id*string

Request Body

application/json
  1. body
workerId*string
issueId*string
ackedInject?string

Delivery id the runtime has applied. Exact replay is accepted; unknown, non-in-flight, or dead-lettered ids return 409.

deadLetteredInjects?array<>

Terminal consumer refusals. These are failure evidence, never acknowledgements, and are replayed until a 2xx response.

Itemsitems <= 128
sessionClass?string

Runtime session class, such as interactive; retained for backward-compatible heartbeat context.

Response Body

Settlement accepted and lock refresh attempted. Applied/dead-letter reports settle even when refreshed is false.

application/json
  1. response
refreshed*boolean
stop?boolean

Present when the shared session status is terminal and the runtime must stop.

inject?
Example Request
curl -X POST 'https://app.rensei.ai/api/sessions/string/lock-refresh' \  -H 'Content-Type: application/json' \  -d '{  "workerId": "string",  "issueId": "string"}'
Example Response
{  "refreshed": true,  "stop": true,  "inject": {    "deliveryId": "string",    "text": "string",    "kind": "memory",    "turnId": "string"  }}