API Reference

Export current key usage CSV

Export current key usage CSV within the current credential scope.

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

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

Preview guide

Export current key usage CSV

Updated · Reviewed

Endpoint and authentication

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

Transport: json

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

Authorization: Bearer YOUR_API_KEY

Before calling

  • Examples use this site's address. For another gateway, replace only the site address and keep the full endpoint path.
  • Use an inference key created on this site's token page. Set the API_KEY environment variable or replace YOUR_API_KEY, as shown in the selected example.

Constraints

  • Replace example timestamps with the required Unix-second range.
  • Account exports use a system token; key exports use that key.
  • Check status and Content-Type before saving the CSV.

Confirming success

Check HTTP status, the business status in the body and the required result fields. Do not rely only on HTTP 200 or the script exit code.

Query parameters

FieldTypeRequiredDescription / constraints
start_timestampintegerYesStart Unix seconds, required.
end_timestampintegerYesEnd Unix seconds, required; range cannot exceed 90 days.
model_namestringNoModel filter.
typeintegerNoLog type filter.

Response fields

FieldTypeDescription / constraints
CSVbinaryUTF-8 CSV on success; failures may be JSON success:false.

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

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

Errors and retries

Check HTTP status and protocol-specific errors; do not mix error formats across protocols.

  • 401/403: check credentials and permissions.
  • 429: classify temporary throttling, exhausted quota, or service capacity failure; only transient failures merit bounded backoff.
  • 5xx: inspect the gateway, upstream, and model/channel configuration.

Error bodies may contain error/message/code depending on the protocol.

  • Use bounded exponential backoff for reads encountering transient errors; fix parameter, authentication, quota, or configuration failures first.
  • Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.