Kling 3.0 Turbo API documentation

Integrate Kling 3.0 Turbo with your VezAPI key. The operations below share the same authentication and account balance.

Base URL: https://api.vezapi.com
Send Authorization: Bearer YOUR_VEZAPI_KEY. Use a unique Idempotency-Key for each submission; reuse it only when checking the same request.

Kling - V3 Turbo Image to Video

POST/api/v1/jobs/createTask

Model IDs: kling/v3-turbo-image-to-video

Parameter	Type	Description & constraints
`model` required	`string`	The model name to use for generation. Required field. - Must be `kling/v3-turbo-image-to-video` for this endpoint Values: `"kling/v3-turbo-image-to-video"` Default: `"kling/v3-turbo-image-to-video"`
`callBackUrl` optional	`string`	The URL to receive generation task completion updates. Optional but recommended for production use. - System will POST task status and results to this URL when generation completes - Callback includes generated content URLs and task information - Your callback endpoint should accept POST requests with JSON payload containing results - Alternatively, use the Get Task Details endpoint to poll task status - To ensure callback security, see [Webhook Verification Guide](/common-api/webhook-verification) for signature verification implementation
`input` required	`object`	Input parameters for the generation task
`input.prompt` required	`string`	The text prompt describing the video to generate (Max length: 2500 characters) `maxLength: 2500`
`input.image_urls` required	`array`	Required. URL of the image to be used for the video (File URL after upload, not file content; Accepted types: image/jpeg, image/png; Max size: 10.0MB) `maxItems: 1`
`input.duration` required	`string`	Required. The duration of the generated video in seconds Optional duration: 3s - 15s
`input.resolution` required	`string`	Required. Resolution of the generated video (720p or 1080p) Values: `"720p", "1080p"`

Request example

curl -X POST 'https://api.vezapi.com/api/v1/jobs/createTask' \
  -H 'Authorization: Bearer YOUR_VEZAPI_KEY' \
  -H 'Idempotency-Key: your-unique-request-id' \
  -H 'Content-Type: application/json' \
  -d '{
  "model": "kling/v3-turbo-image-to-video",
  "input": {
    "prompt": "Outdoor terrace of a European villa, by a dining table with a blue and white checkered tablecloth, a young white woman in a blue and white striped short-sleeve shirt and khaki shorts, with a brown belt, sits barefoot, opposite a young white man in a white T-shirt.The camera zooms in, the woman swirls the juice in a glass, her eyes looking at the distant woods, and says, \"These trees will turn yellow in a month, won'\''t they?\"Close-up of the man, he lowers his head and says, \"But they'\''ll be green again next summer.\"Then the woman turns her head, smiles at the man opposite, and says, \"Are you always this optimistic? Or just about summer?\"Then the man lifts his head, looks at the woman and says, \"Only about summers with you.\"",
    "image_urls": [
      "https://example.com/input.png"
    ],
    "duration": "5",
    "resolution": "720p"
  }
}'

Responses and errors

HTTP 200

Request successful

Parameter	Type	Description & constraints
`code` optional	`integer`	Status code of the request. The HTTP status is 200 even when the request fails, so always check this field: 200 means success; any other value means the request failed and msg describes the reason. Common values: 401 invalid or missing API key; 402 insufficient credits; 429 rate limit exceeded; 422 or 500 the request could not be processed (read msg and check your parameters before retrying). Values: `200, 401, 402, 404, 422, 429, 433, 455, 500, 501, 505`
`msg` optional	`string`	Response message, error description upon failure
`data` required	`object`
`data.taskId` required	`string`	The task ID can be used with the "Get Task Details" endpoint to query the task status.

HTTP 500

Server error.

Kling - V3 Turbo Text to Video

POST/api/v1/jobs/createTask

Model IDs: kling/v3-turbo-text-to-video

