Rensei docs

Stream best-effort live execution events for a workflow instance.

Stream best-effort live execution events for a workflow instance. - Rensei REST API operation reference.

GET
/api/workflows/{id}/instances/{instanceId}/stream

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
Length1 <= length
instanceId*string
Length1 <= length

Response Body

Live-only SSE. heartbeat data is {timestamp}; complete data is {status} where status is completed, failed, cancelled, or waiting; step_state data is the executor event object. Redis step events are best-effort and may be missed before connection or across reconnects. Live step and heartbeat frames may also be dropped when bounded Redis or HTTP backpressure buffers fill; terminal complete is prioritized and reconciled from durable instance state. No replay, Last-Event-ID, or total ordering is promised.

response?stringtext/event-stream

SSE-framed text. Event names are heartbeat, step_state, and complete.

Example Request
curl -X GET 'https://app.rensei.ai/api/workflows/string/instances/string/stream'
Example Response
"string"