Retrieve video generation task

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

Authorization

header

AuthorizationstringRequired

Bearer <your Amux AI 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 task.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 MiniMax 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 MiniMax shape has no corresponding fields. This endpoint also does not return the upstream task_type / modality / usage — use the unified endpoint when you need usage.

Status field#

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

Note that cancelled carries two l's, matching the upstream spelling.

The Amux expired state (the task did not complete and its result can no longer be retrieved) maps to failed: it is a failure with a definite cause, not a lookup miss. Upstream keeps task records for 7 days; Amux never deletes them, so "this ID is no longer known" does not arise on this endpoint.

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 — the upstream's own suggested interval is 10 seconds.

Do not extrapolate timeouts linearly from output length.

Artifact URL#

task.content.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/v2/query/video_generation/{id} \
  -H "Authorization: Bearer $AMUX_API_KEY"

{
  "task": {
    "id": "<string>",
    "status": "queued",
    "content": {
      "url": "<string>"
    },
    "error": {
      "code": "<string>",
      "message": "<string>"
    }
  },
  "request_id": "<string>"
}