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
Result delivery mode. Use
async for polling with statusTask, or callback for webhook delivery.Required when
request_type is callback. Must be a public HTTPS URL that can receive the final task payload. See Webhooks.Response format
Submit task response
POST /generateTask/kling-3-0-turbo returns a task ID when the task is accepted:
Status response fields
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
New non-LLM requests use 1 credit =$0.001. Calculate the full amount, including billable quantity and add-ons, apply the applicable account discount, then round the request total upward to the next whole credit. Agreed fixed unit prices retain their precision and replace the standard price and discount; final rounding still applies. See credit conversion and rounding.
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 API rates in USD, see API 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.
MCP integration
The complete model schema declares result decoding inmcp.result and supported file bindings in mcp.attachments. These are client integration metadata, not generation input parameters. Attachment paths: image_urls. Preserve the user’s file order. Model parameter validation remains on the API.