Overview
Kling 3.0 Turbo is a fast Kuaishou video generation model on APIXO for short clips from text prompts or a single reference image. Use it when you want the Kling 3.0 family with a simpler surface than Kling 3.0 Std.Endpoint and authentication
Base URL:
All requests require your APIXO API key:
Copy-paste async quickstart
This minimal request submits a text-to-video task and returns ataskId.
taskId; you need it to poll for the final result.
Poll for result
resultJson after state becomes success:
Request body
Text-to-video
Image-to-video
Parameters
string
default:"async"
required
Result delivery mode. Use
async for polling with statusTask, or callback for webhook delivery.string
Required when
request_type is callback. Must be a public HTTPS URL that can receive the final task payload. See Webhooks.object
required
Kling 3.0 Turbo input parameters.
Response format
Submit task response
POST /generateTask/kling-3-0-turbo returns a task ID when the task is accepted:
integer
API status code.
200 means the task was accepted.string
Human-readable status message.
string
Unique task identifier used with the status endpoint.
Status response fields
string
Unique task identifier.
string
Current task state:
pending, processing, success, or failed.string
JSON string containing the generated video URLs. Present when
state is success.string
Machine-readable failure code. Present when
state is failed.string
Human-readable failure message. Present when
state is failed.integer
Task creation timestamp in Unix milliseconds.
integer
Task completion timestamp in Unix milliseconds. Present after completion.
integer
Processing duration in milliseconds. Present after successful completion when available.
Webhook callback mode
Use callback mode when your backend should receive the final result automatically instead of polling.code, message, and data shape as the status response. See Webhooks for delivery requirements and retry behavior.
Billing
Kling 3.0 Turbo is billed per output second.text-to-video and image-to-video use the same pricing, and total cost is unit price * duration.
For current route and market comparison pricing, see Pricing.
Latency and polling
Actual latency may vary by prompt complexity, selected resolution, route, and current queue load.
Rate limits and concurrency can vary by account, API key, and route. If you receive
429, slow down requests and retry with backoff. For account-level details, see System APIs.
Errors and troubleshooting
HTTP errors
Task failure codes
Common validation issues
See Error Codes for the full error reference.