Wan 2.7 Pro API, Wan 2.6 API, Wan 2.5 API, Wan 2.2 API: Pricing, Documentation

Authentication

All requests require an API key passed via header.

Webhook (Optional)

You can optionally provide a webhook_url in your request body. When the request completes (success or failure), a POST request will be sent to your webhook URL with the result payload.

Webhook Payload (Success)

{
  "request_id": "wan-2-7-api_019d4e3f-83c5-719c-dbba-039df43078184",
  "status": "COMPLETED",
  "result": {
    "images": [
      {
        "file_name": "output.png",
        "content_type": "image/png",
        "url": "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-api_019d4e3f-83c5-719c-dbba-039df43078184/output.png"
      }
    ],
    "description": ""
  }
}

Webhook Payload (Failure)

{
  "request_id": "wan-2-7-api_019d4e3f-83c5-719c-dbba-039df43078184",
  "status": "FAILED",
  "error": "Processing failed: upstream provider returned an error"
}

Content Policy

Request Parameters - Wan 2.7 Text to Image Request

Response

{
  "status": "QUEUED",
  "request_id": "wan-2-7-api_019d4e3f-83c5-719c-dbba-039df43078184",
  "message": "Request accepted and queued for processing"
}

Request Headers

Response Handling

Common status codes for Wan 2.7 Text to Image Request.

Error Responses

Error responses from the queue system and status/webhook errors.

Queue System Errors

{
  "error": "Invalid request: prompt is required",
  "status": 400
}

{
  "error": "Unauthorized: invalid or missing API key",
  "status": 401
}

{
  "error": "Insufficient balance. Please top up your wallet.",
  "status": 402
}

{
  "error": "Rate limit exceeded. Please retry after some time.",
  "status": 429
}

Status / Webhook Errors

{
  "request_id": "wan-2-7-api_019d4e3f-83c5-719c-dbba-039df43078184",
  "status": "FAILED",
  "error": "Processing failed: upstream provider returned an error"
}

{
  "error": "Request not found",
  "status": 404
}

Retrieving Results

After submitting a request, use the request_id from the queued response to check the status and retrieve results.

GET /v2/requests/status/{request_id}

GET https://gateway.pixazo.ai/v2/requests/status/wan-2-7-api_019d4e3f-83c5-719c-dbba-039df43078184
Ocp-Apim-Subscription-Key: YOUR_API_KEY

Response (Queued / Processing)

{
  "request_id": "wan-2-7-api_019d4e3f-83c5-719c-dbba-039df43078184",
  "status": "PROCESSING",
  "message": "Request is being processed"
}

Response (Completed)

{
  "request_id": "wan-2-7-api_019d4e3f-83c5-719c-dbba-039df43078184",
  "status": "COMPLETED",
  "result": {
    "images": [
      {
        "file_name": "output.png",
        "content_type": "image/png",
        "url": "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-api_019d4e3f-83c5-719c-dbba-039df43078184/output.png"
      }
    ],
    "description": ""
  }
}

Response (Failed)

{
  "request_id": "wan-2-7-api_019d4e3f-83c5-719c-dbba-039df43078184",
  "status": "FAILED",
  "error": "Processing failed: upstream provider returned an error"
}

Response Fields - Wan 2.7 Text to Image Request

Status Values

Status Flow

QUEUED  -->  PROCESSING  -->  COMPLETED
                          \-->  FAILED

Typical Workflow

1. Submit a POST request to https://gateway.pixazo.ai/wan-2-7-api/v1/generateWan27TextToImageRequest with your parameters.
2. Receive a 202 Accepted response with a request_id and status QUEUED.
3. Poll the status endpoint GET /v2/requests/status/{request_id} periodically (e.g. every 5-10 seconds).
4. Retrieve the result once status is COMPLETED. The result object contains image URLs.
5. (Optional) Use a webhook_url to receive results automatically without polling.

Authentication

All requests require an API key passed via header.

Webhook (Optional)

You can optionally provide a webhook_url in your request body. When the request completes (success or failure), a POST request will be sent to your webhook URL with the result payload.

Webhook Payload (Success)

{
  "request_id": "wan-2-7-api_019d4e44-7a8e-7df1-fad0-926fa428ca293",
  "status": "COMPLETED",
  "result": {
    "images": [
      {
        "file_name": "output.png",
        "content_type": "image/png",
        "url": "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-api_019d4e44-7a8e-7df1-fad0-926fa428ca293/output.png"
      }
    ],
    "description": ""
  }
}

Webhook Payload (Failure)

{
  "request_id": "wan-2-7-api_019d4e44-7a8e-7df1-fad0-926fa428ca293",
  "status": "FAILED",
  "error": "Processing failed: upstream provider returned an error"
}

Content Policy

Request Parameters - Wan 2.7 Edit Image Request

Content Item Types & Limits

Response

{
  "status": "QUEUED",
  "request_id": "wan-2-7-api_019d4e44-7a8e-7df1-fad0-926fa428ca293",
  "message": "Request accepted and queued for processing"
}

Request Headers

Response Handling

