Skip to main content
POST
Video Extensions

Video Extensions

The OpenAI format shares the POST /v1/videos/extensions path with Unified Video. For an explanation of the Unified Video flow, see Video Extensions (Unified Video). Use POST /v1/videos/extensions to extend a specified segment of an existing video task; pass the original task ID in video.url in the Body.
  • The route entry is POST /v1/videos/extensions.
  • Required fields: model, prompt, video, start_time.
  • Set video.url to the original video task ID, for example grok:f673ba58-b053-4d8d-8938-c0b429de4d7f.

Method and Path

Request Example

Response Example

Authentication

Body

string
required
Model name, for example grok-video-3.
string
required
Prompt for the extension segment.
object
required
Reference to the original video. Currently requires the url field.
string
required
Original video task ID (not a playable HTTP link), for example grok:f673ba58-b053-4d8d-8938-c0b429de4d7f.
integer
required
Segment start time (seconds); extend from this timestamp in the original video.
integer
Target duration after extension (seconds). Default is 10; supports 6, 10, and 15.

Response

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

Difference Between Extend and Extensions