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.

# Export current key usage CSV

Export current key usage CSV within the current credential scope.

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

```http
Authorization: Bearer YOUR_API_KEY
```

## Query parameters

| Field | Type | Required | Description / constraints |
| --- | --- | --- | --- |
| start_timestamp | integer | Yes | Start Unix seconds, required. |
| end_timestamp | integer | Yes | End Unix seconds, required; range cannot exceed 90 days. |
| model_name | string | No | Model filter. |
| type | integer | No | Log type filter. |

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

## Code examples

### curl

```bash
curl --request GET 'https://api.tu-zi.com/api/log/token/export?start_timestamp=1700000000&end_timestamp=1700086400' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --output 'usage.csv'
```

### python

```python
import json
import os
import requests

url = "https://api.tu-zi.com/api/log/token/export?start_timestamp=1700000000&end_timestamp=1700086400"
headers = json.loads("{\"Authorization\":\"Bearer YOUR_API_KEY\"}")
headers["Authorization"] = "Bearer " + os.environ["API_KEY"]
response = requests.request("GET", url, headers=headers, timeout=120)
response.raise_for_status()
if "json" in response.headers.get("Content-Type", "").lower():
    raise RuntimeError("Expected binary content, received JSON: " + response.text)
with open("usage.csv", "wb") as output:
    output.write(response.content)
```

### javascript

```javascript
import { writeFile } from 'node:fs/promises';
// Node.js 20+
const url = "https://api.tu-zi.com/api/log/token/export?start_timestamp=1700000000&end_timestamp=1700086400";
const headers = {
  "Authorization": "Bearer YOUR_API_KEY"
};
headers.Authorization = 'Bearer ' + process.env.API_KEY;
const response = await fetch(url, { method: "GET", headers });
if (!response.ok) throw new Error(await response.text());
if ((response.headers.get("content-type") || "").toLowerCase().includes("json")) throw new Error("Expected binary content, received JSON: " + await response.text());
await writeFile("usage.csv", Buffer.from(await response.arrayBuffer()));
```

## Response fields

| Field | Type | Description / constraints |
| --- | --- | --- |
| CSV | binary | UTF-8 CSV on success; failures may be JSON success:false. |

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

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

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

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

## Documentation source

Definition version: 1

Reviewed: 2026-11-02

Source: https://api.tu-zi.com/en/docs/api/reference-usage-token-export

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

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

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.

Query parameters

Field	Type	Required	Description / constraints
start_timestamp	integer	Yes	Start Unix seconds, required.
end_timestamp	integer	Yes	End Unix seconds, required; range cannot exceed 90 days.
model_name	string	No	Model filter.
type	integer	No	Log type filter.

Response fields

Field	Type	Description / constraints
CSV	binary	UTF-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. 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.

Document information and sources

Documentation source

Definition version: 1

Reviewed: 2026-11-02

Source: https://api.tu-zi.com/en/docs/api/reference-usage-token-export

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

Request examples

curl --request GET 'https://api.tu-zi.com/api/log/token/export?start_timestamp=1700000000&end_timestamp=1700086400' \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --output 'usage.csv'

import json
import os
import requests

url = "https://api.tu-zi.com/api/log/token/export?start_timestamp=1700000000&end_timestamp=1700086400"
headers = json.loads("{\"Authorization\":\"Bearer YOUR_API_KEY\"}")
headers["Authorization"] = "Bearer " + os.environ["API_KEY"]
response = requests.request("GET", url, headers=headers, timeout=120)
response.raise_for_status()
if "json" in response.headers.get("Content-Type", "").lower():
    raise RuntimeError("Expected binary content, received JSON: " + response.text)
with open("usage.csv", "wb") as output:
    output.write(response.content)

import { writeFile } from 'node:fs/promises';
// Node.js 20+
const url = "https://api.tu-zi.com/api/log/token/export?start_timestamp=1700000000&end_timestamp=1700086400";
const headers = {
  "Authorization": "Bearer YOUR_API_KEY"
};
headers.Authorization = 'Bearer ' + process.env.API_KEY;
const response = await fetch(url, { method: "GET", headers });
if (!response.ok) throw new Error(await response.text());
if ((response.headers.get("content-type") || "").toLowerCase().includes("json")) throw new Error("Expected binary content, received JSON: " + await response.text());
await writeFile("usage.csv", Buffer.from(await response.arrayBuffer()));