Executions
Stream an execution
Re-attach to a running execution (SSE).
Events: status (first, then on change), progress (one per interior step record of the tasks named in task, polled every 250 ms), done (terminal, or the run paused for the user, or reattach: true after 5 min), error (the run vanished mid-stream, e.g. deleted: one event, then the stream closes). A : ping comment every 15 s. A re-attach replays the progress records. Interior records exist for runs started with progress watching (async, MCP, Studio, scheduler runs); a plain synchronous REST run writes none and streams status only.
Authorizations
Authorization: Bearer ozk_…. ozk_ platform API key (Authorization: Bearer ozk_…)Path parameters
exec-…)Query parameters
Maximum array length: 4
Response
Server-sent events
text/event-stream
invalid_task — more than 4 ids, or an id with other than letters, digits, . : _ -
application/json
unauthorized — missing, invalid or revoked ozk_ key
application/json
execution_not_found — no execution with that id for this key (a foreign id answers the same); not_found — no route for this method on this path: every other method answers it
application/json
execution_finished — the run is already terminal, nothing to steer or attach to
application/json
too_many_streams — a run takes at most 5 live streams at once; close one
application/json
upstream_error — a store failed; no detail is returned, retry shortly
application/json