Skip to main content
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

Authorization: Bearer YOUR_API_KEY

​
Request Example

cURL
curl https://api.crazyrouter.com/v1/video/generations/video_task_abc123   -H "Authorization: Bearer YOUR_API_KEY"

​
Typical Success Response

{
  "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: 
{
  "code": "task_not_exist",
  "message": "task_not_exist",
  "data": null
}

​
Common Status Values

StatusDescription
queuedTask is submitted or queued
processingTask is running
SUCCESSTask finished successfully
failedTask failed
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.