Seedance 2.0
查询视频生成任务
本文介绍查询视频生成任务 API 的输入输出参数，供您使用接口时查阅字段含义。按任务 ID 查询任务的当前状态、实际生效的生成参数，以及生成成功后的视频地址。
只能查询当前 API Key 所属账号下的任务。响应结构与 callback_url 收到的通知一致。
任务状态
status 的取值与流转：
| 阶段 | 状态 | 说明 |
|---|---|---|
| 检测 | pending_review → review_passed | 内容安全检测通过后进入排队 |
review_blocked | 未通过检测，任务终止 | |
| 生成 | queued → running | 排队中 → 生成中 |
| 终态 | succeeded | 生成成功，可取视频 |
failed | 生成失败，原因见 error | |
cancelled | 已取消 | |
expired | 超过 execution_expires_after 设定的时间 |
进入终态后 status 不再变化。创建任务时填写了 callback_url 的，状态变化会异步推送到该地址，无需轮询本接口。
取回生成结果
status 为 succeeded 时，产出在 content 下：
| 字段 | 说明 |
|---|---|
content.video_url | 生成视频的下载地址 |
content.expiredAt | video_url 的过期时间，RFC3339 格式 |
content.last_frame_url | 尾帧图像地址，仅在创建时设置 return_last_frame=true 时返回 |
video_url 是带签名的临时地址
有效期至 content.expiredAt，即任务 updated_at 之后 24 小时，过期后失效。需要长期保存的视频请在有效期内转存至己方存储，不要直接把该地址存库或分发给终端用户。
接口详情
授权
BearerAuth Authorization<token>
需要鉴权的接口请传入 Bearer <token> 形式的访问令牌。
位置: header
路径参数
id*string
任务 ID
响应主体
application/json
application/json
application/json
application/json
application/json
application/json
application/json
在线请求
「发送」会向所选服务器地址发起真实调用，与生产环境请求等效，可能产生计费。
请求示例
curl -X GET "https://example.com/api/v3/contents/generations/tasks/string"响应示例
{ "content": { "expiredAt": "2026-06-04T10:02:00Z", "last_frame_url": "https://cdn.example.com/last-frame.png", "video_url": "https://cdn.example.com/output.mp4" }, "created_at": 1712664960, "duration": 5, "error": { "code": "upstream_failed", "message": "seedance task failed upstream" }, "execution_expires_after": 172800, "framespersecond": 24, "generate_audio": false, "id": "task_019db400-0000-7000-8000-000000000001", "model": "seedance-2.0", "ratio": "16:9", "resolution": "720p", "revised_prompt": "A cinematic ocean wave at sunset, golden hour lighting.", "seed": 42, "service_tier": "default", "status": "succeeded", "updated_at": 1712664990, "usage": { "completion_tokens": 88, "tool_usage": { "web_search": 0 }, "total_tokens": 88 }}{ "error": { "code": "InvalidParameter", "message": "The parameter content specified in the request is not valid. Request id: 0217790892668142434549f79b621a35", "param": "content", "reasonCode": "seedance_text_blocked_by_moderation", "requestId": "seedance_req_019e8808-d40e-7ccd-873c-072b78b15437", "type": "BadRequest" }}{ "error": { "code": "InvalidParameter", "message": "The parameter content specified in the request is not valid. Request id: 0217790892668142434549f79b621a35", "param": "content", "reasonCode": "seedance_text_blocked_by_moderation", "requestId": "seedance_req_019e8808-d40e-7ccd-873c-072b78b15437", "type": "BadRequest" }}{ "error": { "code": "InvalidParameter", "message": "The parameter content specified in the request is not valid. Request id: 0217790892668142434549f79b621a35", "param": "content", "reasonCode": "seedance_text_blocked_by_moderation", "requestId": "seedance_req_019e8808-d40e-7ccd-873c-072b78b15437", "type": "BadRequest" }}{ "error": { "code": "InvalidParameter", "message": "The parameter content specified in the request is not valid. Request id: 0217790892668142434549f79b621a35", "param": "content", "reasonCode": "seedance_text_blocked_by_moderation", "requestId": "seedance_req_019e8808-d40e-7ccd-873c-072b78b15437", "type": "BadRequest" }}{ "error": { "code": "InvalidParameter", "message": "The parameter content specified in the request is not valid. Request id: 0217790892668142434549f79b621a35", "param": "content", "reasonCode": "seedance_text_blocked_by_moderation", "requestId": "seedance_req_019e8808-d40e-7ccd-873c-072b78b15437", "type": "BadRequest" }}{ "error": { "code": "InvalidParameter", "message": "The parameter content specified in the request is not valid. Request id: 0217790892668142434549f79b621a35", "param": "content", "reasonCode": "seedance_text_blocked_by_moderation", "requestId": "seedance_req_019e8808-d40e-7ccd-873c-072b78b15437", "type": "BadRequest" }}