Get TRX Historical Price/Volume/Market Cap
1. Overview & Typical Use
Returns historical data for TRX, including price, trading volume, and market capitalization records.
- Typical use: displaying TRX candlestick charts, price trends, and market cap changes.
- When not to use: to view available data sources use “Get TRX Price Data Sources”.
2. Endpoint & Authentication
GET /api/trx/volume
For Base URL and authentication, see Common Network & Authentication.
3. Request
Fields
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
limit | integer | No | 10 | Number of records to return |
start_timestamp | integer | No | — | Start time, millisecond timestamp |
end_timestamp | integer | No | — | End time, millisecond timestamp |
start | integer | No | 0 | Start index |
source | string | No | coinmarketcap | Data source |
4. Response
Fields
Top-level
| Field | Type | Required | Description | Unit/Precision |
|---|---|---|---|---|
lastUpdateSeconds | integer | Required | Data update time | Millisecond timestamp |
total | integer | Required | Total number of data records | — |
code | integer | Required | Status code | — |
message | string | Required | Status message | — |
status | string | Required | Request status; normal is "1" | — |
trx_market_cap_change_ratio | string | Required | Market cap change rate | — |
trx_price_change_ratio | string | Required | Price change rate | — |
data | array | Required | Historical price data list; see below | — |
data[] elements
| Field | Type | Required | Description | Unit/Precision |
|---|---|---|---|---|
volume | string | Required | Daily trading volume | USD |
high | string | Required | High price | USD |
market_cap | string | Required | Market capitalization | USD |
low | string | Required | Low price | USD |
time | integer | Required | Timestamp | Millisecond timestamp |
source | string | Required | Data source | — |
close | string | Required | Closing price | USD |
open | string | Required | Opening price | USD |
5. Errors
For HTTP status codes, see Common Errors. Notes for this endpoint:
- Empty result is not an error: no matches returns
200+data: [], which is a normal response.
Last updated on: