Retrieve task · Legacy format
Retrieve Wan 3.0 tasks using the legacy response format.
This endpoint returns a legacy task in code/message/data. New integrations should use platform retrieval; the response structures are not interchangeable.
/v1/video/generations/{task_id}Authorization
bearerAuth Use the platform API Key: Authorization: Bearer your-api-key.
In: header
Path Parameters
The public task ID returned by the platform. Store it as a string and use it for retrieval and download, not request_id or a nested upstream task ID.
1 <= lengthResponse Body
application/json
application/json
application/json
Read legacy results
code: "success" indicates query success only. Still check data.status:
| Status | Meaning |
|---|---|
NOT_START/SUBMITTED/QUEUED | Not started, submitted, or queued |
IN_PROGRESS | Processing |
SUCCESS | Successful; read data.result_url |
FAILURE | Failed; read data.fail_reason and stop polling |
data.progress is a string such as "100%", unlike numeric progress in platform retrieval. created_at/updated_at/submit_time/start_time/finish_time are Unix timestamps in seconds; start or finish times may be 0 before the event. Examples show task-related fields; actual responses may contain others.
Query and download using the public task ID returned by creation, shown here as data.task_id. data.data is the native response; its task ID is not used for platform queries or downloads.
Polling and error handling
Poll about every 15 seconds, set an overall timeout, and stop at a terminal status. Save the completed video promptly. Stopping polling does not cancel generation.
HTTP 400 task_not_exist and HTTP 401 are query errors, not normal task statuses. Check the task ID, API site, and API Key before processing task data.