Common status codes for Wan 2.7 Edit Image Request.

Error Responses

Error responses from the queue system and status/webhook errors.

Queue System Errors

{
  "error": "Invalid request: prompt is required",
  "status": 400
}

{
  "error": "Unauthorized: invalid or missing API key",
  "status": 401
}

{
  "error": "Insufficient balance. Please top up your wallet.",
  "status": 402
}

{
  "error": "Rate limit exceeded. Please retry after some time.",
  "status": 429
}

Status / Webhook Errors

{
  "request_id": "wan-2-7-api_019d4e44-7a8e-7df1-fad0-926fa428ca293",
  "status": "FAILED",
  "error": "Processing failed: upstream provider returned an error"
}

{
  "error": "Request not found",
  "status": 404
}

Retrieving Results

After submitting a request, use the request_id from the queued response to check the status and retrieve results.

GET /v2/requests/status/{request_id}

GET https://gateway.pixazo.ai/v2/requests/status/wan-2-7-api_019d4e44-7a8e-7df1-fad0-926fa428ca293
Ocp-Apim-Subscription-Key: YOUR_API_KEY

Response (Queued / Processing)

{
  "request_id": "wan-2-7-api_019d4e44-7a8e-7df1-fad0-926fa428ca293",
  "status": "PROCESSING",
  "message": "Request is being processed"
}

Response (Completed)

{
  "request_id": "wan-2-7-api_019d4e44-7a8e-7df1-fad0-926fa428ca293",
  "status": "COMPLETED",
  "result": {
    "images": [
      {
        "file_name": "output.png",
        "content_type": "image/png",
        "url": "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-api_019d4e44-7a8e-7df1-fad0-926fa428ca293/output.png"
      }
    ],
    "description": ""
  }
}

Response (Failed)

{
  "request_id": "wan-2-7-api_019d4e44-7a8e-7df1-fad0-926fa428ca293",
  "status": "FAILED",
  "error": "Processing failed: upstream provider returned an error"
}

Response Fields - Wan 2.7 Edit Image Request

Status Values

Status Flow

QUEUED  -->  PROCESSING  -->  COMPLETED
                          \-->  FAILED

Typical Workflow

1. Submit a POST request to https://gateway.pixazo.ai/wan-2-7-api/v1/generateWan27EditImageRequest with your parameters.
2. Receive a 202 Accepted response with a request_id and status QUEUED.
3. Poll the status endpoint GET /v2/requests/status/{request_id} periodically (e.g. every 5-10 seconds).
4. Retrieve the result once status is COMPLETED. The result object contains image URLs.
5. (Optional) Use a webhook_url to receive results automatically without polling.

Authentication

All requests require an API key passed via header.

Webhook (Optional)

Add the X-Webhook-URL header to your submit request to receive a POST callback when the job completes — no polling required.

Using curl? These are HTTP request headers — pass each with -H, e.g. -H "X-Webhook-URL: https://your-server.com/webhook/callback". Do not paste them as bare lines, and end every line of a multi-line command with \.

Webhook Headers

Example: enable webhook

X-Webhook-URL: https://your-server.com/webhook/callback
X-Webhook-Mode: terminal

Callback Payload

Your endpoint receives a POST application/json with the same shape as the GET /v2/requests/status/{request_id} response. Example terminal callback (mode terminal):

{
  "request_id": "wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "wan-2-7-video-api",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-05-22T13:17:32.110Z",
  "updated_at": "2026-05-22 13:19:23",
  "completed_at": "2026-05-22 13:19:23"
}

Failure callback shape

{
  "request_id": "wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "wan-2-7-video-api",
  "error": "Description of the error",
  "output": null,
  "created_at": "...",
  "updated_at": "...",
  "completed_at": "..."
}

Delivery semantics

• terminal mode (default) — exactly one POST when the request reaches a terminal status. No callback during PROCESSING.
• sync mode — POST on every status poll (with delay capped at ~15s) plus a final POST at terminal status. Use when you want progress updates.
• Idempotency — use request_id as your idempotency key. Network retries can deliver the same callback more than once; your handler must tolerate duplicates.
• Response — respond 200 OK within a few seconds. The queue does not block on slow handlers, but persistent failures may stop further deliveries.
• HTTPS required — plain http:// URLs are rejected.

Request Parameters - Wan 2.7 Video Style Transfer Request

Content Item Types & Limits

Request Headers

Response Handling

Common status codes.

Error Responses

Queue system errors and model validation errors.

Queue System Errors

// 402 — Insufficient balance
{
  "error": "Insufficient Balance",
  "message": "Your wallet does not have enough balance. Required: $0.01"
}

// 400 — Model not found
{
  "error": "Model not found",
  "message": "Model 'wan-2-7-video-api' not found or is disabled"
}

Error via Status/Webhook

{
  "request_id": "wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "wan-2-7-video-api",
  "error": "Description of the error",
  "output": null
}

Retrieving Results

Poll the universal status endpoint to check progress and retrieve results.

Endpoint

GET https://gateway.pixazo.ai/v2/requests/status/{request_id}
Ocp-Apim-Subscription-Key: YOUR_API_KEY

