API Reference

Get account quota history

Get account quota history. Returns data visible to the current account.

GET https://api.tu-zi.com/api/data/self
Preview guide

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

Preview guide

Get account quota history

Updated · Reviewed

Endpoint and authentication

GET https://api.tu-zi.com/api/data/self

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; keep system tokens out of frontend code.

Authorization: Bearer YOUR_SYSTEM_TOKEN
New-Api-User: YOUR_USER_ID

Before calling

  • Examples use this site's address. For another gateway, replace only the site address and keep the full endpoint path.
  • Python / JavaScript read SYSTEM_TOKEN (account system token) and USER_ID (account ID) from the environment. In cURL, replace YOUR_SYSTEM_TOKEN and YOUR_USER_ID.

Constraints

Maximum range is 2592000 seconds (30 days). Historical aggregates may lag and do not replace the current balance.

Query parameters

FieldTypeRequiredDescription / constraints
start_timestampintegerYesStart time in Unix seconds. Example: 1793491200
end_timestampintegerYesEnd time in Unix seconds, after the start. Example: 1793577600
default_timestringNoday groups by day, week by week; any other or omitted value uses one-hour buckets. Values: "hour", "day", "week"

Response fields

FieldTypeDescription / constraints
successbooleanBusiness success; do not rely only on HTTP status.
messagestringResult or error message.
dataarrayHistorical aggregate rows; may be empty.
data[].user_idintegerAccount ID.
data[].model_namestringModel name.
data[].created_atintegerTimestamp in Unix seconds.
data[].token_usedintegerTokens used.
data[].countintegerCall count.
data[].quotaintegerQuota used in internal units.

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.