Wan 2.6 Flash API documentation

Integrate Wan 2.6 Flash with your VezAPI key. The operations below share the same authentication and account balance.

Base URL: https://api.vezapi.com
Send Authorization: Bearer YOUR_VEZAPI_KEY. Use a unique Idempotency-Key for each submission; reuse it only when checking the same request.

Wan - 2.6-flash-image-to-video

POST/api/v1/jobs/createTask

Model IDs: wan/2-6-flash-image-to-video

Parameter	Type	Description & constraints
`model` required	`string`	The model name to use for generation. Required field. - Must be `wan/2-6-flash-image-to-video` for this endpoint Values: `"wan/2-6-flash-image-to-video"` Default: `"wan/2-6-flash-image-to-video"`
`callBackUrl` optional	`string`	The URL to receive generation task completion updates. Optional but recommended for production use. - System will POST task status and results to this URL when generation completes - Callback includes generated content URLs and task information - Your callback endpoint should accept POST requests with JSON payload containing results - Alternatively, use the Get Task Details endpoint to poll task status
`input` optional	`object`	Input parameters for the generation task
`input.prompt` required	`string`	Text prompts for video generation. Supports Chinese and English, 2–1,500 characters. `maxLength: 1500`
`input.image_urls` required	`array`	A list of image URLs. All images must be at least 256x256px. (File URL after upload, not file content; Accepted types: image/jpeg, image/png, image/webp; Max size: 10.0MB) `maxItems: 1`
`input.duration` optional	`string`	The duration of the generated video in seconds Values: `"5", "10", "15"` Default: `"5"`
`input.resolution` optional	`string`	Video resolution tier Values: `"720p", "1080p"` Default: `"1080p"`
`input.audio` required	`boolean`	Whether to generate video with audio. Audio directly affects the cost, as the pricing differs between videos with sound and silent videos. (Boolean value (true/false))
`input.multi_shots` optional	`boolean`	The multi shots parameter controls the shot composition style during AI video generation, determining whether the generated video is a single continuous shot or multiple shots with transitions. (Boolean value (true/false))
`input.nsfw_checker` optional	`boolean`	Defaults to false. When false, no additional content filtering is applied and results are returned directly by the model.

Request example

curl -X POST 'https://api.vezapi.com/api/v1/jobs/createTask' \
  -H 'Authorization: Bearer YOUR_VEZAPI_KEY' \
  -H 'Idempotency-Key: your-unique-request-id' \
  -H 'Content-Type: application/json' \
  -d '{
  "model": "wan/2-6-flash-image-to-video",
  "input": {
    "prompt": "Anthopmopric fox singing a Christmas song at the rubbish dump in the rain.",
    "image_urls": [
      "https://example.com/input.png"
    ],
    "duration": "5",
    "resolution": "720p",
    "audio": false
  }
}'

Responses and errors

HTTP 200

Request successful

Parameter	Type	Description & constraints
`code` optional	`integer`	Status code of the request. The HTTP status is 200 even when the request fails, so always check this field: 200 means success; any other value means the request failed and msg describes the reason. Common values: 401 invalid or missing API key; 402 insufficient credits; 429 rate limit exceeded; 422 or 500 the request could not be processed (read msg and check your parameters before retrying). Values: `200, 401, 402, 404, 422, 429, 433, 455, 500, 501, 505`
`msg` optional	`string`	Response message, error description upon failure
`data` required	`object`
`data.taskId` required	`string`	The task ID can be used with the "Get Task Details" endpoint to query the task status.

HTTP 500

Server error.

Wan - 2-6-flash-video-to-video

POST/api/v1/jobs/createTask

Model IDs: wan/2-6-flash-video-to-video

Parameter	Type	Description & constraints
`model` required	`string`	The model name to use for generation. Required field. - Must be `wan/2-6-flash-video-to-video` for this endpoint Values: `"wan/2-6-flash-video-to-video"` Default: `"wan/2-6-flash-video-to-video"`
`callBackUrl` optional	`string`	The URL to receive generation task completion updates. Optional but recommended for production use. - System will POST task status and results to this URL when generation completes - Callback includes generated content URLs and task information - Your callback endpoint should accept POST requests with JSON payload containing results - Alternatively, use the Get Task Details endpoint to poll task status
`input` optional	`object`	Input parameters for the generation task
`input.prompt` required	`string`	Text prompts for video generation. Supports Chinese and English, 2–1,500 characters. `maxLength: 1500`
`input.video_urls` required	`array`	Reference video URLs. (File URL after upload, not file content; Accepted types: video/mp4, video/quicktime, video/x-matroska; Max size: 10.0MB) `maxItems: 3`
`input.duration` optional	`string`	The duration of the generated video in seconds Values: `"5", "10"` Default: `"5"`
`input.resolution` optional	`string`	Video resolution tier Values: `"720p", "1080p"` Default: `"1080p"`
`input.audio` optional	`boolean`	Whether to generate video with audio. Audio directly affects the cost, as the pricing differs between videos with sound and silent videos. (Boolean value (true/false))
`input.multi_shots` optional	`boolean`	The multi shots parameter controls the shot composition style during AI video generation, determining whether the generated video is a single continuous shot or multiple shots with transitions. (Boolean value (true/false))
`input.nsfw_checker` optional	`boolean`	Defaults to false. When false, no additional content filtering is applied and results are returned directly by the model.

Request example

curl -X POST 'https://api.vezapi.com/api/v1/jobs/createTask' \
  -H 'Authorization: Bearer YOUR_VEZAPI_KEY' \
  -H 'Idempotency-Key: your-unique-request-id' \
  -H 'Content-Type: application/json' \
  -d '{
  "model": "wan/2-6-flash-video-to-video",
  "input": {
    "prompt": "The video drinks milk tea while doing some improvised dance moves to the music.",
    "video_urls": [
      "https://example.com/input.png"
    ],
    "duration": "5",
    "resolution": "720p"
  }
}'

Responses and errors

HTTP 200

Request successful

Parameter	Type	Description & constraints
`code` optional	`integer`	Status code of the request. The HTTP status is 200 even when the request fails, so always check this field: 200 means success; any other value means the request failed and msg describes the reason. Common values: 401 invalid or missing API key; 402 insufficient credits; 429 rate limit exceeded; 422 or 500 the request could not be processed (read msg and check your parameters before retrying). Values: `200, 401, 402, 404, 422, 429, 433, 455, 500, 501, 505`
`msg` optional	`string`	Response message, error description upon failure
`data` required	`object`
`data.taskId` required	`string`	The task ID can be used with the "Get Task Details" endpoint to query the task status.

HTTP 500

Server error.

Task status and callbacks

For asynchronous tasks, keep the returned taskId. Query GET /api/v1/jobs/recordInfo?taskId=... or provide callBackUrl when creating the task. Only the account that created a task can access it or derive new resources from it.

A timeout can mean the submission was accepted. Inspect the existing request in your dashboard; do not create another task automatically. Callback delivery is retried and may arrive more than once. Deduplicate with X-VezAPI-Event-Id.

Files, logs and billing

Generated media normally follows a 14-day provider lifetime; uploaded files expire after 24 hours. Save the files you need before expiration. VezAPI streams registered files without keeping a permanent media library. Request logs are retained for two calendar months.

Credits are reserved before submission. Final deductions match actual discounted consumption one for one. Unknown usage pauses new paid requests. If available funds cannot cover final usage while protecting other reservations, settlement stays pending until funded; model usage cannot make the wallet negative. Time-based inputs require server-side metadata reads; a failed read prevents submission.