curl -H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
  "https://gateway.pixazo.ai/v2/requests/status/wan-2-7-video-api_019d52bf-9ae0-7faf-594a-08e2d4e7281b0"

{
  "request_id": "wan-2-7-video-api_019d52bf-9ae0-7faf-594a-08e2d4e7281b0",
  "status": "COMPLETED",
  "model_id": "wan-2-7-video-api",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-video-api_019d52bf-9ae0-7faf-594a-08e2d4e7281b0/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-03-31T07:32:03.749Z",
  "updated_at": "2026-03-31T07:32:20.000Z",
  "completed_at": "2026-03-31T07:32:20.000Z"
}

Response Fields

Status Values

Status Flow

QUEUED → PROCESSING → COMPLETED
                    → FAILED
                    → ERROR

Typical Workflow

1. Send a generate request to the API endpoint
2. Save the request_id from the response
3. Poll every 5-10 seconds: GET /v2/requests/status/{request_id}
4. When status is "COMPLETED", download from output.media_url

Tip: Use X-Webhook-URL header to get a callback instead of polling.

Authentication

All requests require an API key passed via header.

Webhook (Optional)

Add the X-Webhook-URL header to your submit request to receive a POST callback when the job completes — no polling required.

Using curl? These are HTTP request headers — pass each with -H, e.g. -H "X-Webhook-URL: https://your-server.com/webhook/callback". Do not paste them as bare lines, and end every line of a multi-line command with \.

Webhook Headers

Example: enable webhook

X-Webhook-URL: https://your-server.com/webhook/callback
X-Webhook-Mode: terminal

Callback Payload

Your endpoint receives a POST application/json with the same shape as the GET /v2/requests/status/{request_id} response. Example terminal callback (mode terminal):

{
  "request_id": "wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "wan-2-7-video-api",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-05-22T13:17:32.110Z",
  "updated_at": "2026-05-22 13:19:23",
  "completed_at": "2026-05-22 13:19:23"
}

Failure callback shape

{
  "request_id": "wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "wan-2-7-video-api",
  "error": "Description of the error",
  "output": null,
  "created_at": "...",
  "updated_at": "...",
  "completed_at": "..."
}

Delivery semantics

• terminal mode (default) — exactly one POST when the request reaches a terminal status. No callback during PROCESSING.
• sync mode — POST on every status poll (with delay capped at ~15s) plus a final POST at terminal status. Use when you want progress updates.
• Idempotency — use request_id as your idempotency key. Network retries can deliver the same callback more than once; your handler must tolerate duplicates.
• Response — respond 200 OK within a few seconds. The queue does not block on slow handlers, but persistent failures may stop further deliveries.
• HTTPS required — plain http:// URLs are rejected.

Request Parameters - Wan 2.7 Video Edit By Reference Request

Content Item Types & Limits

Request Headers

Response Handling

Common status codes.

Error Responses

Queue system errors and model validation errors.

Queue System Errors

// 402 — Insufficient balance
{
  "error": "Insufficient Balance",
  "message": "Your wallet does not have enough balance. Required: $0.01"
}

// 400 — Model not found
{
  "error": "Model not found",
  "message": "Model 'wan-2-7-video-api' not found or is disabled"
}

Error via Status/Webhook

{
  "request_id": "wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "wan-2-7-video-api",
  "error": "Description of the error",
  "output": null
}

Retrieving Results

Poll the universal status endpoint to check progress and retrieve results.

Endpoint

GET https://gateway.pixazo.ai/v2/requests/status/{request_id}
Ocp-Apim-Subscription-Key: YOUR_API_KEY

curl -H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
  "https://gateway.pixazo.ai/v2/requests/status/wan-2-7-video-api_019d52bf-9ae0-7faf-594a-08e2d4e7281b0"

{
  "request_id": "wan-2-7-video-api_019d52bf-9ae0-7faf-594a-08e2d4e7281b0",
  "status": "COMPLETED",
  "model_id": "wan-2-7-video-api",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-video-api_019d52bf-9ae0-7faf-594a-08e2d4e7281b0/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-03-31T07:32:03.749Z",
  "updated_at": "2026-03-31T07:32:20.000Z",
  "completed_at": "2026-03-31T07:32:20.000Z"
}

Response Fields

Status Values

Status Flow

QUEUED → PROCESSING → COMPLETED
                    → FAILED
                    → ERROR

Typical Workflow

1. Send a generate request to the API endpoint
2. Save the request_id from the response
3. Poll every 5-10 seconds: GET /v2/requests/status/{request_id}
4. When status is "COMPLETED", download from output.media_url

Tip: Use X-Webhook-URL header to get a callback instead of polling.

Authentication

All requests require an API key passed via header.

Webhook (Optional)

Add the X-Webhook-URL header to your submit request to receive a POST callback when the job completes — no polling required.

Using curl? These are HTTP request headers — pass each with -H, e.g. -H "X-Webhook-URL: https://your-server.com/webhook/callback". Do not paste them as bare lines, and end every line of a multi-line command with \.

Webhook Headers

