Skip to main content

Overview

Vidu Q3 is a per-second video generation model for text-to-video, image-to-video, and Turbo image-to-video workflows. Use this page when you are ready to call the API after trying the model 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 Standard text-to-video task and returns a taskId.
Successful response:
Save the taskId; you need it to poll for the final video.

Poll for result

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

Request body

Text-to-video

Single-image animation

First-and-last-frame transition

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 URL that can receive the final task payload. See Webhooks.
object
required
Vidu Q3 input parameters.
Use public, directly accessible image URLs for image modes. The task is rejected if an image URL cannot be accessed or processed.

Response format

Submit task response

POST /generateTask/vidu-q3 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, 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. Present after completion when timing data is available.

Webhook callback mode

Use callback mode when your backend should receive the final result automatically instead of polling.
The callback payload uses the same top-level shape as status polling with code, message, and data. Successful callbacks include the final state and resultJson. See Webhooks for delivery requirements and retry behavior.

Billing

Vidu Q3 is billed per second. The selected mode determines whether the task uses the Standard or Turbo rate, and resolution determines the per-second unit price.
For current route and market comparison pricing, see Pricing.

Latency and polling

Video generation is long-running. Typical Vidu Q3 processing time is about 60-120 seconds, but actual latency may vary by mode, duration, resolution, prompt complexity, reference image accessibility, route queue load, and storage transfer time.
For production workloads, use callback mode to avoid frequent polling while video tasks run.
Result URLs are temporary. Download and store important outputs promptly after task completion. Rate limits and concurrency can vary by account, API key, and route. If you receive 429, slow down requests and retry with backoff. For account-level details, see System APIs.

Errors and troubleshooting

HTTP errors

Validation notes

Task failure codes

failCode is generated from APIXO’s mapped upstream error. Common values include: See Error Codes for the full error reference.