Get Account Daily Analysis Data List

1. Overview & Typical Use

Query the daily analysis data list for an account over a specified time range. Use the type parameter to select different analysis dimensions.

Typical use: account activity trend charts, resource consumption analysis, balance change tracking.
When not to use: for current account status use “Get Account Detail”; for a single transaction use the Transaction & Transfer endpoints.

type values:

`type`	Description
`0`	Balance — daily TRX balance and TRX price (in USDT)
`1`	Token transfers — transfer count (TRX/TRC10/TRC20) and number of unique tokens involved
`2`	Energy consumption — from frozen TRX, TRX burn, and contract deployer; plus total
`3`	Bandwidth consumption — from frozen TRX or free bandwidth, and TRX burn
`4`	Transactions — number of transactions initiated and received by the account

GET /api/account/analysis

For Base URL and authentication, see Common Network & Authentication.

Parameter	Type	Required	Default	Description
`address`	string	Yes	—	Account address (Base58, starts with T)
`start_timestamp`	integer	Yes	—	Start time, millisecond timestamp
`end_timestamp`	integer	Yes	—	End time, millisecond timestamp
`type`	integer	No	`0`	Analysis type, values `0`–`4`; see table above

The top-level structure is fixed: { "size": <int>, "data": [...] }. Fields in data[] vary by type.

Top-level

Field	Type	Required	Description	Unit/Precision
`size`	integer	Required	Number of returned records	—
`data`	array	Required	Daily analysis data array; see below	—

data[] elements (type=0 balance)

Field	Type	Required	Description	Unit/Precision
`day`	string	Required	Date (`YYYY-MM-DD`)	—
`trx_amount`	string	Required	Daily TRX balance	TRX
`usdt_amount`	string	Required	Equivalent USDT value	USDT
`price`	number	Required	TRX/USDT price	—

data[] elements (type=1 token transfers)

Field	Type	Required	Description	Unit/Precision
`day`	string	Required	Date	—
`transfer_count`	integer	Required	Number of transfers	—
`token_count`	integer	Required	Number of unique tokens involved	—

data[] elements (type=2 energy consumption)

Field	Type	Required	Description	Unit/Precision
`day`	string	Required	Date	—
`energy_usage`	integer	Required	Energy consumed from frozen TRX	—
`energy_burn`	integer	Required	Energy obtained by burning TRX	—
`origin_energy_usage`	integer	Required	Energy covered by the contract deployer	—
`energy_usage_total`	integer	Required	Total energy consumption	—
`energy_usage_as_deploy`	integer	Required	Energy consumed as deployer	—
`energy_total`	integer	Required	Total energy used	—

data[] elements (type=3 bandwidth consumption)

Field	Type	Required	Description	Unit/Precision
`day`	string	Required	Date	—
`net_usage`	integer	Required	Bandwidth from frozen TRX or free allowance	—
`net_burn`	integer	Required	Bandwidth obtained by burning TRX	—
`net_usage_total`	integer	Required	Total bandwidth consumption	—

data[] elements (type=4 transactions)

Field	Type	Required	Description	Unit/Precision
`day`	string	Required	Date	—
`transaction_count`	integer	Required	Transaction count	—

For HTTP status codes, see Common Errors. Notes for this endpoint:

Empty result is not an error: no data in the specified range returns 200 + data: [], which is a normal response.