AnyInt Docs
Models

Video Generation

The current published generic video flow is task-based. DashScope media routes and Transtreams Kling routes are available.

The current published generic video flow is task-based. DashScope media routes remain available, and Kling V3 video is available through Transtreams task routes.

Published routes

RoutePurpose
POST /dashscope/v1/services/aigc/video-generation/video-synthesisCreate a video from prompt, image, and audio
GET /dashscope/v1/tasks/{task_id}Query video task status and fetch the result
POST /transtreams/kling/v1/videos/text2videoCreate a Kling V3 text-to-video task
GET /transtreams/kling/v1/videos/text2video/{task_id}Query a Kling V3 text-to-video task
POST /transtreams/kling/v1/videos/omni-videoCreate a Kling V3 Omni video task
GET /transtreams/kling/v1/videos/omni-video/{task_id}Query a Kling V3 Omni video task

Input pattern

The current schema combines:

  • a text prompt
  • an image URL
  • an audio URL
  • generation parameters such as duration and resolution

Task lifecycle

The response returns a task immediately. After that:

  1. store task_id
  2. query the task route
  3. wait for task_status to reach success
  4. consume video_url

In the published examples, the task starts as PENDING and later becomes SUCCEEDED.

For Kling V3 details, including Standard/Pro model_name: "kling-v3", Omni model_name: "kling-v3-omni", mode, audio, and reference video, see Kling video. The Omni model is displayed as Kling: Video v3.0 Omni.

Practical advice

  • Design your UI as an async workflow, not a single request-response page
  • Persist the original prompt, task ID, and returned asset URL together
  • Keep polling as a fallback even if you also use webhooks elsewhere in your platform

Where AI Music fits

If you are generating a music video from a song workflow rather than a generic video pipeline, look at Media & Music instead of treating it as a plain video job.

On this page