Skip to main content

Why Use the Async Queue

The synchronous endpoints (/ai/images/generate, /ai/videos/generate) block until the result is ready. For video generation, this can be 1-10+ minutes. The async queue returns immediately with generation IDs so you can:
  • Run many generations in parallel (up to 4 per request, no limit on total queued)
  • Avoid long-lived HTTP connections
  • Build progress-tracking UIs
  • Query completed generations and their output URLs at any time

Workflow

Generations persist after reaching a terminal state (succeeded, failed, or cancelled), so you can retrieve results at any time. A Server-Sent Events stream at GET /api/events can also deliver completion notifications with the output file URL. See Completion Events.

Enqueue

Submit an async image or video generation job.

Required Parameters

Additional Parameters

All other parameters (e.g. prompt, multi_prompt, input_image, input_video, aspect_ratio, duration, seed, generate_audio, response_format) are passed through to the model. Consult the model’s request_schema via GET /api/ai/models/:id for supported parameters and their constraints.

Response

Validation

The API validates at enqueue time that:
  • The model exists and has image or video output capability
  • num_generations is 1-4
  • The user is authenticated with sufficient credits
Model-specific parameter validation (prompt content, duration ranges, aspect ratio values) happens when the generation runs, not at enqueue time. If a parameter is invalid, the generation transitions to failed status with an error_message. To validate parameters and get immediate error feedback, use /ai/images/generate or /ai/videos/generate instead.

List Generations

Lists generations for the authenticated user’s namespace. By default, only active generations (queued or processing) are returned. Pass an explicit status filter to include terminal states.

Query Parameters

Response

Any additional parameters from the original enqueue request (e.g. seed, aspect_ratio, duration, input_image) are included in the response alongside the fields above.

Polling Strategy

  • Image generation (FLUX, etc.): typically completes in 5-30 seconds. Poll every 2-5 seconds.
  • Video generation (Kling, etc.): typically takes 1-5 minutes. Poll every 10-30 seconds.
Poll until every generation’s status is a terminal value (succeeded, failed, or cancelled), or until count reaches 0 when using the default active-only filter.

Get Generation

Retrieves metadata for a single generation. Includes result_url when the generation has succeeded and error_message when it has failed.

Path Parameters

Response (in progress)

Response (succeeded)

Response (failed)

Response (not found)

Returns 404 when the generation ID does not exist:

Cancel Generation

Cancels a queued or in-progress generation.

Path Parameters

Response (success)

Response (not found)

Returns 404 when the generation ID does not exist:
You can only cancel generations that are still active (queued or processing). Cancelling a generation that has already reached a terminal state (succeeded, failed, or cancelled) has no effect.

Completion Events

Server-Sent Events stream that emits media_generation_completed events when generations reach a terminal state.

Connect

Response is Content-Type: text/event-stream. The server sends : keep-alive\n\n every 15 seconds when idle. Events are broadcast to currently-connected subscribers with no buffering. Anything that fires before you connect is lost. Subscribe before calling POST /ai/queue to avoid missing events.

Event: media_generation_completed

Fires once per generation on terminal state. Success wire format:
Failure:

Fields

Other events on this stream

GET /api/events is a user-scoped stream that may carry unrelated event types (e.g. deployment events). Filter on the event: line and ignore anything other than media_generation_completed.

Example

Terminal states without events

media_generation_completed does not fire for cancelled generations (you called DELETE /ai/queue/:id). You can still retrieve the final status of any generation via GET /ai/queue/:id.

Examples

Batch image generation with polling

Async video generation

Poll a single generation by ID

End-to-end: enqueue, wait for SSE, download

Python

Errors