Parameter	Type	Description & constraints
`model` required	`string`	The model name to use for generation. Required field. - Must be `kling/v3-turbo-text-to-video` for this endpoint Values: `"kling/v3-turbo-text-to-video"` Default: `"kling/v3-turbo-text-to-video"`
`callBackUrl` optional	`string`	The URL to receive generation task completion updates. Optional but recommended for production use. - System will POST task status and results to this URL when generation completes - Callback includes generated content URLs and task information - Your callback endpoint should accept POST requests with JSON payload containing results - Alternatively, use the Get Task Details endpoint to poll task status - To ensure callback security, see [Webhook Verification Guide](/common-api/webhook-verification) for signature verification implementation
`input` required	`object`	Input parameters for the generation task
`input.prompt` required	`string`	The text description of the video you want to generate (Max length: 2500 characters) `maxLength: 2500`
`input.duration` required	`string`	Required. The duration of the generated video in seconds Optional duration: 3s - 15s
`input.aspect_ratio` required	`string`	Required. The aspect ratio of the generated video frame Values: `"1:1", "9:16", "16:9"`
`input.resolution` required	`string`	Required. Resolution of the generated video (720p or 1080p) Values: `"720p", "1080p"`

Request example

curl -X POST 'https://api.vezapi.com/api/v1/jobs/createTask' \
  -H 'Authorization: Bearer YOUR_VEZAPI_KEY' \
  -H 'Idempotency-Key: your-unique-request-id' \
  -H 'Content-Type: application/json' \
  -d '{
  "model": "kling/v3-turbo-text-to-video",
  "input": {
    "prompt": "Outdoor terrace of a European villa, by a dining table with a blue and white checkered tablecloth, a young white woman in a blue and white striped short-sleeve shirt and khaki shorts, with a brown belt, sits barefoot, opposite a young white man in a white T-shirt.The camera zooms in, the woman swirls the juice in a glass, her eyes looking at the distant woods, and says, \"These trees will turn yellow in a month, won'\''t they?\"Close-up of the man, he lowers his head and says, \"But they'\''ll be green again next summer.\"Then the woman turns her head, smiles at the man opposite, and says, \"Are you always this optimistic? Or just about summer?\"Then the man lifts his head, looks at the woman and says, \"Only about summers with you.\"",
    "duration": "5",
    "aspect_ratio": "16:9",
    "resolution": "720p"
  }
}'

Responses and errors

HTTP 200

Request successful

Parameter	Type	Description & constraints
`code` optional	`integer`	Status code of the request. The HTTP status is 200 even when the request fails, so always check this field: 200 means success; any other value means the request failed and msg describes the reason. Common values: 401 invalid or missing API key; 402 insufficient credits; 429 rate limit exceeded; 422 or 500 the request could not be processed (read msg and check your parameters before retrying). Values: `200, 401, 402, 404, 422, 429, 433, 455, 500, 501, 505`
`msg` optional	`string`	Response message, error description upon failure
`data` required	`object`
`data.taskId` required	`string`	The task ID can be used with the "Get Task Details" endpoint to query the task status.

HTTP 500

Server error.

Task status and callbacks

For asynchronous tasks, keep the returned taskId. Query GET /api/v1/jobs/recordInfo?taskId=... or provide callBackUrl when creating the task. Only the account that created a task can access it or derive new resources from it.

A timeout can mean the submission was accepted. Inspect the existing request in your dashboard; do not create another task automatically. Callback delivery is retried and may arrive more than once. Deduplicate with X-VezAPI-Event-Id.

Files, logs and billing

Generated media normally follows a 14-day provider lifetime; uploaded files expire after 24 hours. Save the files you need before expiration. VezAPI streams registered files without keeping a permanent media library. Request logs are retained for two calendar months.

Credits are reserved before submission. Final deductions match actual discounted consumption one for one. Unknown usage pauses new paid requests. If available funds cannot cover final usage while protecting other reservations, settlement stays pending until funded; model usage cannot make the wallet negative. Time-based inputs require server-side metadata reads; a failed read prevents submission.