Skip to main content
POST
Video API Overview
Choose a video family below for its request schema and examples. Most families use the shared asynchronous endpoints; Kling uses separate native endpoints and task queries, with a different response structure.

Video Families

Endpoints and Authentication

The shared endpoints above and workflow below do not apply to Kling. For Kling, store submission data.id and use Query Kling Task to read succeeded and outputs[].url.
Use the exact model identifier from your account’s Model Marketplace or List Models. A vendor release alone does not imply MixRoute access.

Workflow

  1. Select a family page and construct that model’s request.
  2. Submit it and retain the MixRoute task_id (some routes also return id).
  3. Use Query Video Task until success or a terminal failure. Submission success does not mean the video has finished.
  4. Read the result URL returned for your route. Use Download Video for Sora routes that require the separate download endpoint.

Submission Response

Illustrative gateway response:
Keep the submitted task ID rather than substituting an upstream operation name or file ID. A timeout after submission is not proof that no task was created; check the console before resubmitting to avoid duplicate paid tasks.