API Reference
Query a Kling element task
Poll a site creation task and retrieve element_id for video generation.
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/v1/general/advanced-custom-elements/{task_id}
Transport: json
Use an inference API key. Examples contain placeholders; read credentials from environment variables.
Authorization: Bearer YOUR_API_KEY
Before calling
- Examples use this site's address. For another gateway, replace only the site address and keep the full endpoint path.
- Use an inference key created on this site's token page. Set the
API_KEYenvironment variable or replaceYOUR_API_KEY, as shown in the selected example.
Constraints
Use the returned element_id in an element item inside contents when calling POST /v1/videos. id names the prompt reference, such as element_1 for @element_1. Only site element_ IDs are accepted, not numeric Kling IDs. Use the same site API key. Up to 7 elements per request; elements and voices in one request must share a route.
Confirming success
Check HTTP status, the business status in the body and the required result fields. Do not rely only on HTTP 200 or the script exit code.
Path parameters
| Field | Type | Required | Description / constraints |
|---|---|---|---|
| task_id | string | Yes | Site task ID returned by creation. Example: task_example |
Response fields
| Field | Type | Description / constraints |
|---|---|---|
| data.task_status | string | submitted / processing / succeed / failed. |
| data.task_result.elements[].element_id | string | Site element_id, only returned on success. |
Illustrative response; some endpoints show essential fields only. Optional fields may be absent.
{
"code": 0,
"message": "SUCCEED",
"data": {
"task_id": "task_example",
"task_status": "succeed",
"task_result": {
"elements": [
{
"element_id": "element_example",
"element_name": "Rabbit"
}
]
}
}
}
Errors and retries
Check HTTP status and protocol-specific errors; do not mix error formats across protocols.
- 401/403: check credentials and permissions.
- 429: classify temporary throttling, exhausted quota, or service capacity failure; only transient failures merit bounded backoff.
- 5xx: inspect the gateway, upstream, and model/channel configuration.
Error bodies may contain error/message/code depending on the protocol.
- Use bounded exponential backoff for reads encountering transient errors; fix parameter, authentication, quota, or configuration failures first.
- Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.
兔子API