Unified Video

Video Remix

Use `POST /v1/video/remix` to submit remix requests for existing Grok tasks through the unified video format.

POSThttps://zx1.deepwl.net/v1/video/remix
Request
curl -X POST https://zx1.deepwl.net/v1/video/remix \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '
{
  "model": "grok-video-3",
  "prompt": "play with another white cat",
  "aspect_ratio": "3:2",
  "size": "1080P",
  "task_id": "grok:48a67431-0708-46d1-9ab9-83cb84700153"
}'
Response
{
  "id": "grok:48a67431-0708-46d1-9ab9-83cb84700153",
  "status": "processing",
  "status_update_time": 1762685256
}

The Grok unified video remix endpoint is POST /v1/video/remix. Unlike OpenAI-format Video Remix, the original task ID is passed in the Body via task_id instead of a path parameter.

  • Required fields: model, prompt, size, aspect_ratio, task_id.
  • After submission succeeds, poll the newly returned id using Query Task.

Request Headers

Authorizationstring必填

Authentication header. Uses a Bearer token, e.g. Bearer YOUR_API_KEY.

Content-Typestring必填

Request content type, must be application/json.

Request Body

modelstring必填

Model name, for example grok-video-3.

promptstring必填

Remix prompt.

sizestring必填

Resolution specification, pass 720P or 1080P.

aspect_ratiostring必填

Video ratio, optional values: 2:3, 3:2, 1:1.

task_idstring必填

Original video task ID, matching the id returned by Create Video or Query Task.

parent_post_idstring

Upstream post ID. Appears in some Apifox examples; not a required schema field. Pass it if needed.

Request Examples

Response Examples

Response Fields

idstring

New remix task ID.

statusstring

Task status. Common values include processing, completed, failed.

status_update_timeinteger

Most recent status update time (Unix timestamp).