AsyncAPI channel · fal · fal Event-Driven APIs

`{model_id}/requests/{request_id}/status/stream`

Name: {model_id}/requests/{request_id}/status/stream
Creator: fal

Server-Sent Events stream of queue status updates for a single submitted request. The connection remains open and emits one event per state change until the request reaches `COMPLETED`. Enable runner logs by adding `?logs=1` to the query string.

Open source AsyncAPI → All fal channels fal provider profile

Provider: fal AsyncAPI: v2.6.0 Spec: fal Event-Driven APIs Operations: 1 Messages: 3

Channel address

{model_id}/requests/{request_id}/status/stream

Parameters

model_id — Fully-qualified fal model identifier (e.g. `fal-ai/flux/dev`, `fal-ai/fast-sdxl`, `fal-ai/veo3`).
request_id — Queue request identifier returned by the original submit call.

Operations

subscribeQueueStatusStream

Subscribe to queue status events for a submitted request.

Messages

QueueStatusInQueue

Request has been received and persisted; waiting for an available runner.

Content-Type: application/json

QueueStatusInProgress

fal's dispatcher has routed the request to a runner.

Content-Type: application/json

QueueStatusCompleted

Result is stored and available for retrieval at `response_url` (or was POSTed to the configured webhook). This is the terminal event of the stream.

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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.