API Reference
Rotate system token
Rotate system token. Returns data visible to the current account.
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/api/user/token
Transport: json
Use an account system token and New-Api-User (account ID), or a valid site login session. Manage system tokens in account settings. Inference API keys are not substitutes.
Authorization: Bearer YOUR_SYSTEM_TOKEN
New-Api-User: YOUR_USER_ID
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.
Set SYSTEM_TOKEN and USER_ID in the environment; keep system tokens out of frontend code. Replace YOUR_SYSTEM_TOKEN and YOUR_USER_ID in cURL.
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
The value is an account credential, not an inference key. Store it only on a trusted backend; never send it to an AI or public logs. Sign in through account settings to obtain the initial credential. This GET mutates the credential and invalidates the old token. Never prefetch, automatically retry, or use it as a health check. Use /api/user/token/current for a read.
Request parameters
No request body is needed; send the authentication described above.
Response fields
| Field | Type | Description / constraints |
|---|---|---|
| success | boolean | Business success; do not rely only on HTTP status. |
| message | string | Result or error message. |
| data | string | System token; the read endpoint can return an empty string when none exists. |
Illustrative response; some endpoints show essential fields only. Optional fields may be absent.
{
"success": true,
"data": "YOUR_SYSTEM_TOKEN"
}
Errors and retries
Check HTTP status and success. Business validation errors may return HTTP 200 with {"success":false,"message":"..."}; some include error.code. Authentication may return 401/403 and rate limiting 429. HTTP 200 alone does not guarantee success.
Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.
兔子API