Retrieve video task

Last updated September 8, 2026

Read a bytedance/doubao-seedance-2-0-fast task in Ark's shape. Same task as the unified endpoint.

Read a bytedance/doubao-seedance-2-0-fast task in Volcengine Ark's shape. It reads the same task as the unified endpoint; only the rendering differs.

GEThttps://gateway.amux.ai/api/v3/contents/generations/tasks/{id}

Authorization

header

AuthorizationstringRequired

Bearer <your Amux key> Your Amux API key.

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.

An alias, not a second store

One task, two renderings. It exists because Ark clients build this URL themselves — without it, pointing base_url here would submit fine and then 404 on retrieval.

Status values

Status	Meaning
`queued` / `running`	Still running; keep polling
`succeeded`	Done; the result is in `content.video_url`
`failed`	Failed; the reason is in `error`
`cancelled`	Cancelled. Required: two l's, following the upstream spelling
`expired`	Outlived `execution_expires_after` (48 hours by default). Not billed; the reservation is released

Usage

This endpoint returns Ark-compatible usage.completion_tokens and usage.total_tokens. The generated-video token count is the quantity used for billing. Cost is available from the unified shape.

The result URL points at our storage

Not the upstream's signed, expiring temporary URL. Required: the field is video_url, not url — that is the upstream's own naming, unlike the MiniMax shape.

cURL

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>"
  }
}