API Reference

Delete API keys in a batch

Delete API keys in a batch within the current credential scope.

POST https://api.tu-zi.com/api/token/batch
Preview guide

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

Preview guide

Delete API keys in a batch

Updated · Reviewed

Endpoint and authentication

POST https://api.tu-zi.com/api/token/batch

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
Content-Type: application/json

Minimal request example

{
  "ids": [
    123
  ]
}

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

Deletes owned keys only. Deleted keys stop working; verify IDs first. OAuth application tokens are not accepted here.

Body parameters

FieldTypeRequiredDescription / constraints
idsinteger[]YesUp to 100 owned key IDs, not key strings. Example: [123]

Response fields

FieldTypeDescription / constraints
successbooleanBusiness success.
dataintegerNumber deleted.

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

{
  "success": true,
  "data": 1
}

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.