Example: enable webhook

X-Webhook-URL: https://your-server.com/webhook/callback
X-Webhook-Mode: terminal

Callback Payload

Your endpoint receives a POST application/json with the same shape as the GET /v2/requests/status/{request_id} response. Example terminal callback (mode terminal):

{
  "request_id": "wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "wan-2-7-video-api",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-07-08T12:06:52.606Z",
  "updated_at": "2026-07-08 12:08:46",
  "completed_at": "2026-07-08 12:08:46"
}

Failure callback shape

{
  "request_id": "wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "wan-2-7-video-api",
  "error": "Description of the error",
  "output": null,
  "created_at": "...",
  "updated_at": "...",
  "completed_at": "..."
}

Delivery semantics

• terminal mode (default) — exactly one POST when the request reaches a terminal status. No callback during PROCESSING.
• sync mode — POST on every status poll (with delay capped at ~15s) plus a final POST at terminal status. Use when you want progress updates.
• Idempotency — use request_id as your idempotency key. Network retries can deliver the same callback more than once; your handler must tolerate duplicates.
• Response — respond 200 OK within a few seconds. The queue does not block on slow handlers, but persistent failures may stop further deliveries.
• HTTPS required — plain http:// URLs are rejected.

Request Parameters - Text to Video

Request Headers

Response Handling

Error Responses

Submit-time failures return a JSON error immediately (e.g. 402):

{
  "error": "Insufficient balance",
  "message": "Your wallet balance is too low to run this request."
}

Failures after queuing surface through the status endpoint / webhook with status: "ERROR" and a populated error field — see the failure callback shape above. Failed requests are not billed.

Retrieving Results

Poll the status endpoint with the request_id from the submit response:

GET https://gateway.pixazo.ai/v2/requests/status/{request_id}

cURL Example

curl "https://gateway.pixazo.ai/v2/requests/status/wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" \\
  -H "Ocp-Apim-Subscription-Key: YOUR_API_KEY"

Response (Completed)

{
  "request_id": "wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "wan-2-7-video-api",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-07-08T12:06:52.606Z",
  "updated_at": "2026-07-08 12:08:46",
  "completed_at": "2026-07-08 12:08:46"
}

output.media_url[0] is a direct, downloadable URL of the generated video (hosted on our CDN) — a plain GET with no auth headers.

Response Fields

Notes

• Billing — per second of generated video by resolution: $0.10/s at 720P, $0.15/s at 1080P. Default request (1080P, 5s) = $0.75. Failed requests are not billed.
• Audio — pass audio_url (WAV/MP3, 2–30s, ≤ 15 MB, public URL) to add a soundtrack to the generated video.
• Duration — integer seconds, 2–15. Longer durations cost proportionally more and take longer to render.
• Prompts — English and Chinese are supported; prompt_extend (default on) rewrites short prompts for richer results.

Authentication

All requests require an API key passed via header.

Webhook (Optional)

Add the X-Webhook-URL header to your submit request to receive a POST callback when the job completes — no polling required.

Using curl? These are HTTP request headers — pass each with -H, e.g. -H "X-Webhook-URL: https://your-server.com/webhook/callback". Do not paste them as bare lines, and end every line of a multi-line command with \.

Webhook Headers

Example: enable webhook

X-Webhook-URL: https://your-server.com/webhook/callback
X-Webhook-Mode: terminal

Callback Payload

Your endpoint receives a POST application/json with the same shape as the GET /v2/requests/status/{request_id} response. Example terminal callback (mode terminal):

{
  "request_id": "wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "wan-2-7-video-api",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-07-08T12:06:52.606Z",
  "updated_at": "2026-07-08 12:08:46",
  "completed_at": "2026-07-08 12:08:46"
}

Failure callback shape

{
  "request_id": "wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "wan-2-7-video-api",
  "error": "Description of the error",
  "output": null,
  "created_at": "...",
  "updated_at": "...",
  "completed_at": "..."
}

Delivery semantics

• terminal mode (default) — exactly one POST when the request reaches a terminal status. No callback during PROCESSING.
• sync mode — POST on every status poll (with delay capped at ~15s) plus a final POST at terminal status. Use when you want progress updates.
• Idempotency — use request_id as your idempotency key. Network retries can deliver the same callback more than once; your handler must tolerate duplicates.
• Response — respond 200 OK within a few seconds. The queue does not block on slow handlers, but persistent failures may stop further deliveries.
• HTTPS required — plain http:// URLs are rejected.

Request Parameters - Image to Video

Request Headers

Response Handling

Error Responses

Submit-time failures return a JSON error immediately (e.g. 402):

{
  "error": "Insufficient balance",
  "message": "Your wallet balance is too low to run this request."
}

Failures after queuing surface through the status endpoint / webhook with status: "ERROR" and a populated error field — see the failure callback shape above. Failed requests are not billed.

Retrieving Results

Poll the status endpoint with the request_id from the submit response:

GET https://gateway.pixazo.ai/v2/requests/status/{request_id}

cURL Example

curl "https://gateway.pixazo.ai/v2/requests/status/wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" \\
  -H "Ocp-Apim-Subscription-Key: YOUR_API_KEY"

