Skip to main content
POST

omni-fast-v2v

omni-fast-v2v submits asynchronous video tasks with a JSON request body, suitable for editing, extending, or regenerating an existing MP4 as a reference video.
  • Asynchronous processing mode; returns id or task_id after submission.
  • The reference video field supports video, video_url, and input_video.
  • The reference video supports a public MP4 URL or data:video/mp4;base64,....
  • The reference video is up to 15MB.
  • When a reference video is not needed, prefer omni-fast.

Method and Path

Request Examples

Response Examples

Authentication

Use Bearer Token authentication:
All request examples must include the Authorization header. JSON requests must also include:

Body

string
required
Fixed value omni-fast-v2v. Example: "omni-fast-v2v".
string
required
Video editing or generation prompt. It is recommended to state which motion, camera, or subject to preserve, and explicitly request a newly generated video. Example: "Edit the attached video into a visibly new version".
string
Reference video. Supports a public MP4 URL or data:video/mp4;base64,.... Choose one of video, video_url, input_video. Example: "https://example.com/source.mp4".
string
Compatibility field for video. Can be used when video is not provided. Example: "https://example.com/source.mp4".
string
Compatibility field for video. Can be used when neither video nor video_url is provided. Example: "https://example.com/source.mp4".
string
Output duration. Recommended as a string; recommended range is 4 to 30 seconds. Example: "8".
string
Aspect ratio. Example values: "16:9", "9:16".
string
Resolution field. Example values: "720p", "1080p", "2k", "4k".
string
First frame image field compatible with omni-fast. When there is no reference video, prefer omni-fast. Example: "https://example.com/first-frame.jpg".
array<string>
Multi-reference image field compatible with omni-fast, up to 5. When there is no reference video, prefer omni-fast.

Response

string
Video task ID. Can be used later for GET /v1/videos/{task_id} queries.
string
Compatibility field for the video task ID. Usually the same as id.
string
Object type, usually video.
string
The model used for this task, for example omni-fast-v2v.
string
Task status. Common values are queued, in_progress, completed, failed.
number
Task progress, commonly in the range 0 to 100.
string
The video URL after completion.
object
The error object returned when a task fails or an API error occurs, usually containing message and code.

Use Cases

Public MP4 Reference Video

Local MP4 to data URI

Using the input_video alias

Notes

  • omni-fast does not support reference video; V2V must use omni-fast-v2v.
  • The reference video is up to 15MB; when too large, compress it first or convert to a public URL.
  • video, video_url, input_video are the same kind of reference-video input; prefer video.
  • For data:video/mp4;base64,..., the actual request body grows larger, so allow for network timeout.
  • After completion, retrieve the generated MP4 from the returned video_url.