API Reference
Retrieve a Kling videos task
Retrieve a Kling videos task. The following is this gateway’s public contract.
Preview guide
Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.
Updated · Reviewed
Endpoint and authentication
GET https://api.tu-zi.com/kling/v1/videos/{kind}/{task_id}
Transport: json
Use an inference API key. Examples contain placeholders; read credentials from environment variables.
Authorization: Bearer YOUR_API_KEY
Before running
Replace https://api.tu-zi.com with this site origin (do not append /v1 twice), and YOUR_MODEL with the exact marketplace model ID. Install requests for Python; use Node.js 20+ and save JavaScript as .mjs. WebSocket samples list their own dependencies.
Create an inference key on the site and set API_KEY in the environment; replace YOUR_API_KEY in cURL. Prepare local input.png/input.wav files for upload examples.
Start with a minimal request, then read the result using the response fields below. For async APIs, a returned task ID requires polling; acceptance does not mean generation has finished.
Constraints
Keep the creation operation in the path, such as text2video. This gateway returns its generic TaskDto with uppercase states, not the direct Kling data.task_status shape. Read output URLs only after successful generation.
Path parameters
| Field | Type | Required | Description / constraints |
|---|---|---|---|
| kind | string | Yes | Operation path segment used at creation. Example: text2video |
| task_id | string | Yes | Public task ID returned by this gateway. Example: YOUR_TASK_ID |
Response fields
| Field | Type | Description / constraints |
|---|---|---|
| code | string | success for a successful query. |
| data.task_id | string | Public gateway task ID. |
| data.status | string | SUBMITTED, QUEUED and IN_PROGRESS are pending; SUCCESS and FAILURE are terminal. |
| data.result_url | string | Media URL when available after success. |
| data.fail_reason | string | Failure reason. |
| data.data | object | array | Protocol-specific result content. |
Illustrative response; some endpoints show essential fields only. Optional fields may be absent.
{
"code": "success",
"message": "",
"data": {
"task_id": "task_example",
"status": "QUEUED",
"data": {}
}
}
Errors and retries
Check HTTP status and protocol-specific errors; do not mix error formats across protocols. For 401/403 check credentials and permissions, for 429 back off, and for 5xx check gateway/upstream status. Error bodies may contain error/message/code depending on the protocol.
Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.
兔子API