Kling 2.5 Turbo API documentation

Integrate Kling 2.5 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 - V2.5 Turbo Image to Video Pro

POST/api/v1/jobs/createTask

Model IDs: kling/v2-5-turbo-image-to-video-pro

Parameter	Type	Description & constraints
`model` required	`string`	The model name to use for generation. Required field. - Must be `kling/v2-5-turbo-image-to-video-pro` for this endpoint Values: `"kling/v2-5-turbo-image-to-video-pro"` Default: `"kling/v2-5-turbo-image-to-video-pro"`
`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` optional	`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_url` required	`string`	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)
`input.tail_image_url` optional	`string`	Tail frame image of video (File URL after upload, not file content; Accepted types: image/jpeg, image/png; Max size: 10.0MB)
`input.duration` required	`string`	Required. "5" or "10" (seconds). Values: `"5", "10"`
`input.negative_prompt` optional	`string`	Negative prompt to exclude certain elements from the video (Max length: 2,496 characters) `maxLength: 2496`
`input.cfg_scale` optional	`number`	The CFG (Classifier Free Guidance) scale is a measure of how close you want the model to stick to your prompt (Min: 0, Max: 1, Step: 0.1) (step: 0.1) Default: `0.5` `minimum: 0` `maximum: 1`

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/v2-5-turbo-image-to-video-pro",
  "input": {
    "prompt": "A team of paratroopers descends into enemy territory, as they pass through clouds, the camera switches to a slow pan above the battlefield lighting up with",
    "image_url": "https://example.com/input.png",
    "duration": "5"
  }
}'

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 - V2.5 Turbo Text to Video Pro

POST/api/v1/jobs/createTask

Model IDs: kling/v2-5-turbo-text-to-video-pro

Parameter	Type	Description & constraints
`model` required	`string`	The model name to use for generation. Required field. - Must be `kling/v2-5-turbo-text-to-video-pro` for this endpoint Values: `"kling/v2-5-turbo-text-to-video-pro"` Default: `"kling/v2-5-turbo-text-to-video-pro"`
`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` optional	`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. "5" or "10" (seconds). Values: `"5", "10"`
`input.aspect_ratio` optional	`string`	The aspect ratio of the generated video frame Values: `"16:9", "9:16", "1:1"` Default: `"16:9"`
`input.negative_prompt` optional	`string`	Things to avoid in the generated video (Max length: 2500 characters) `maxLength: 2500`
`input.cfg_scale` optional	`number`	The CFG (Classifier Free Guidance) scale is a measure of how close you want the model to stick to your prompt (Min: 0, Max: 1, Step: 0.1) (step: 0.1) Default: `0.5` `minimum: 0` `maximum: 1`

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/v2-5-turbo-text-to-video-pro",
  "input": {
    "prompt": "Real-time playback. Wide shot of a ruined city: collapsed towers, fires blazing, storm clouds with lightning. Camera drops fast from the sky over burning streets and tilted buildings. Smoke and dust fill the air. A lone hero walks out of the ruins, silhouetted by fire. Camera shifts front: his face is dirty with dust and sweat, eyes firm, a faint smile. Wind blows, debris rises. Extreme close-up: his eyes reflect the approaching enemy. Music and drums hit. Final wide shot: fire forms a blazing halo behind him — reborn in flames with epic cinematic vibe.",
    "duration": "5",
    "aspect_ratio": "16:9"
  }
}'

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.