Response (Completed)

{
  "request_id": "wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "wan-2-7-video-api",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-video-api_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-07-08T12:06:52.606Z",
  "updated_at": "2026-07-08 12:08:46",
  "completed_at": "2026-07-08 12:08:46"
}

output.media_url[0] is a direct, downloadable URL of the generated video (hosted on our CDN) — a plain GET with no auth headers.

Response Fields

Notes

• Billing — per second of generated video by resolution: $0.10/s at 720P, $0.15/s at 1080P. Default request (1080P, 5s) = $0.75. Failed requests are not billed.
• Audio — pass audio_url (WAV/MP3, 2–30s, ≤ 15 MB, public URL) to add a soundtrack to the generated video.
• Duration — integer seconds, 2–15. Longer durations cost proportionally more and take longer to render.
• Prompts — English and Chinese are supported; prompt_extend (default on) rewrites short prompts for richer results.

Authentication

All requests require an API key passed via header.

Webhook (Optional)

You can optionally provide a webhook_url in your request body. When the request completes (success or failure), a POST request will be sent to your webhook URL with the result payload.

Webhook Payload (Success)

{
  "request_id": "wan-2-7-pro-api_019d4e4b-b2da-7a82-ecae-994db4acea2c6",
  "status": "COMPLETED",
  "result": {
    "images": [
      {
        "file_name": "output.png",
        "content_type": "image/png",
        "url": "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-pro-api_019d4e4b-b2da-7a82-ecae-994db4acea2c6/output.png"
      }
    ],
    "description": ""
  }
}

Webhook Payload (Failure)

{
  "request_id": "wan-2-7-pro-api_019d4e4b-b2da-7a82-ecae-994db4acea2c6",
  "status": "FAILED",
  "error": "Processing failed: upstream provider returned an error"
}

Request Parameters - Wan 2.7 Pro Text to Image Request

Response

{
  "status": "QUEUED",
  "request_id": "wan-2-7-pro-api_019d4e4b-b2da-7a82-ecae-994db4acea2c6",
  "message": "Request accepted and queued for processing"
}

Request Headers

Response Handling

Common status codes for Wan 2.7 Pro Text to Image Request.

Error Responses

Error responses from the queue system and status/webhook errors.

Queue System Errors

{
  "error": "Invalid request: prompt is required",
  "status": 400
}

{
  "error": "Unauthorized: invalid or missing API key",
  "status": 401
}

{
  "error": "Insufficient balance. Please top up your wallet.",
  "status": 402
}

{
  "error": "Rate limit exceeded. Please retry after some time.",
  "status": 429
}

Status / Webhook Errors

{
  "request_id": "wan-2-7-pro-api_019d4e4b-b2da-7a82-ecae-994db4acea2c6",
  "status": "FAILED",
  "error": "Processing failed: upstream provider returned an error"
}

{
  "error": "Request not found",
  "status": 404
}

Retrieving Results

After submitting a request, use the request_id from the queued response to check the status and retrieve results.

GET /v2/requests/status/{request_id}

GET https://gateway.pixazo.ai/v2/requests/status/wan-2-7-pro-api_019d4e4b-b2da-7a82-ecae-994db4acea2c6
Ocp-Apim-Subscription-Key: YOUR_API_KEY

Response (Queued / Processing)

{
  "request_id": "wan-2-7-pro-api_019d4e4b-b2da-7a82-ecae-994db4acea2c6",
  "status": "PROCESSING",
  "message": "Request is being processed"
}

Response (Completed)

{
  "request_id": "wan-2-7-pro-api_019d4e4b-b2da-7a82-ecae-994db4acea2c6",
  "status": "COMPLETED",
  "result": {
    "images": [
      {
        "file_name": "output.png",
        "content_type": "image/png",
        "url": "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-pro-api_019d4e4b-b2da-7a82-ecae-994db4acea2c6/output.png"
      }
    ],
    "description": ""
  }
}

Response (Failed)

{
  "request_id": "wan-2-7-pro-api_019d4e4b-b2da-7a82-ecae-994db4acea2c6",
  "status": "FAILED",
  "error": "Processing failed: upstream provider returned an error"
}

Response Fields - Wan 2.7 Pro Text to Image Request

Status Values

Status Flow

QUEUED  -->  PROCESSING  -->  COMPLETED
                          \-->  FAILED

Typical Workflow

1. Submit a POST request to https://gateway.pixazo.ai/wan-2-7-pro-api/v1/generateWan27ProTextToImageRequest with your parameters.
2. Receive a 202 Accepted response with a request_id and status QUEUED.
3. Poll the status endpoint GET /v2/requests/status/{request_id} periodically (e.g. every 5-10 seconds).
4. Retrieve the result once status is COMPLETED. The result object contains image URLs.
5. (Optional) Use a webhook_url to receive results automatically without polling.

Authentication

All requests require an API key passed via header.

Webhook (Optional)

You can optionally provide a webhook_url in your request body. When the request completes (success or failure), a POST request will be sent to your webhook URL with the result payload.

