Get TRX Transfer List for an Address

1. Overview & Typical Use

Query TRX transfer records for a specified address, with support for filtering by direction (in / out), time range, and other conditions.

Typical use: wallet TRX transaction history display, querying inbound/outbound TRX transfer details for an address.
When not to use: for TRC10 token transfers use “Get TRC10 Token Transfer List for an Address”; for TRC20 token transfers use “Get TRC20 Token Transfer List for an Address”.

GET /api/transfer/trx

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

Parameter	Type	Required	Default	Description
`address`	string	Yes	—	Query address
`start`	integer	No	`0`	Start offset; `start + limit ≤ 10000`
`limit`	integer	No	`20`	Page size, max 50
`direction`	integer	No	`1`	Transfer direction: `1` in, `2` out, `0` all
`start_timestamp`	integer	No	`1529769600000`	Start time, ms timestamp
`end_timestamp`	integer	No	—	End time, ms timestamp
`db_version`	integer	No	`0`	Filter invalid transfers
`reverse`	boolean	No	`true`	Sort data in descending order
`fee`	boolean	No	`false`	Whether to return data for TRX burned by resource consumption

Top-level

Field	Type	Required	Description	Unit/Precision
`code`	integer	Required	Status code	—
`page_size`	integer	Required	Number of records returned on the current page	—
`tokenInfo`	object	Required	TRX token metadata (value schema below)	—
`data`	array	Required	Transfer record array; see below	—
`contractMap`	object	Optional	Address → whether it is a contract mapping	—

tokenInfo object schema (9 common fields):

Field	Type	Required	Description	Unit/Precision
`tokenId`	string	Required	Token contract address (Base58); TRX placeholder is `_`	—
`tokenAbbr`	string	Required	Token abbreviation (e.g. `USDT` / `TRX`)	—
`tokenName`	string	Required	Token name	—
`tokenDecimal`	integer	Required	Decimal precision (required to convert the `amount` field)	—
`tokenCanShow`	integer	Required	Whether displayable (`1` yes / `0` no)	—
`tokenType`	string	Required	Token type (`trc10` / `trc20` / `trc721` / `trc1155`)	—
`tokenLogo`	string	Required	Token logo URL	—
`tokenLevel`	string	Required	Token level	—
`vip`	boolean	Required	Whether it is a VIP token	—

data[] elements

Field	Type	Required	Description	Unit/Precision
`hash`	string	Required	Transaction hash	—
`block`	integer	Required	Block height	—
`block_timestamp`	integer	Required	Block time	ms timestamp
`from`	string	Required	Sender address	—
`to`	string	Required	Recipient address	—
`amount`	string	Required	Transfer amount (raw value)	sun
`confirmed`	integer	Required	Confirmation status	—
`contract_type`	string	Required	Contract type string (e.g. `TransferContract`)	—
`contractType`	integer	Required	Contract type number	—
`revert`	integer	Required	Whether reverted	—
`contract_ret`	string	Required	Contract execution result	—
`direction`	integer	Required	Transfer direction	—
`cheatStatus`	boolean	Required	Whether this is a fraudulent transaction	—
`symbol`	string	Required	Token abbreviation (`trx` for TRX)	—
`decimals`	integer	Required	Token decimals	—
`token_name`	string	Required	Token name	—
`issue_address`	string	Required	Token issuer address	—

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

Required parameters: address is required; missing it returns an error.
Parameter violations are not reported as errors: limit > 50, start + limit > 10000, etc. are silently truncated.
Empty result is not an error: no matches returns 200 + data: [], which is a normal response.