Amux

Retrieve task

Last updated September 6, 2026

Get an alibaba/happyhorse-1.1 task result in the unified shape, with usage and cost.

Returns the status and result of an alibaba/happyhorse-1.1 task in the unified shape.

GEThttps://gateway.amux.ai/v1/tasks/{id}

Authorization

header
AuthorizationstringRequired

Bearer <your Amux key> Your Amux API key.

Request

idstringRequired

The task ID returned at submit time.

Response

200response

The task's current state.

404response

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

Two fields the Model Studio shape does not have

This endpoint and the Model Studio retrieve are two renderings of the same task. This one also carries:

  • usage.output_video_seconds — the seconds actually produced, which is what cost is computed from;
  • cost — the amount actually charged for this call, in USD.

Model Studio's envelope has no such fields, so that endpoint cannot report them.

output.images is always empty, and always present

Video tasks produce no images, so output.images stays an empty array. The field never disappears — it is kept for existing image clients, which read output.images.length unconditionally. So do not use the presence of images to detect the task modality; that check is always true. Video artifacts are in output.videos.

Status and billing

statusMeaningBilled?
queued / runningQueued / generatingReservation held
succeededDone, artifacts in output.videosBy seconds actually produced
failedUpstream refused or erroredNo, reservation released
expiredNever finished and no longer retrievableNo, reservation released
canceledCanceledNo, reservation released

Poll about every 15 seconds. The last four are terminal and never change, so you can stop polling there.

Dropped parameters are explained here

If you send a parameter this model does not have (audio / prompt_extend), it is dropped, and the "What we did" section of the log detail says what was dropped and why.

Not an error, but not silent either — dropping a parameter is invisible from the request side (it succeeds, the video comes back, only that parameter had no effect), so it needs somewhere to be said.

The same section shows what the upstream actually produced (real frame rate and ratio). That can differ from what you asked for: for first-frame generation the ratio comes from the image, which is the most common reason "the ratio is wrong".

output.videos[].url is a directly accessible mp4 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
curl https://gateway.amux.ai/v1/tasks/{id} \
  -H "Authorization: Bearer $AMUX_API_KEY"
{
  "id": "task_01M1VD9E8WRYVBR7ES10SNQQQT",
  "status": "queued",
  "model": "alibaba/happyhorse-1.1",
  "created_at": "<string>",
  "output": {
    "images": [
      {}
    ],
    "videos": [
      {
        "index": 0,
        "url": "<string>"
      }
    ]
  },
  "usage": {
    "input_tokens": 0,
    "output_tokens": 0,
    "total_tokens": 0,
    "output_video_seconds": 0
  },
  "cost": "0.185654",
  "error": {
    "message": "<string>",
    "code": "<string>"
  }
}