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.
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
subscribe
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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.