API Reference

Manually refresh a not-started task

Manually refresh a not-started task. Returns data visible to the current account.

POST https://api.tu-zi.com/api/task/{task_id}/poll
Preview guide

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

Preview guide

Manually refresh a not-started task

Updated · Reviewed

Endpoint and authentication

POST https://api.tu-zi.com/api/task/{task_id}/poll

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

Only for NOT_START tasks with persisted upstream identity, supported polling and valid permissions. This is not normal result retrieval or generation retry. Per-task cooldown is 30 seconds (429/Retry-After); changed state or missing upstream identity returns 409, unsupported tasks 400, invisible tasks 404. Success still requires checking final completion.

Path parameters

FieldTypeRequiredDescription / constraints
task_idstringYesGateway task ID belonging to this account. Example: YOUR_TASK_ID

Response fields

FieldTypeDescription / constraints
successbooleanBusiness success; do not rely only on HTTP status.
messagestringResult or error message.
data.task_idstringGateway task ID.
data.statusstringTask status after refresh.
data.progressstringProgress after refresh.

Illustrative response; some endpoints show essential fields only. Optional fields may be absent.

{
  "success": true,
  "data": {
    "task_id": "YOUR_TASK_ID",
    "status": "IN_PROGRESS",
    "progress": "10%"
  }
}

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.