Get Stablecoin Key Events
1. Overview & Typical Use
Returns key on-chain events for stablecoins, such as minting (Issue), burning (DestroyedBlackFunds, Redeem), and blacklist additions (AddedBlackList), with optional filters by operator, time range, and amount range. This endpoint requires an API Key; calls without a Key return 401.
- Typical use: monitor large mint/burn events; detect blacklist operations; compliance analysis.
- When not to use: for general transfer records use the TRC20 transfers endpoint.
2. Endpoint & Authentication
GET /api/deep/stableCoin/totalSupply/keyEvents
For Base URL and authentication, see Common Network & Authentication.
This endpoint requires an API Key; calls without a Key return 401.
3. Request
Fields
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
start | integer | Yes | — | Starting index. start + limit must not exceed 10000 |
limit | integer | No | 100 | Number to return, capped at 100 |
sort | integer | Yes | — | 1: by event value in USD; 2: by event time |
operatorAddress | string | No | — | Filter by operator address |
direction | integer | Yes | — | 1: ascending, 2: descending |
startTime | integer | No | — | Start time, inclusive; Unix seconds |
endTime | integer | No | — | End time, inclusive; Unix seconds |
startAmount | number | No | — | Minimum event value in USD, inclusive; nonnegative decimal. Omit for no lower bound |
endAmount | number | No | — | Maximum event value in USD, inclusive; nonnegative decimal. Omit for no upper bound |
USDT | string | No | — | Comma-separated USDT event names, e.g. Issue,Redeem,AddedBlackList |
USDCOLD | string | No | — | Comma-separated legacy USDC event names, e.g. Mint,Burn |
USDD | string | No | — | Comma-separated USDD event names, e.g. Deposit,Withdrawal |
TUSD | string | No | — | Comma-separated TUSD event names, e.g. Mint,Burn |
When any token filter is nonempty, only the specified token/event combinations are included; matches across events and tokens are combined with OR. When all token filters are omitted or empty, the default event sets for these four tokens are used.
4. Response
Fields
Top-level (successful response)
| Field | Type | Required | Description | Unit/Precision |
|---|---|---|---|---|
total | integer | Required | Total matching event count | — |
code | integer | Required | Response code (0 = success, 1 = error) | — |
data | array | Required | Key event list; [] when no events match | — |
refreshTimeInfo | object | Required | Data refresh metadata | — |
data[] element
| Field | Type | Required | Description | Unit/Precision |
|---|---|---|---|---|
tokenName | string | Required | Token symbol, e.g. USDT | — |
tokenAddress | string | Required | Token contract address | — |
eventName | string | Required | Event name (e.g., Issue, Redeem, AddedBlackList) | — |
count | string | Required | Decimal-adjusted token quantity; events without a quantity, such as AddedBlackList, return an empty string "" | Token quantity |
operatorAddress | string | Required | Operator address | — |
time | string | Required | Event time | Unix milliseconds, as a string |
hash | string | Required | Transaction hash | — |
addressTag | string | Optional | Operator address label; omitted when no label is available | — |
refreshTimeInfo object
| Field | Type | Required | Description | Unit/Precision |
|---|---|---|---|---|
type | string | Required | Data refresh type, e.g. realtime | — |
lastUpdateTime | integer | Required | Last update time | Unix seconds |
5. Errors
For HTTP status codes, see Common Errors. Key points for this endpoint:
- API Key Required: returns 401 if
TRON-PRO-API-KEYheader is not provided. - Invalid parameters, such as
sort=time,sort=3, orstartAmount=-1, return HTTP200withcode: 1and amsgdescription.start + limitmust not exceed 10000.