OpenAI-Compatible Video Interface
OpenAI-Compatible Video Interface
Use OpenAI Videos-style create, query, remix, and content proxy routing operations for video tasks.
POST
OpenAI-Compatible Video Interface
OpenAI-Compatible Video Interface
This set of routes presents itself externally in an OpenAI Videos API style, suitable for clients that already read and write results asvideo objects.
- Creation, querying, and remix all use the OpenAI-style
videoobject. - The exposed
idmaps to the platform task ID, rather than directly exposing the upstream raw task ID. - The
contentproxy route supports access via API Key and logged-in session state. - Remix will preferentially look up the original video task and lock execution to the original channel.
Route List
Request Examples
Response Examples
Authentication
Creation, querying, and remix use Bearer Token:GET /v1/videos/{task_id}/content also supports:
Authorization: Bearer YOUR_API_KEY- Web dashboard login state
UserAuth
Path Parameters
string
必填
Video task ID, used for querying and content proxying.
string
必填
The source video ID for remix. The server will first look up the original task and original channel using it.
Body
string
必填
Video model name, such as
sora-2, sora_video2, or a model name mapped from another channel.string
必填
Video description or remix instruction.
string
Input image for image-to-video generation. Support depends on the specific upstream provider.
string
Target video duration, common values are
5, 10, and 15.string
Target resolution or ratio, such as
1280x720, 720x1280, or 16:9.object
Vendor passthrough parameters. For remix, upstream proprietary fields can also be included here.
Response
string
Public video task ID.
string
Task status, common values are
queued, in_progress, completed, and failed.string
Playable URL after generation is complete. In many cases, it points to the platform proxy route.
object
Error details for failed tasks, shown only when
status = failed.