Skip to main content
Wan 2.7

Wan 2.7 -- Retrieve video editing result

Check wan2.7 video editing task status

GET
/tasks/{task_id}
cURL - Query task result
# Replace {task_id} with the actual task ID from the submit response
curl -X GET 'https://dashscope-intl.aliyuncs.com/api/v1/tasks/{task_id}' \
  -H "Authorization: Bearer $DASHSCOPE_API_KEY"
{
  "request_id": "f16ae7e9-d518-92f8-a02c-xxxxxx",
  "output": {
    "task_id": "05e68c7e-850c-49e4-b866-xxxxxx",
    "task_status": "SUCCEEDED",
    "submit_time": "2026-04-03 00:08:03.576",
    "scheduled_time": "2026-04-03 00:08:13.408",
    "end_time": "2026-04-03 00:11:57.286",
    "orig_prompt": "Convert the entire scene to a claymation style",
    "video_url": "https://dashscope-a717.oss-accelerate.aliyuncs.com/xxx.mp4?xxxx"
  },
  "usage": {
    "duration": 10.04,
    "input_video_duration": 5.02,
    "output_video_duration": 5.02,
    "video_count": 1,
    "SR": 720
  }
}
Check task status and retrieve video editing results.

Polling strategy

  1. Submit a task via Edit a video and save the returned task_id.
  2. Poll every 15 seconds until task_status reaches SUCCEEDED or FAILED.
  3. On success, retrieve the video from video_url.

Notes

  • URL expiration: Download within 24 hours -- video_url expires after that.
  • Status flow: PENDING -> RUNNING -> SUCCEEDED / FAILED.

Authorizations

string
header
required

DashScope API Key. Get one from the Qwen Cloud console.

Path Parameters

string
required

Task ID from the submit response.

Response

200-application/json
string

Unique request identifier for tracing and troubleshooting.

f16ae7e9-d518-92f8-a02c-xxxxxx
object
object

Resource consumption. Only present when task_status is SUCCEEDED.