AsyncAPI channel · Agno · Agno AgentOS Run Streaming (HTTP + SSE)

`/workflows/{workflow_id}/runs`

Workflow run SSE stream. Opened via `POST /workflows/{workflow_id}/runs` with `stream=true` (default). Per Agno's docs, the first event on a workflow run is `event: RunStarted`, followed by per-step events, and a terminal completion or error event.

Open source AsyncAPI → All Agno channels Agno provider profile

Provider: Agno AsyncAPI: v2.6.0 Spec: Agno AgentOS Run Streaming (HTTP + SSE) Operations: 1 Messages: 5

Channel address

/workflows/{workflow_id}/runs

Parameters

workflow_id — The ID of the workflow to execute.

Operations

streamWorkflowRunEvents

Subscribe to streamed workflow run events (SSE).

Messages

RunStarted

First SSE event emitted when a run begins.

Content-Type: application/json

WorkflowStepEvent

Emitted as a workflow transitions between steps.

Content-Type: application/json

RunContent

A single SSE event carrying an incremental slice of model output. Many of these are emitted per request, in order.

Content-Type: application/json

RunCompleted

Terminal event marking successful completion of the run.

Content-Type: application/json

RunError

Terminal event emitted if the run fails.

Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.