Webhook Payload (Success)

{
  "request_id": "wan-2-7-pro-api_019d4e48-893e-7582-850a-9be6943bebe13",
  "status": "COMPLETED",
  "result": {
    "images": [
      {
        "file_name": "output.png",
        "content_type": "image/png",
        "url": "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-pro-api_019d4e48-893e-7582-850a-9be6943bebe13/output.png"
      }
    ],
    "description": ""
  }
}

Webhook Payload (Failure)

{
  "request_id": "wan-2-7-pro-api_019d4e48-893e-7582-850a-9be6943bebe13",
  "status": "FAILED",
  "error": "Processing failed: upstream provider returned an error"
}

Request Parameters - Wan 2.7 Pro Edit Image Request

Content Item Types & Limits

Response

{
  "status": "QUEUED",
  "request_id": "wan-2-7-pro-api_019d4e48-893e-7582-850a-9be6943bebe13",
  "message": "Request accepted and queued for processing"
}

Request Headers

Response Handling

Common status codes for Wan 2.7 Pro Edit Image Request.

Error Responses

Error responses from the queue system and status/webhook errors.

Queue System Errors

{
  "error": "Invalid request: prompt is required",
  "status": 400
}

{
  "error": "Unauthorized: invalid or missing API key",
  "status": 401
}

{
  "error": "Insufficient balance. Please top up your wallet.",
  "status": 402
}

{
  "error": "Rate limit exceeded. Please retry after some time.",
  "status": 429
}

Status / Webhook Errors

{
  "request_id": "wan-2-7-pro-api_019d4e48-893e-7582-850a-9be6943bebe13",
  "status": "FAILED",
  "error": "Processing failed: upstream provider returned an error"
}

{
  "error": "Request not found",
  "status": 404
}

Retrieving Results

After submitting a request, use the request_id from the queued response to check the status and retrieve results.

GET /v2/requests/status/{request_id}

GET https://gateway.pixazo.ai/v2/requests/status/wan-2-7-pro-api_019d4e48-893e-7582-850a-9be6943bebe13
Ocp-Apim-Subscription-Key: YOUR_API_KEY

Response (Queued / Processing)

{
  "request_id": "wan-2-7-pro-api_019d4e48-893e-7582-850a-9be6943bebe13",
  "status": "PROCESSING",
  "message": "Request is being processed"
}

Response (Completed)

{
  "request_id": "wan-2-7-pro-api_019d4e48-893e-7582-850a-9be6943bebe13",
  "status": "COMPLETED",
  "result": {
    "images": [
      {
        "file_name": "output.png",
        "content_type": "image/png",
        "url": "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-7-pro-api_019d4e48-893e-7582-850a-9be6943bebe13/output.png"
      }
    ],
    "description": ""
  }
}

Response (Failed)

{
  "request_id": "wan-2-7-pro-api_019d4e48-893e-7582-850a-9be6943bebe13",
  "status": "FAILED",
  "error": "Processing failed: upstream provider returned an error"
}

Response Fields - Wan 2.7 Pro Edit Image Request

Status Values

Status Flow

QUEUED  -->  PROCESSING  -->  COMPLETED
                          \-->  FAILED

Typical Workflow

1. Submit a POST request to https://gateway.pixazo.ai/wan-2-7-pro-api/v1/generateWan27ProEditImageRequest with your parameters.
2. Receive a 202 Accepted response with a request_id and status QUEUED.
3. Poll the status endpoint GET /v2/requests/status/{request_id} periodically (e.g. every 5-10 seconds).
4. Retrieve the result once status is COMPLETED. The result object contains image URLs.
5. (Optional) Use a webhook_url to receive results automatically without polling.

Authentication

All requests require an API key passed via header.

Webhook (Optional)

Add the X-Webhook-URL header to your submit request to receive a POST callback when the job completes — no polling required.

Using curl? These are HTTP request headers — pass each with -H, e.g. -H "X-Webhook-URL: https://your-server.com/webhook/callback". Do not paste them as bare lines, and end every line of a multi-line command with \.

Webhook Headers

Example: enable webhook

X-Webhook-URL: https://your-server.com/webhook/callback
X-Webhook-Mode: terminal

Callback Payload

Your endpoint receives a POST application/json with the same shape as the GET /v2/requests/status/{request_id} response. Example terminal callback (mode terminal):

{
  "request_id": "wan-2-6-image-to-video-477_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "wan-2-6-image-to-video-477",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-6-image-to-video-477_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-05-22T13:17:32.110Z",
  "updated_at": "2026-05-22 13:19:23",
  "completed_at": "2026-05-22 13:19:23"
}

Failure callback shape

{
  "request_id": "wan-2-6-image-to-video-477_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "wan-2-6-image-to-video-477",
  "error": "Description of the error",
  "output": null,
  "created_at": "...",
  "updated_at": "...",
  "completed_at": "..."
}

Delivery semantics

