API Reference

List top-up records

List top-up records. Fields and permissions follow this gateway implementation.

GET https://api.tu-zi.com/api/user/topup/self

Preview guide

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

# List top-up records

List top-up records. Fields and permissions follow this gateway implementation.

## Endpoint and authentication

`GET https://api.tu-zi.com/api/user/topup/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.

```http
Authorization: Bearer YOUR_SYSTEM_TOKEN
New-Api-User: YOUR_USER_ID
```

## Query parameters

| Field | Type | Required | Description / constraints |
| --- | --- | --- | --- |
| p | integer | No | Page number starting at 1. Example: 1 |
| page_size | integer | No | Page size up to 100; omitted uses the site setting. Example: 10 |
| keyword | string | No | Order search keyword. |

## 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 GET 'https://api.tu-zi.com/api/user/topup/self' \
  --header 'Authorization: Bearer YOUR_SYSTEM_TOKEN' \
  --header 'New-Api-User: YOUR_USER_ID'
```

### python

```python
import json
import os
import requests

url = "https://api.tu-zi.com/api/user/topup/self"
headers = json.loads("{\"Authorization\":\"Bearer YOUR_SYSTEM_TOKEN\",\"New-Api-User\":\"YOUR_USER_ID\"}")
headers["Authorization"] = "Bearer " + os.environ["SYSTEM_TOKEN"]
headers["New-Api-User"] = os.environ["USER_ID"]
response = requests.request("GET", url, headers=headers, 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/user/topup/self";
const headers = {
  "Authorization": "Bearer YOUR_SYSTEM_TOKEN",
  "New-Api-User": "YOUR_USER_ID"
};
headers.Authorization = 'Bearer ' + process.env.SYSTEM_TOKEN;
headers['New-Api-User'] = process.env.USER_ID;
const response = await fetch(url, { method: "GET", headers });
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; do not rely only on HTTP status. |
| message | string | Result or error message. |
| data.page | integer | Current page. |
| data.page_size | integer | Effective page size. |
| data.total | integer | Total records. |
| data.items | array | Records in the current page. |
| data.items[].id | integer | Record ID. |
| data.items[].trade_no | string | Gateway order number. |
| data.items[].amount | number | Recharge amount with legacy storage semantics; do not treat as actual money paid. |
| data.items[].money | number | Order amount; use order_currency. |
| data.items[].order_currency | string | Order currency. |
| data.items[].status | string | Original order status. |
| data.items[].create_time | integer | Creation time, Unix seconds. |
| data.items[].complete_time | integer | Completion time, Unix seconds. |
| data.items[].payment_method | string | Payment method. |
| data.items[].invoice_eligible | boolean | Whether invoice eligible. |

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

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

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

## Documentation source

Definition version: 1

Reviewed: 2026-11-02

Source: https://api.tu-zi.com/en/docs/api/reference-topup-records

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/user/topup/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.

Authorization: Bearer YOUR_SYSTEM_TOKEN
New-Api-User: YOUR_USER_ID

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.

Query parameters

Field	Type	Required	Description / constraints
p	integer	No	Page number starting at 1. Example: 1
page_size	integer	No	Page size up to 100; omitted uses the site setting. Example: 10
keyword	string	No	Order search keyword.

Response fields

Field	Type	Description / constraints
success	boolean	Business success; do not rely only on HTTP status.
message	string	Result or error message.
data.page	integer	Current page.
data.page_size	integer	Effective page size.
data.total	integer	Total records.
data.items	array	Records in the current page.
data.items[].id	integer	Record ID.
data.items[].trade_no	string	Gateway order number.
data.items[].amount	number	Recharge amount with legacy storage semantics; do not treat as actual money paid.
data.items[].money	number	Order amount; use order_currency.
data.items[].order_currency	string	Order currency.
data.items[].status	string	Original order status.
data.items[].create_time	integer	Creation time, Unix seconds.
data.items[].complete_time	integer	Completion time, Unix seconds.
data.items[].payment_method	string	Payment method.
data.items[].invoice_eligible	boolean	Whether invoice eligible.

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

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/user/topup/self' \
  --header 'Authorization: Bearer YOUR_SYSTEM_TOKEN' \
  --header 'New-Api-User: YOUR_USER_ID'

import json
import os
import requests

url = "https://api.tu-zi.com/api/user/topup/self"
headers = json.loads("{\"Authorization\":\"Bearer YOUR_SYSTEM_TOKEN\",\"New-Api-User\":\"YOUR_USER_ID\"}")
headers["Authorization"] = "Bearer " + os.environ["SYSTEM_TOKEN"]
headers["New-Api-User"] = os.environ["USER_ID"]
response = requests.request("GET", url, headers=headers, 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/user/topup/self";
const headers = {
  "Authorization": "Bearer YOUR_SYSTEM_TOKEN",
  "New-Api-User": "YOUR_USER_ID"
};
headers.Authorization = 'Bearer ' + process.env.SYSTEM_TOKEN;
headers['New-Api-User'] = process.env.USER_ID;
const response = await fetch(url, { method: "GET", headers });
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.