FLUX 3
Black Forest Labs' first video model — 20-second shots in 1080p with native audio.
Capabilities
Best for
- •Cinematic text-to-video shots
- •Short social and ad clips
- •Consistent multi-shot sequences
- •Look-dev and style exploration
Not for
- •Frame-exact rotoscoping
- •Feature-length renders
- •Pixel-perfect compositing
- •Precise on-screen text
Authentication
api key header
The Pika API uses API keys to authenticate requests. Send your key in the X-API-Key header. Your API key is a secret. Don't expose it in browsers or other client-side code. Instead, call the API from your server. The signed-in playground uses a portal session and never sends your API key.
X-API-Key: YOUR_API_KEY
Endpoint
asynchronous · poll for the result
REST Setup
plain HTTPS
Video generation runs through the REST endpoint shown above. The API is plain JSON over HTTPS, so any HTTP client works. No provider-specific SDK is required.
Generate
POST /v1/media/black-forest-labs/flux-3-video/text-to-video
Request
curl -X POST https://api.dev.pika.art/v1/media/black-forest-labs/flux-3-video/text-to-video \-H "X-API-Key: YOUR_API_KEY" \-H "Content-Type: application/json" \-d '{"prompt": "Shot on 35mm film, muted desaturated pastel grade with soft grain and gentle halation, exactly like a 1990s European fashion editorial. Tight side-on view of a vintage sage-green sedan idling on a Paris street: a woman's arm in a long dusty-pink satin opera glove is draped out of the open rear window, hand hanging loose and relaxed over the chrome window trim, fingers slightly parted. A cream shaggy fur coat is just visible inside the dark car interior behind the glass. The road and blurred grey pedestrians recede out of focus behind. Camera: smooth cinematic tracking dolly moving alongside the car at matching speed, slight handheld float, shallow depth of field holding the glove sharp while the street streaks past. The glove sways gently in the wind.","resolution": "1080p","duration": 10,"aspect_ratio": "16:9","draft": false,"generate_audio": false}'
Response
{"id": "media_8f3a2c91-5b7d-4e0a-9c26-31d4f2a8e6b0","status": "queued"}
Request body
Accepted values
- resolution
- aspect_ratio
Returns
Returns a job object with status , not the final output. Store the id from the response and poll the job until it completes.
Poll status
GET /v1/media/jobs/{request_id}
Request
curl https://api.dev.pika.art/v1/media/jobs/{request_id} \-H "X-API-Key: YOUR_API_KEY"
Response
{"id": "media_8f3a2c91-5b7d-4e0a-9c26-31d4f2a8e6b0","status": "running"}
Poll the job by id until it reaches a terminal state: completed or failed. A completed job carries its download URL in output, and GET /v1/media/jobs/{request_id}/content returns that same URL as { "url" } for clients that only kept the id.
DELETE /v1/media/jobs/{request_id} erases the stored media for a job, and the request captured at submit (the prompt and parameters). The job then reports deleted_at and no output, and the content endpoint answers 410.
The job object
Errors
shared across calls
Errors use conventional HTTP status codes with a JSON body of the shape {"message": "..."}. Validation failures return 422 with a message naming the offending field. Submit rejections after the job row exists (balance, rate limit) return the failed job envelope — branch on error.code.
| Status | When | Body |
|---|---|---|
| 401 Unauthorized | The API key is missing or invalid. | {"message":"Invalid API key"} |
| 403 Forbidden | An inactive key is rejected with a {"message"} body. A submit that the org balance or postpaid cycle limit cannot cover is rejected after the job row exists and returns the failed job envelope. GET /billing/balance separates the two: a 200 means the key is active, so the rejection was the balance or the cycle limit. | {"id":"media_8f3a2c91-5b7d-4e0a-9c26-31d4f2a8e6b0","status":"failed","error":{"code":"insufficient_balance","message":"Insufficient org balance"}} |
| 404 Not Found | No job with that id exists in your org, or the media path names an unknown vendor/model/function. | {"message":"media job not found"} |
| 409 Conflict | The result was requested before the job completed, or an Idempotency-Key header was reused with a different body. | {"message":"media job is not ready"} |
| 422 Unprocessable Entity | The request body failed validation: an invalid enum value, a missing required field, a wrong type, or malformed JSON. The JSON message names the offending field. A schema-valid parameter combination that cannot be priced instead fails after job creation and returns the failed job envelope with error code invalid_input. | {"message":"duration: Input should be less than or equal to 15"} |
| 429 Too Many Requests | Org limit reached: requests per minute or day, or concurrent jobs. Returned as the failed job envelope; check the Retry-After header and retry with a fresh Idempotency-Key. | {"id":"media_8f3a2c91-5b7d-4e0a-9c26-31d4f2a8e6b0","status":"failed","error":{"code":"rate_limited","message":"rate limit exceeded: rpm"}} |
| 503 Service Unavailable | The model rail or a backend dependency is temporarily unavailable. Returned as the failed job envelope; retry with backoff and a fresh Idempotency-Key. | {"id":"media_8f3a2c91-5b7d-4e0a-9c26-31d4f2a8e6b0","status":"failed","error":{"code":"provider_unavailable","message":"media dispatch unavailable"}} |