Skip to main content
get/workflow/{workflow_run_id}/events
Request example
Response
get/workflow/{workflow_run_id}/events

Authorization

Authorizationstringheaderrequired#

Every request authenticates with an API key: Authorization: Bearer {API_KEY}. App endpoints take an app API key; knowledge endpoints take a knowledge base API key (Get Started).

Keep keys server-side; never embed them in client code. Requests with a missing or invalid key fail with HTTP 401 (unauthorized).

Path parameters

workflow_run_idstringrequired#
Workflow run ID whose event stream to resume, from the response or streaming events of Run Workflow.

Query parameters

userstringrequired#
End-user identifier, defined by your app and unique within it. Must match the user that started the run. See End User Identity.
include_state_snapshotboolean#
When true, replay from the persisted state snapshot to include a status summary of already-executed nodes before streaming new events.

Default: false

continue_on_pauseboolean#
Set to true to keep the stream open across multiple workflow_paused events (useful when the workflow has more than one Human Input node in sequence). Default closes the stream after the first pause.

Default: false

Responses

text/event-stream
Server-Sent Events stream. It opens with a bare event: ping frame (keep-alive; more arrive roughly every 10 seconds); every other event is delivered as data: {JSON}\n\n. Event payloads follow the same schemas as the original streaming response.