API Reference

Update API keys in a batch

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

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

Preview guide

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

# Update API keys in a batch

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

## Endpoint and authentication

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

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.

```http
Authorization: Bearer YOUR_SYSTEM_TOKEN
New-Api-User: YOUR_USER_ID
Content-Type: application/json
```

## Body parameters

| Field | Type | Required | Description / constraints |
| --- | --- | --- | --- |
| ids | integer[] | Yes | Up to 100 owned key IDs, not key strings. Example: [123] |
| group_action | string | No | Group operation; empty leaves it unchanged. Values: "replace", "append", "remove" |
| group | string | No | Group value for the selected action. |
| quota_action | string | No | Quota operation; empty leaves it unchanged. Values: "set", "add", "subtract", "unlimited" |
| quota | integer | No | set allows 0; add/subtract require a positive value; internal quota units. |
| status | integer | No | 1 enabled, 2 disabled. Values: 1, 2 |

## Minimal request example

```json
{
  "ids": [
    123
  ],
  "quota_action": "set",
  "quota": 0,
  "status": 2
}
```

## 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.

## Code examples

### curl

```bash
curl --request POST 'https://api.tu-zi.com/api/token/batch/update' \
  --header 'Authorization: Bearer YOUR_SYSTEM_TOKEN' \
  --header 'New-Api-User: YOUR_USER_ID' \
  --header 'Content-Type: application/json' \
  --data '{
  "ids": [
    123
  ],
  "quota_action": "set",
  "quota": 0,
  "status": 2
}'
```

### python

```python
import json
import os
import requests

url = "https://api.tu-zi.com/api/token/batch/update"
headers = json.loads("{\"Authorization\":\"Bearer YOUR_SYSTEM_TOKEN\",\"New-Api-User\":\"YOUR_USER_ID\",\"Content-Type\":\"application/json\"}")
headers["Authorization"] = "Bearer " + os.environ["SYSTEM_TOKEN"]
headers["New-Api-User"] = os.environ["USER_ID"]
payload = json.loads("{\"ids\":[123],\"quota_action\":\"set\",\"quota\":0,\"status\":2}")
response = requests.request("POST", url, headers=headers, json=payload, timeout=120)
response.raise_for_status()
result = response.json()
if isinstance(result, dict) and (result.get("success") is False or result.get("error")):
    raise RuntimeError(json.dumps(result, ensure_ascii=False))
print(result)  # Also inspect protocol-specific status/code fields.
```

### javascript

```javascript
// Node.js 20+
const url = "https://api.tu-zi.com/api/token/batch/update";
const headers = {
  "Authorization": "Bearer YOUR_SYSTEM_TOKEN",
  "New-Api-User": "YOUR_USER_ID",
  "Content-Type": "application/json"
};
headers.Authorization = 'Bearer ' + process.env.SYSTEM_TOKEN;
headers['New-Api-User'] = process.env.USER_ID;
const response = await fetch(url, { method: "POST", headers, body: JSON.stringify({
  "ids": [
    123
  ],
  "quota_action": "set",
  "quota": 0,
  "status": 2
}) });
if (!response.ok) throw new Error(await response.text());
const result = await response.json();
if (result?.success === false || result?.error) throw new Error(JSON.stringify(result));
console.log(result); // Also inspect protocol-specific status/code fields.
```

## Response fields

| Field | Type | Description / constraints |
| --- | --- | --- |
| success | boolean | Business success. |
| data.count | integer | Number updated. |

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

```json
{
  "success": true,
  "data": {}
}
```

## 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.

## Constraints

Only owned keys are updated. Preserve explicit zero values. This batch endpoint does not accept OAuth application tokens.

## Documentation source

Definition version: 1

Reviewed: 2026-11-02

Source: https://api.tu-zi.com/en/docs/api/reference-token-batch-update

This export contains documentation and examples only, without real credentials, account data or user requests.

Updated 2026-11-02 · Reviewed 2026-11-02

Endpoint and authentication

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

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
  ],
  "quota_action": "set",
  "quota": 0,
  "status": 2
}

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 owned keys are updated. Preserve explicit zero values. This batch endpoint does not accept OAuth application tokens.

Body parameters

Field	Type	Required	Description / constraints
ids	integer[]	Yes	Up to 100 owned key IDs, not key strings. Example: [123]
group_action	string	No	Group operation; empty leaves it unchanged. Values: "replace", "append", "remove"
group	string	No	Group value for the selected action.
quota_action	string	No	Quota operation; empty leaves it unchanged. Values: "set", "add", "subtract", "unlimited"
quota	integer	No	set allows 0; add/subtract require a positive value; internal quota units.
status	integer	No	1 enabled, 2 disabled. Values: 1, 2

Response fields

Field	Type	Description / constraints
success	boolean	Business success.
data.count	integer	Number updated.

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

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

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.

Document information and sources

Documentation source

Definition version: 1

Reviewed: 2026-11-02

Source: https://api.tu-zi.com/en/docs/api/reference-token-batch-update

This export contains documentation and examples only, without real credentials, account data or user requests.

Request examples

curl --request POST 'https://api.tu-zi.com/api/token/batch/update' \
  --header 'Authorization: Bearer YOUR_SYSTEM_TOKEN' \
  --header 'New-Api-User: YOUR_USER_ID' \
  --header 'Content-Type: application/json' \
  --data '{
  "ids": [
    123
  ],
  "quota_action": "set",
  "quota": 0,
  "status": 2
}'

import json
import os
import requests

url = "https://api.tu-zi.com/api/token/batch/update"
headers = json.loads("{\"Authorization\":\"Bearer YOUR_SYSTEM_TOKEN\",\"New-Api-User\":\"YOUR_USER_ID\",\"Content-Type\":\"application/json\"}")
headers["Authorization"] = "Bearer " + os.environ["SYSTEM_TOKEN"]
headers["New-Api-User"] = os.environ["USER_ID"]
payload = json.loads("{\"ids\":[123],\"quota_action\":\"set\",\"quota\":0,\"status\":2}")
response = requests.request("POST", url, headers=headers, json=payload, timeout=120)
response.raise_for_status()
result = response.json()
if isinstance(result, dict) and (result.get("success") is False or result.get("error")):
    raise RuntimeError(json.dumps(result, ensure_ascii=False))
print(result)  # Also inspect protocol-specific status/code fields.

// Node.js 20+
const url = "https://api.tu-zi.com/api/token/batch/update";
const headers = {
  "Authorization": "Bearer YOUR_SYSTEM_TOKEN",
  "New-Api-User": "YOUR_USER_ID",
  "Content-Type": "application/json"
};
headers.Authorization = 'Bearer ' + process.env.SYSTEM_TOKEN;
headers['New-Api-User'] = process.env.USER_ID;
const response = await fetch(url, { method: "POST", headers, body: JSON.stringify({
  "ids": [
    123
  ],
  "quota_action": "set",
  "quota": 0,
  "status": 2
}) });
if (!response.ok) throw new Error(await response.text());
const result = await response.json();
if (result?.success === false || result?.error) throw new Error(JSON.stringify(result));
console.log(result); // Also inspect protocol-specific status/code fields.