Wan 3.0 · API

Quick start

Three steps: submit a job, poll it, take the video link. Replace YOUR_API_KEY with your key and the commands below run as they are.

Step 1 · Submit (returns a job id at once, HTTP 202)

curl https://nezhagate.com/v1/videos/generations \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "wan3.0-video", "prompt": "A shiba inu chases falling cherry blossoms under a tree, bright sunlight, slow motion", "duration": 5, "resolution": "720P", "size": "16:9"}'

Response (HTTP 202)

{
  "id": "img_5c2e8f1a9b3d7e6f0a4c8b2d",
  "object": "video.generation.job",
  "status": "queued",
  "created": 1791281400,
  "model": "wan3.0-video"
}

Step 2 · Poll every 5–10 seconds until status is succeeded or failed

curl https://nezhagate.com/v1/videos/jobs/img_5c2e8f1a9b3d7e6f0a4c8b2d \
  -H "Authorization: Bearer YOUR_API_KEY"

Response when it succeeds

{
  "id": "img_5c2e8f1a9b3d7e6f0a4c8b2d",
  "object": "video.generation.job",
  "status": "succeeded",
  "created": 1791281400,
  "model": "wan3.0-video",
  "data": [
    {"url": "https://img.nezhagate.com/i/8c1f0e5d2b7a49e3a6d0c4f1b9e2a7d5.mp4"}
  ],
  "usage": {"clips": 1, "model": "wan3.0-video"}
}

Step 3 · data[0].url is the clip (MP4). It is kept for 15 days; download it to your own storage to keep it longer.

Complete example (Python: submit, wait, save to disk)

import time
import requests

BASE = "https://nezhagate.com/v1"
HEADERS = {"Authorization": "Bearer YOUR_API_KEY"}

# 1. submit
job = requests.post(f"{BASE}/videos/generations", headers=HEADERS, json={
    "model": "wan3.0-video",
    "prompt": "A shiba inu chases falling cherry blossoms under a tree, bright sunlight, slow motion",
    "duration": 5,
    "resolution": "720P",
    "size": "16:9",
}).json()
if "error" in job:
    raise SystemExit(job["error"]["message"])

# 2. poll every 10 seconds, for up to an hour
deadline = time.time() + 3600
while job["status"] not in ("succeeded", "failed") and time.time() < deadline:
    time.sleep(10)
    job = requests.get(f"{BASE}/videos/jobs/{job['id']}", headers=HEADERS).json()

# 3. download the video
if job["status"] == "succeeded":
    url = job["data"][0]["url"]
    with open("wan3.0-video.mp4", "wb") as f:
        f.write(requests.get(url).content)
    print("saved", url)
elif job["status"] == "failed":
    print("failed:", job["error"]["code"], job["error"]["message"])
else:
    print("still", job["status"], job["id"])

While queued, the poll also returns queue_position (jobs ahead of yours) and eta_seconds (expected wait). If your time limit passes, do not resubmit: the job is still there, so keep polling the same id later.

Authentication

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Create an API Key in the console to start.

At a glance

Request parameters

The JSON body of POST /v1/videos/generations:

Other fields (seed, negative_prompt, fps, watermark and the like) are not passed on and do not change the price; results are always MP4, returned as a url.

Price

Billed per second: cost = the per-second rate of the chosen resolution × (output seconds + the seconds of every reference video). Reference images and audio are free. Held at submit, refunded in full on failure. 1 credit = $0.005.

Reference material

• One endpoint, the parameters pick the mode: no image is text-to-video; one image is the first frame; two images with image_role: first_frame are first + last frame (first, then last); otherwise two or more are references, up to 10.
• Up to 5 reference videos (15 s in total, each with its duration) are used to restyle or continue that footage; with reference videos, images can only be references, not frames. Up to 5 reference audio clips, public URLs only.
• With a first frame, size: adaptive makes the clip follow the image. Human-face review restriction: avoid reference material containing real human faces; realistic faces can also trigger detection. FaceDetectionSuspect means a possible real human face was detected. DataInspectionFailed means the input material did not pass content review, not that the service is unavailable. Replace the reference before resubmitting rather than repeatedly retrying unchanged input; contact support about suspected false positives. Failed tasks are not billed.
• Each image is a public image URL, a data: URI or base64, up to 16 MB; send several as an array in images. We store the images before the job is queued; one that cannot be read is refused with 400, message says which, and nothing is charged.
• Reference files we store are kept for 7 days; results for 15 days.

First + last frame: a transition between two images

curl https://nezhagate.com/v1/videos/generations \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "wan3.0-video", "prompt": "Dawn turns into dusk, clouds drifting, the light growing warmer", "images": ["https://example.com/first.png", "https://example.com/last.png"], "image_role": "first_frame", "duration": 5, "resolution": "720P", "size": "adaptive"}'

image_role: first_frame makes the two images the first and last frame; size: adaptive makes the clip follow the first image. Without image_role, two images are references.

Job status and fields

GET /v1/videos/jobs/{id} reports these statuses; every field is described in Async jobs. Poll every 5–10 seconds, or let a webhook (below) push the result. Polling is free, and any key of the same account can read the job.

• processing can go back to queued, for example while every line is busy, while a finished clip is fetched again, or after a restart. If a line cannot finish a job, the gateway may hand it to the next line to render again; however many lines it passes through, a job is charged once.
• One account runs up to 50 jobs at a time; further jobs wait in submission order, and a job that has not started after 15 minutes fails and is refunded in full. Job records are kept for 3 days and video links for 15 days.

How long it takes

Usually 2–4 minutes; more references take longer.

Real calls over the last 7 days: median 3.5 min, 90% done within 6.9 min.

Errors and refunds

An error at submit comes back at once as HTTP 4xx / 5xx: no job is created and nothing is charged. A failure after the job was accepted is reported by the job endpoint, and the hold is refunded in full. Every code is listed under Error codes.

Errors at submit

Failed jobs (status failed)

Branch on code, not on the text of message. Treat any code you do not recognise (or a missing one) as upstream_error: resubmitting usually works. Every failed job is refunded in full.

Webhooks instead of polling

Add callback_url when you submit and the moment the job ends, success or failure, the gateway pushes exactly what the poll endpoint returns to that URL, signed and retried on failure. You can also set an account-wide address under Settings → Webhook in the console. Webhook docs →

curl https://nezhagate.com/v1/videos/generations \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "wan3.0-video", "prompt": "A shiba inu chases falling cherry blossoms under a tree, bright sunlight, slow motion", "duration": 5, "resolution": "720P", "size": "16:9", "callback_url": "https://your-domain.com/webhook"}'