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

# Video Task Query Alias

> GET /v1/video/generations/{task_id} compatibility alias for querying video task status

> Last updated: 2026-06-06

# Video Task Query Alias

```
GET /v1/video/generations/{task_id}
```

Use this route to query tasks created through the compatibility video-generation path. It is the matching query alias for `/v1/video/generations`.

## Authentication

```http theme={null}
Authorization: Bearer YOUR_API_KEY
```

## Request Example

```bash cURL theme={null}
curl https://api.crazyrouter.com/v1/video/generations/video_task_abc123   -H "Authorization: Bearer YOUR_API_KEY"
```

## Typical Success Response

```json theme={null}
{
  "code": "success",
  "message": "",
  "data": {
    "id": "video_task_abc123",
    "task_id": "video_task_abc123",
    "status": "SUCCESS",
    "result_url": "https://media.crazyrouter.com/task-artifacts/example.mp4",
    "artifact_url": "https://media.crazyrouter.com/task-artifacts/example.mp4"
  }
}
```

## Missing-Task Response Verified Locally

On the local `http://127.0.0.1:4000` environment, querying a nonexistent task returns:

```json theme={null}
{
  "code": "task_not_exist",
  "message": "task_not_exist",
  "data": null
}
```

## Common Status Values

| Status       | Description                 |
| ------------ | --------------------------- |
| `queued`     | Task is submitted or queued |
| `processing` | Task is running             |
| `SUCCESS`    | Task finished successfully  |
| `failed`     | Task failed                 |

<Note>
  Final result fields can vary slightly by video model and upstream provider. The safest operational pattern is to keep creation and query requests on the same compatibility path family, and prefer `data.artifact_url` or `data.result_url`.
</Note>