Rensei docs
API ReferenceSessions ( Public)

Get enriched session detail

Get enriched session detail - Rensei REST API operation reference.

GET
/api/public/sessions/{id}

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

Session id in ANY namespace: the canonical session id (what rensei session launch --json and rensei session list return), the 16-char public session hash, or the tracker AgentSession id. All three resolve to the same row inside the caller's organization.

Response Body

Enriched session detail with health diagnostics.

application/json
  1. response
[key: string]?any
Example Request
curl -X GET 'https://app.rensei.ai/api/public/sessions/string'
Example Response
{}

List enriched sessions for the authenticated org

Returns enriched session list with health summaries. Accepts an optional project scope via `?projectId=` or `?project=<slug>`. Falls back to parsing the `Referer` header for dashboard calls.

Send a prompt to a running session

Resolves a canonical session id or its public/tracker alias to one tenant-scoped session. Non-terminal input is durably queued on the session heartbeat rail; terminal retries use a durable admission receipt before reset/re-dispatch. A terminal generation is re-dispatched only when its original work type and provider-session resume identity are established from live or durable evidence; missing continuity returns a typed held 409 and creates no queue item. A caller-supplied idempotency key returns the exact current queued/in_flight/applied/dead_lettered active disposition or the original terminal receipt and conflicts on changed input. `in_flight` means claimed by the daemon but not acknowledged as applied; `delivered:true`/`deliveryTier:live` appears only after an exact applied ACK.