• terminal mode (default) — exactly one POST when the request reaches a terminal status. No callback during PROCESSING.
• sync mode — POST on every status poll (with delay capped at ~15s) plus a final POST at terminal status. Use when you want progress updates.
• Idempotency — use request_id as your idempotency key. Network retries can deliver the same callback more than once; your handler must tolerate duplicates.
• Response — respond 200 OK within a few seconds. The queue does not block on slow handlers, but persistent failures may stop further deliveries.
• HTTPS required — plain http:// URLs are rejected.

Request Parameters - Wan 2.6 Image to Video generate request

Content Item Types & Limits

Request Headers

Response Handling

Common status codes.

Error Responses

Queue system errors and model validation errors.

Queue System Errors

// 402 — Insufficient balance
{
  "error": "Insufficient Balance",
  "message": "Your wallet does not have enough balance. Required: $0.01"
}

// 400 — Model not found
{
  "error": "Model not found",
  "message": "Model 'wan-2-6-image-to-video-477' not found or is disabled"
}

Error via Status/Webhook

{
  "request_id": "wan-2-6-image-to-video-477_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "wan-2-6-image-to-video-477",
  "error": "Description of the error",
  "output": null
}

Retrieving Results

Poll the universal status endpoint to check progress and retrieve results.

Endpoint

GET https://gateway.pixazo.ai/v2/requests/status/{request_id}
Ocp-Apim-Subscription-Key: YOUR_API_KEY

curl -H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
  "https://gateway.pixazo.ai/v2/requests/status/wan-2-6-image-to-video-477_019d42ce-ae71-7999-24c9-5d76447ecafb4"

{
  "request_id": "wan-2-6-image-to-video-477_019d42ce-ae71-7999-24c9-5d76447ecafb4",
  "status": "COMPLETED",
  "model_id": "wan-2-6-image-to-video-477",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-6-image-to-video-477_019d42ce-ae71-7999-24c9-5d76447ecafb4/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-03-31T07:32:03.749Z",
  "updated_at": "2026-03-31T07:32:20.000Z",
  "completed_at": "2026-03-31T07:32:20.000Z"
}

Response Fields

Status Values

Status Flow

QUEUED → PROCESSING → COMPLETED
                    → FAILED
                    → ERROR

Typical Workflow

1. Send a generate request to the API endpoint
2. Save the request_id from the response
3. Poll every 5-10 seconds: GET /v2/requests/status/{request_id}
4. When status is "COMPLETED", download from output.media_url

Tip: Use X-Webhook-URL header to get a callback instead of polling.

Authentication

All requests require an API key passed via header.

Webhook (Optional)

Add the X-Webhook-URL header to your submit request to receive a POST callback when the job completes — no polling required.

Using curl? These are HTTP request headers — pass each with -H, e.g. -H "X-Webhook-URL: https://your-server.com/webhook/callback". Do not paste them as bare lines, and end every line of a multi-line command with \.

Webhook Headers

Example: enable webhook

X-Webhook-URL: https://your-server.com/webhook/callback
X-Webhook-Mode: terminal

Callback Payload

Your endpoint receives a POST application/json with the same shape as the GET /v2/requests/status/{request_id} response. Example terminal callback (mode terminal):

{
  "request_id": "wan-2-6-text-to-video-569_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "wan-2-6-text-to-video-569",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-6-text-to-video-569_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-05-22T13:17:32.110Z",
  "updated_at": "2026-05-22 13:19:23",
  "completed_at": "2026-05-22 13:19:23"
}

Failure callback shape

{
  "request_id": "wan-2-6-text-to-video-569_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "wan-2-6-text-to-video-569",
  "error": "Description of the error",
  "output": null,
  "created_at": "...",
  "updated_at": "...",
  "completed_at": "..."
}

Delivery semantics

• terminal mode (default) — exactly one POST when the request reaches a terminal status. No callback during PROCESSING.
• sync mode — POST on every status poll (with delay capped at ~15s) plus a final POST at terminal status. Use when you want progress updates.
• Idempotency — use request_id as your idempotency key. Network retries can deliver the same callback more than once; your handler must tolerate duplicates.
• Response — respond 200 OK within a few seconds. The queue does not block on slow handlers, but persistent failures may stop further deliveries.
• HTTPS required — plain http:// URLs are rejected.

Request Parameters - Wan 2.6 Text to Video generate request

Content Item Types & Limits

Request Headers

Response Handling

Common status codes.

Error Responses

Queue system errors and model validation errors.

Queue System Errors

// 402 — Insufficient balance
{
  "error": "Insufficient Balance",
  "message": "Your wallet does not have enough balance."
}

// 400 — Model not found
{
  "error": "Model not found",
  "message": "Model 'wan-2-6-text-to-video-569' not found or is disabled"
}

Error via Status/Webhook

{
  "request_id": "wan-2-6-text-to-video-569_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "wan-2-6-text-to-video-569",
  "error": "Description of the error",
  "output": null
}

Retrieving Results

Poll the universal status endpoint to check progress and retrieve results.

Endpoint

GET https://gateway.pixazo.ai/v2/requests/status/{request_id}
Ocp-Apim-Subscription-Key: YOUR_API_KEY

curl -H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
  "https://gateway.pixazo.ai/v2/requests/status/wan-2-6-text-to-video-569_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

