Skip to main content

Overview

Wan 3.0 Video generates videos from prompts, first-frame or first-and-last-frame images, and multimodal reference inputs such as images, videos, audio files, files, and web links. 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 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

Reference-to-video

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
Wan 3.0 Video input parameters.
Use public, directly accessible URLs for all media inputs. Video and audio durations are checked before the task is submitted.
When duration is positive and video_urls are provided, total reference video seconds plus duration cannot exceed 30 seconds. When duration is -1, the request uses smart duration and is pre-charged as 30 seconds.

Response format

Submit task response

POST /generateTask/wan-3-0-video 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: 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

Wan 3.0 Video is billed per second. Unit price depends on both mode and resolution. Billing formulas: Input images, audio files, files, and links do not add separate billable seconds. For current route and market comparison pricing, see Pricing.

Latency and polling

Wan 3.0 Video tasks are asynchronous. Actual latency may vary by prompt complexity, duration, reference media accessibility, resolution, route queue load, and provider-side processing 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 provider error. Common values include: See Error Codes for the full error reference.