Get Energy and Bandwidth Acquisition Cost Data
1. Overview & Typical Use
Returns the cost to acquire resources such as energy and bandwidth, including staking cost and burn cost.
- Typical use: analyze trends in resource acquisition costs to inform staking or burn decisions.
- When not to use: for energy consumption distribution use “Get Energy Consumption Distribution”.
2. Endpoint & Authentication
GET /api/acquisition_cost_statistic
For Base URL and authentication, see Common Network & Authentication.
3. Request
Fields
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
start_timestamp | integer | No | — | Start time, millisecond timestamp |
end_timestamp | integer | No | Yesterday | End time, millisecond timestamp |
limit | integer | No | 14 | Number of records to return |
4. Response
Fields
Top-level
| Field | Type | Required | Description | Unit/Precision |
|---|---|---|---|---|
total | integer | Required | Number of data records | — |
energy_cost_max | object | Required | Data record with the maximum energy cost | — |
energy_cost_min | object | Required | Data record with the minimum energy cost | — |
net_cost_max | object | Required | Data record with the maximum bandwidth cost | — |
net_cost_min | object | Required | Data record with the minimum bandwidth cost | — |
data | array | Required | Daily cost data list; see below | — |
data[] elements
| Field | Type | Required | Description | Unit/Precision |
|---|---|---|---|---|
day | string | Required | Statistics date | yyyy-MM-dd |
total_energy_cost | number | Required | Energy staking cost | TRX/Energy |
energy_cost_rate | number | Required | Energy cost day-over-day change rate | — |
total_net_cost | number | Required | Bandwidth staking cost | TRX/Bandwidth |
net_cost_rate | number | Required | Bandwidth cost day-over-day change rate | — |
burn_energy_cost | number | Required | Energy burn cost | TRX/Energy |
burn_net_cost | number | Required | Bandwidth burn cost | TRX/Bandwidth |
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: