API Reference

Retrieve usage logs for the current API key

List usage logs. Fields and permissions follow this gateway implementation.

GET https://api.tu-zi.com/api/log/token
Preview guide

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

Preview guide

Retrieve usage logs for the current API key

Updated · Reviewed

Endpoint and authentication

GET https://api.tu-zi.com/api/log/token

Transport: json

Use an inference API key. Examples contain placeholders; read credentials from environment variables.

Authorization: Bearer YOUR_API_KEY

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.

Create an inference key on the site and set API_KEY in the environment; replace YOUR_API_KEY in cURL. Prepare local input.png/input.wav files for upload examples.

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

Use an inference key; only its logs are returned. The example explicitly paginates; omitting all pagination parameters returns a legacy array shape.

Query parameters

FieldTypeRequiredDescription / constraints
pintegerNoPage number starting at 1. Example: 1
page_sizeintegerNoPage size up to 100; omitted uses the site setting. Example: 10
typeintegerNo0 all; 1 top-up, 2 usage, 3 management, 4 system, 5 referral, 6 error, 7 refund.
start_timestampintegerNoStart Unix timestamp in seconds.
end_timestampintegerNoEnd Unix timestamp in seconds.
model_namestringNoModel-name filter.
groupstringNoGroup filter.
request_idstringNoGateway request ID.
upstream_request_idstringNoUpstream request ID.
request_pathstringNoEndpoint path; requires a bounded time range. Supply both bounds, no more than 90 days apart.

Response fields

FieldTypeDescription / constraints
successbooleanBusiness success; do not rely only on HTTP status.
messagestringResult or error message.
data.pageintegerCurrent page.
data.page_sizeintegerEffective page size.
data.totalintegerTotal records.
data.itemsarrayRecords in the current page.
data.items[].idintegerLog ID.
data.items[].created_atintegerUnix seconds.
data.items[].model_namestringModel name.
data.items[].quotaintegerConsumed quota in site units.
data.items[].prompt_tokensintegerInput tokens.
data.items[].completion_tokensintegerOutput tokens.
data.items[].is_streambooleanWhether streaming.
data.items[].request_idstringRequest ID.
data.items[].otherstringJSON-encoded extra metadata; inspect fields before use.

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

{
  "success": true,
  "message": "",
  "data": {
    "page": 1,
    "page_size": 10,
    "total": 0,
    "items": []
  }
}

Errors and retries

Check HTTP status and protocol-specific errors; do not mix error formats across protocols. For 401/403 check credentials and permissions, for 429 back off, and for 5xx check gateway/upstream status. Error bodies may contain error/message/code depending on the protocol.

Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.