Skip to main content
POST
Video Extensions

Video Extensions

In the Grok unified video pipeline, segment extension is still submitted through POST /v1/videos/extensions (the same path as OpenAI-format Video Extensions), with the original task ID passed in video.url in the body.
  • The route entry is POST /v1/videos/extensions.
  • model, prompt, video, and start_time are required.
  • Set video.url to the original task ID, for example grok:f673ba58-b053-4d8d-8938-c0b429de4d7f.
  • After a successful submission, use Query Task to poll for results.

Method and Path

Request Example

Response Example

Authentication

Body

model
string
required
Model name, for example grok-video-3.
prompt
string
required
Prompt for the extension segment.
video
object
required
Reference to the original video, which must include the url field.
video.url
string
required
Original video task ID, the same as the id returned by unified Create Video.
start_time
integer
required
Segment start time (seconds).
duration
integer
Target extension duration (seconds). Defaults to 10, supports 6, 10, and 15.

Response

id
string
New extensions task ID.
status
string
Task status, common values include processing, completed, and failed.
status_update_time
integer
Most recent status update time (Unix timestamp).

Difference Between Extend and Extensions Under Unified Video