Retrieve Seedance task

Look up a video task by the ID returned at submit time. The response is in Volcengine Ark's shape.

Authorization

header

AuthorizationstringRequired

Bearer <your Amux key> An Amux key created in the console. If you lose it, you can view it again on the keys page.

Request

idstringRequired

The Amux task ID returned at submit time.

Response

200response

Always 200, finished or not — the state is in status.

404response

No such task in this workspace.

Relationship to the unified retrieval endpoint#

This endpoint returns the same task as GET /v1/tasks/{id}: one task table, one ID, one set of data, rendered two ways at the very end.

It is provided because Ark clients construct this address themselves; without it, changing base_url would produce successful submissions and 404s on retrieval.

New integrations should use the unified endpoint, which carries usage and cost; the Ark shape has no corresponding fields. This endpoint also does not return the upstream usage / resolution / duration — use the unified endpoint when you need usage.

Status field#

Always 200, whether or not the task has finished. The state lives in status, so polling only has to read that one field.

⚠️ Note that cancelled carries two l's, matching the upstream spelling. ⚠️ The artifact field is content.video_url, not content.url — that is also the vendor's own naming, and it differs from the MiniMax shape.

Polling#

Video generation takes an order of magnitude longer than image generation, and elapsed time is dominated by queueing rather than scaling with the requested duration. Suggested: do not poll during the first 20 seconds, then poll every 10-15 seconds.

Do not extrapolate timeouts linearly from output length.

Artifact URL#

content.video_url points at Amux storage, not the upstream's provider-signed, expiring temporary address. Those URLs are cleaned up periodically — download anything you need to keep.

Not found returns 404#

No such task, or the task does not belong to your workspace — both return the same 404.

Sharing one response is deliberate: separating them would allow a task ID to be probed across workspaces to confirm whether it exists.

curl https://gateway.amux.ai/api/v3/contents/generations/tasks/{id} \
  -H "Authorization: Bearer $AMUX_API_KEY"

{
  "id": "<string>",
  "model": "<string>",
  "status": "queued",
  "content": {
    "video_url": "<string>"
  },
  "usage": {
    "completion_tokens": 0,
    "total_tokens": 0,
    "tool_usage": {
      "web_search": 0
    }
  },
  "error": {
    "code": "<string>",
    "message": "<string>"
  }
}