API Reference

Query a Kling voice task

Poll a site creation task and retrieve voice_id for video generation.

GET https://api.tu-zi.com/v1/general/custom-voices/{task_id}
Preview guide

Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.

Preview guide

Query a Kling voice task

Updated · Reviewed

Endpoint and authentication

GET https://api.tu-zi.com/v1/general/custom-voices/{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_KEY environment variable or replace YOUR_API_KEY, as shown in the selected example.

Constraints

Use the returned voice_id in a voice item inside contents when calling POST /v1/videos. id names the prompt reference, such as voice_1 for @voice_1. Audio URLs are not accepted in voice items. Use the same site API key. This applies to standard kling-4.0; Flash does not support direct voice references.

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

FieldTypeRequiredDescription / constraints
task_idstringYesSite task ID returned by creation. Example: task_example

Response fields

FieldTypeDescription / constraints
data.task_statusstringsubmitted / processing / succeed / failed.
data.task_result.voices[].voice_idstringSite voice_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": {
      "voices": [
        {
          "voice_id": "voice_example",
          "voice_name": "My voice"
        }
      ]
    }
  }
}

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.