> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gengen.farm/llms.txt
> Use this file to discover all available pages before exploring further.

# Retrieve WonderClip video task

> Retrieve normalized status and video outputs for a WonderClip task.

```text theme={"dark"}
GET https://gengen.farm/api/gengen/v1/contents/generations/tasks/{id}
```

Retrieve a WonderClip video task with the public ID returned by
[Create WonderClip video task](/api-reference/wonderclip/video-generation/create-task).

[Try the retrieve workflow](https://gengen.farm/api-explorer/demos/wonderclip-video-generation-query).

## Path parameter

<ParamField path="id" type="string" required>
  Public task ID with the `wonderclip10:` prefix. URL-encode the colon when placing the ID in the
  request path.
</ParamField>

```bash theme={"dark"}
curl --request GET \
  --url https://gengen.farm/api/gengen/v1/contents/generations/tasks/wonderclip10%3Aag_123 \
  --header 'Authorization: Bearer gengen_live_xxxxxxxxxxxxxxxx'
```

## Response

```json theme={"dark"}
{
  "id": "wonderclip10:ag_123",
  "model": "wonder-pro",
  "status": "succeeded",
  "outputs": {
    "videos": [
      "https://example.com/generated-video.mp4"
    ],
    "images": []
  }
}
```

| Field            | Type      | Description                                   |
| ---------------- | --------- | --------------------------------------------- |
| `id`             | string    | Public GENGEN task ID                         |
| `model`          | string    | Public WonderClip model ID used by the task   |
| `status`         | string    | `queued`, `running`, `succeeded`, or `failed` |
| `outputs.videos` | string\[] | Generated video URLs after success            |
| `outputs.images` | string\[] | Reserved image outputs; empty for video tasks |
| `failureReason`  | string    | Failure explanation when provided             |

Provider-native job state and output containers are not part of the standard response. Existing
compatibility clients can continue to consume them where available, but new integrations should
read `status` and `outputs.videos`.

<Note>
  Retrieve the task with the same GENGEN API key that created it. Another key in the same
  workspace cannot retrieve the task.
</Note>