{
  "request_id": "wan-2-6-text-to-video-569_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "wan-2-6-text-to-video-569",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-6-text-to-video-569_019dxxxx-xxxx/output.ext"
    ],
    "media_type": "application/octet-stream"
  },
  "created_at": "2026-03-31T10:00:00.000Z",
  "updated_at": "2026-03-31T10:00:15.000Z",
  "completed_at": "2026-03-31T10:00:15.000Z"
}

Response Fields

Status Values

Status Flow

QUEUED → PROCESSING → COMPLETED
                    → FAILED
                    → ERROR

Typical Workflow

1. Send a generate request to the API endpoint
2. Save the request_id from the response
3. Poll every 5-10 seconds: GET /v2/requests/status/{request_id}
4. When status is "COMPLETED", download from output.media_url

Tip: Use X-Webhook-URL header to get a callback instead of polling.

Authentication

All requests require an API key passed via header.

Webhook (Optional)

Add the X-Webhook-URL header to your submit request to receive a POST callback when the job completes — no polling required.

Using curl? These are HTTP request headers — pass each with -H, e.g. -H "X-Webhook-URL: https://your-server.com/webhook/callback". Do not paste them as bare lines, and end every line of a multi-line command with \.

Webhook Headers

Example: enable webhook

X-Webhook-URL: https://your-server.com/webhook/callback
X-Webhook-Mode: terminal

Callback Payload

Your endpoint receives a POST application/json with the same shape as the GET /v2/requests/status/{request_id} response. Example terminal callback (mode terminal):

{
  "request_id": "wan-2-6-image-to-video-flash-api-353_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "wan-2-6-image-to-video-flash-api-353",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-6-image-to-video-flash-api-353_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/output.mp4"
    ],
    "media_type": "video/mp4"
  },
  "created_at": "2026-05-22T13:17:32.110Z",
  "updated_at": "2026-05-22 13:19:23",
  "completed_at": "2026-05-22 13:19:23"
}

Failure callback shape

{
  "request_id": "wan-2-6-image-to-video-flash-api-353_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "wan-2-6-image-to-video-flash-api-353",
  "error": "Description of the error",
  "output": null,
  "created_at": "...",
  "updated_at": "...",
  "completed_at": "..."
}

Delivery semantics

• terminal mode (default) — exactly one POST when the request reaches a terminal status. No callback during PROCESSING.
• sync mode — POST on every status poll (with delay capped at ~15s) plus a final POST at terminal status. Use when you want progress updates.
• Idempotency — use request_id as your idempotency key. Network retries can deliver the same callback more than once; your handler must tolerate duplicates.
• Response — respond 200 OK within a few seconds. The queue does not block on slow handlers, but persistent failures may stop further deliveries.
• HTTPS required — plain http:// URLs are rejected.

Request Parameters - Wan 2.6 Image-to-Video Flash API generate request

Content Item Types & Limits

Response

Error Responses

Queue system errors and model validation errors.

Queue System Errors

// 402 — Insufficient balance
{
  "error": "Insufficient Balance",
  "message": "Your wallet does not have enough balance."
}

// 400 — Model not found
{
  "error": "Model not found",
  "message": "Model 'wan-2-6-image-to-video-flash-api-353' not found or is disabled"
}

Error via Status/Webhook

{
  "request_id": "wan-2-6-image-to-video-flash-api-353_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "ERROR",
  "model_id": "wan-2-6-image-to-video-flash-api-353",
  "error": "Description of the error",
  "output": null
}

Retrieving Results

Poll the universal status endpoint to check progress and retrieve results.

Endpoint

GET https://gateway.pixazo.ai/v2/requests/status/{request_id}
Ocp-Apim-Subscription-Key: YOUR_API_KEY

curl -H "Ocp-Apim-Subscription-Key: YOUR_API_KEY" \
  "https://gateway.pixazo.ai/v2/requests/status/wan-2-6-image-to-video-flash-api-353_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

{
  "request_id": "wan-2-6-image-to-video-flash-api-353_019dxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "status": "COMPLETED",
  "model_id": "wan-2-6-image-to-video-flash-api-353",
  "error": null,
  "output": {
    "media_url": [
      "https://pub-582b7213209642b9b995c96c95a30381.r2.dev/v1/wan-2-6-image-to-video-flash-api-353_019dxxxx-xxxx/output.ext"
    ],
    "media_type": "application/octet-stream"
  },
  "created_at": "2026-03-31T10:00:00.000Z",
  "updated_at": "2026-03-31T10:00:15.000Z",
  "completed_at": "2026-03-31T10:00:15.000Z"
}

Response Fields

Status Values

Status Flow

QUEUED → PROCESSING → COMPLETED
                    → FAILED
                    → ERROR

Typical Workflow

1. Send a generate request to the API endpoint
2. Save the request_id from the response
3. Poll every 5-10 seconds: GET /v2/requests/status/{request_id}
4. When status is "COMPLETED", download from output.media_url

Tip: Use X-Webhook-URL header to get a callback instead of polling.

Request Headers