Create Video
Unified Video
Create Video
Use POST /v1/video/create to submit Sora asynchronous generation tasks via the unified video format.
POST
Create Video
Create Video
The Sora unified video entry point usesPOST /v1/video/create, and the request body is JSON. Unlike OpenAI-format Sora video generation, this API uses fields such as images, orientation, size, and duration, and supports Sora-specific options such as watermark, private, style, and storyboard.
- The route entry point is
POST /v1/video/create. - Reference images are passed as a list of URLs in the
imagesarray; text-to-video can pass an empty array. - A common model example is
sora-2; use the model actually available in the current channel as the standard. - After a successful submission, the task
idandstatusare returned; use Query Task to poll for results later.
Method and Path
Request Example
Response Example
object, model, progress, created_at, size, and detail, and its structure is consistent with the OpenAI VIDEO response format.
Authentication
Body
List of reference image links. Text-to-video can pass
[].Model name, for example
sora-2.Frame orientation.
portrait means vertical, and landscape means horizontal.Prompt.
Output specification.
small generally corresponds to 720p.Video duration in seconds. The default is often
10; optional values are 10, 15, and 25 (sora-2-pro supports longer durations).Whether to keep the watermark. The default is
true: the system will first try to generate without a watermark, and may fall back to a watermark if that fails. Passing false forces no watermark; if a watermark-removal error occurs, it may automatically retry.Whether to hide the video. When
true, the video will not be published and remix will not be available; the default is false.Video style, available only for supported models such as
sora_video2. Optional values include thanksgiving, comic, news, selfie, nostalgic, and anime.Whether to use a storyboard to achieve finer-grained control over video generation details.
Response
Task ID, passed as the
id parameter in subsequent queries.Task status. Common values include
pending, queued, processing, completed, failed, and cancelled.The most recent status update time (Unix timestamp).
Object type; some responses use
video.The actual model used.
Task progress.
Submission details, usually including the echoed
input field.