Skip to main content
POST
/
grok
/
generations
cURL
curl --request POST \
  --url https://api.ttapi.io/grok/generations \
  --header 'Content-Type: application/json' \
  --header 'TT-API-KEY: <api-key>' \
  --data '
{
  "prompt": "<string>",
  "aspect_ratio": "16:9",
  "video_length": "10",
  "resolution_name": "720p",
  "refer_images": [
    "<string>"
  ],
  "hook_url": "https://example.com/callback"
}
'
{
  "status": "SUCCESS",
  "message": "success",
  "data": {
    "job_id": "job_id"
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.ttapi.io/llms.txt

Use this file to discover all available pages before exploring further.

Start here if you need the main endpoint for Grok video API generation. For the complete endpoint directory, workflow guidance, and related links, see the Grok video API overview.

​
When To Use Grok Generations API

Use this endpoint when your app needs:
  • Prompt-based Grok Video API generation
  • A text-to-video entry point for async creative workflows
  • The first step before polling results with Grok Fetch API
  1. Submit the video generation request through Grok Generations API.
  2. Store the returned job identifier.
  3. Poll the Grok Fetch API until the result is ready.

​
Before You Integrate

Authorizations

​
TT-API-KEY
string
header
required

You can obtain your API key from the TTAPI Dashboard.

Body

application/json
​
prompt
string
required

Prompt

​
aspect_ratio
enum<string>
default:16:9

Video aspect ratio

Available options:
2:3,
3:2,
1:1,
9:16,
16:9
​
video_length
string
default:10

Video duration with range from 10 to 30 seconds

​
resolution_name
string
default:720p

Output resolution, currently only supports 720p

​
refer_images
string[]

Reference image URL['https://cdn.ttapi.io/other/2026-03-13/a86ca2c7-6333-4840-b337-395a5d02a182.png','https://cdn.ttapi.io/other/2026-03-13/64a858ed-6095-45ce-92d5-b515c9864703.png']

​
hook_url
string

Callback URL address. When the task completes or fails, notifications will be sent to this address. The notification data structure is consistent with the fetch structure. If not set, you need to call the fetch endpoint to query the result

Example:

"https://example.com/callback"

Response

Request successful

​
status
string
required
Example:

"SUCCESS"

​
message
string
required
Example:

"success"

​
data
object
required
Example:
{ "job_id": "job_id" }
Last modified on April 15, 2026