Skip to main content

Overview

FLUX 3 is a Black Forest Labs video model for generating short videos from text, animating one or two image frames, or extending an existing short video. Use this page when you are ready to call the API after trying FLUX 3 in the APIXO playground.

Endpoint and authentication

Base URL:
All requests require your APIXO API key:
Submit requests also require:

Copy-paste async quickstart

This minimal request submits a text-to-video task and returns a taskId.
Successful response:
Save the taskId; you need it to poll for the final result.

Poll for result

Processing response:
Success response:
Failed response:
Parse resultJson after state becomes success:

Request body

Text-to-video

Image-to-video

Image-to-video with start and end frames

Video extend

Parameters

string
default:"async"
Result delivery mode. Omit this field or use async for polling with statusTask, or use callback for webhook delivery.
string
Required when request_type is callback. Must be a public HTTPS URL that can receive the final task payload. See Webhooks.
object
required
FLUX 3 input parameters.

Mode options

Response format

Submit task response

POST /generateTask/flux-3 returns a task ID when the task is accepted:
integer
API status code. 200 means the task was accepted.
string
Human-readable status message.
string
Unique task identifier used with the status endpoint.

Status response fields

string
Unique task identifier.
string
Current task state: pending, processing, processing_r2, success, or failed.
string
JSON string containing generated video URLs in resultUrls. Present when state is success.
string
Machine-readable failure code. Present when state is failed.
string
Human-readable failure message. Present when state is failed.
integer
Task creation timestamp in Unix milliseconds.
integer
Task completion timestamp in Unix milliseconds. Present after completion.
integer
Processing duration in milliseconds when available.

Webhook callback mode

Use callback mode when your backend should receive the final result automatically instead of polling.
Callback delivery uses the same final payload shape as the status response. See Webhooks for delivery requirements and retry behavior.

Billing

FLUX 3 is billed per output second. The selected resolution determines the per-second unit price, and duration determines the billable seconds. text-to-video, image-to-video, start/end-frame image-to-video, and video-extend use the same resolution-based pricing. Formula:
Audio generation with sound: true does not add a separate charge. For the latest published pricing, see Pricing.

Latency and polling

Actual latency may vary by prompt complexity, selected mode, media accessibility, duration, resolution, and current queue load.
For production video workloads, use callback mode to avoid frequent polling while generation is still running.
For image-to-video, use image_urls with either 1 or 2 URLs. Two URLs represent the start and end frames in order. For video-extend, use one public MP4 URL. Keep the source file under 50 MB and at or below 15 seconds.

Errors and troubleshooting

HTTP errors

Validation notes

See Error Codes for the full error reference.