Skip to main content

Overview

Wan 2.5 generates short videos from a text prompt or from one reference image plus a prompt.

Endpoint and authentication

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

Copy-paste async quickstart

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

Parameters

string
default:"async"
required
Result delivery mode. Use async for polling with statusTask, or 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 2.5 input parameters.

Response format

Submit task response

POST /generateTask/wan-2-5-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: pending, processing, success, or failed.
string
JSON string containing the generated video URLs. 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 successful completion.

Webhook callback mode

Use callback mode when your backend should receive the final result automatically instead of polling.
See Webhooks for delivery requirements and retry behavior.

Billing

Wan 2.5 is billed per generated second. Final cost formula:
For current route and market comparison pricing, see Pricing.

Latency and polling

Video generation is long-running. Actual latency may vary by prompt complexity, mode, selected resolution, and current queue load.
For high-concurrency production workloads, use callback mode to avoid frequent polling.
Practical notes:
  • Use aspect_ratio only with text-to-video.
  • audio_urls supports one MP3/WAV URL with max 15 MB; recommended duration range is 3-30 seconds.
  • For image-to-video, image_urls must contain exactly one image URL and the image file should be at most 20 MB.
  • Result URLs are temporary. Download important outputs promptly.
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

Task failure codes

Parameter troubleshooting

  • prompt is required for text-to-video, optional for image-to-video.
  • image_urls is required only for image-to-video and must contain exactly one URL.
  • audio_urls supports exactly one MP3/WAV URL when provided; file size should be ≤ 15 MB and recommended duration range is 3-30 seconds.
  • resolution defaults to 1080p when omitted.
  • duration defaults to 5 when omitted and only accepts 5 or 10.
  • aspect_ratio applies only to text-to-video.
See Error Codes for the full error reference.