Retrieve video task

Look up a minimax/minimax-h3 task in MiniMax's shape.

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 task.status.

404response

No such task in this workspace.

It reads the same task as the unified endpoint#

One task table, one ID, one set of data, rendered two ways at the very end. It exists because MiniMax clients construct this address themselves; without it, changing base_url would give you a successful submit and a 404 on retrieval.

New integrations should prefer the unified endpoint: it carries usage and cost, which this shape has no fields for.

Status#

Always 200, finished or not. The state lives in task.status.

Note cancelled is spelled with two l characters, matching the upstream.

Polling#

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 our storage, not the upstream's provider-signed, expiring address. Those URLs are cleaned up periodically — download anything you need to keep.

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