Stream task events (SSE)
Opens a Server-Sent Events (SSE) stream for real-time task status updates. The connection stays open until the task reaches a terminal state (completed, failed, or cancelled), then closes automatically.
Event types:
status— Task status change (pending → waiting → queued → running)progress— Real-time execution progress (step X/Y, current node)completed— Task completed with output datafailed— Task failed with error messagecancelled— Task was cancellederror— Server-side error fetching status
Example SSE stream:
event: status
data: {"task_id":"...","status":"running","timestamp":"..."}
event: progress
data: {"task_id":"...","progress":0.35,"current_node":"3","step_current":7,"step_total":20,"timestamp":"..."}
event: progress
data: {"task_id":"...","progress":1.0,"current_node":"3","step_current":20,"step_total":20,"timestamp":"..."}
event: completed
data: {"task_id":"...","status":"completed","output":{...}}
Recommended over polling GET /r/tasks/ — lower latency, fewer requests.
Accepts JWT Bearer, sk- integration credential, or dk- device credential.
Documentation Index
Fetch the complete documentation index at: https://docs.cyberun.cloud/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
User session JWT (Bearer ). Must be paired with the X-Team-ID
request header on team-scoped endpoints so the server knows which
team's resources to operate on.
Headers
UUID of the team to scope the request to. Used by dual-auth endpoints (runtime + scoped management):
- JWT callers MUST send it — a user may belong to multiple teams and the runtime cannot otherwise know which one to operate on. Missing header → 400.
- Credential callers (
sk-,dk-) can omit it because the team is derived from the credential row itself. Any value sent is ignored.
"019abc12-4567-7890-abcd-ef1234567891"
Path Parameters
UUID of the task.
"019abc12-9012-7890-abcd-ef1234567896"
Response
SSE event stream
Server-Sent Events stream with task status updates
