Overview
Wan 2.5 Image is an Alibaba image model for text-to-image and image-to-image generation. 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:
Copy-paste async quickstart
This minimal request submits a text-to-image task and returns ataskId.
taskId; you need it to poll for the final result.
Poll for result
resultJson after state becomes success:
Request body
Text-to-image
Image-to-image
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 callback URL that can receive the final task payload. See Webhooks.object
required
Wan 2.5 Image input parameters.
Response format
Submit task response
POST /generateTask/wan-2-5-image 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 image 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 provider timing is available.
success, and resultJson.resultUrls includes only successful images.
Webhook callback mode
Use callback mode when your backend should receive the final result automatically instead of polling.Billing
Wan 2.5 Image is billed per generated image.
Billing behavior:
ModelPricing.md.
Latency and polling
Wan 2.5 Image tasks are asynchronous. The backend does not provide a fixed public latency SLA; actual latency varies by prompt complexity, requested image count, media fetch speed, and queue load.
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
failCode is route-dependent and may come from mapped third-party model failures. Common values include:
Parameter troubleshooting
promptis required for both modes and cannot be empty.image_urlsis required only forimage-to-image, and must contain1-3items.num_imagessupports1-4; if omitted, default is4.aspect_ratiomust match the selected mode’s supported set.aspect_ratiodefaults to1:1when omitted.- In
text-to-image, any providedimage_urlsinput is ignored.