Retrieve video task

Returns the status and result of an alibaba/happyhorse-1.1 task in Alibaba Model Studio's own shape.

Authorization

header

AuthorizationstringRequired

Bearer <your Amux key> Your Amux API key.

Request

idstringRequired

The task ID returned at submit time (ours, not the upstream's).

Response

200response

The task's current state.

404response

No such task, or it does not belong to the current workspace. Both return

404: a 403 would let someone confirm that a task exists.

Same task as the unified retrieve#

This endpoint and the unified retrieve return two renderings of the same task, not two task systems.

This address exists because DashScope SDKs build it themselves — without it, pointing base_url at Amux would submit fine and then 404 on retrieve. If you are not keeping an existing SDK, prefer the unified retrieve: it also carries usage and cost, which Model Studio's envelope simply does not have.

Only our task ID works#

task_id is Amux's ID. The upstream's ID is an internal field and never appears in any response.

Status and billing#

Upstream uses UNKNOWN for "I no longer know this task" (its tasks answer that after 24 hours). It does not occur here — our task rows are never deleted, so we can always answer with a terminal state.

Poll about every 15 seconds. This model normally takes minutes; polling harder will not produce the result sooner.

Artifact links are cleaned up#

video_url points at our storage, not the upstream's 24-hour signed temporary URL. That address is cleaned up periodically — download promptly if you need to keep the file. It returns 404 afterwards.

Errors#

type values and retry semantics are described in Errors and retries.

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

{
  "output": {
    "task_id": "<string>",
    "task_status": "PENDING",
    "video_url": "<string>",
    "code": "<string>",
    "message": "<string>"
  },
  "request_id": "<string>"
}