メインコンテンツへスキップ
更新日: 2026-06-07

Video Generation Alias

This is a Crazyrouter compatibility alias for clients or middleware that are already pinned to the /v1/video/generations path.

Authentication

When To Use It

  • your client is hardcoded to /v1/video/generations
  • you are migrating an older video workflow and do not want to change the path
  • you need to preserve compatibility with an existing third-party request shape
  • you want to submit Wan text-to-video models such as wan2.5-t2v-preview or wan2.2-t2v-plus
For new integrations, prefer:
  • Wan text-to-video: use this page’s POST /v1/video/generations
  • Veo / unified-video workflows: use POST /v1/video/create with veo-3.1-fast or veo-3.1-quality
  • OpenAI-compatible video workflows: use POST /v1/videos

Minimal Request Example

Wan 2.2 T2V Plus

cURL

Generic Minimal Example

cURL

Typical Success Response

Error Response Verified Locally

On the local http://127.0.0.1:4000 environment, this route was verified to exist. When the model is temporarily unavailable, it returns a business error rather than 404:

Notes

  • request fields vary by video model and upstream capability
  • model availability depends on the token whitelist and current upstream state
  • Wan text-to-video uses model, prompt, seconds, and size; the verified wan2.2-t2v-plus combinations are seconds: "5" with size: "480P" or "1080P".
  • Do not submit wan2.2-t2v-plus to /alibailian/api/v1/services/aigc/video-generation/video-synthesis.
  • after task creation, query status with GET /v1/video/generations/{task_id}
This route is a compatibility alias. It does not guarantee that every video model shares the exact same body schema. Wan text-to-video currently uses this route; Veo and unified-video workflows should use /v1/video/create with veo-3.1-fast or veo-3.1-quality.