🔍 Get account information

Code samples

GET /api/v1/trx/account/{address}

curl 'https://settla.net/api/v1/trx/account/TMuA6YqfCeX8EhbfYEg5y7S4DqzSJireY9' \
  -H 'X-API-Key: $SETTLA_API_KEY' \
  -H 'Accept: application/json'

Returns the raw account record from the node (/wallet/getaccount): TRX balance, resource counters, permissions and the full TRC10 holdings. Two things to plan for. The field set is not fixed — the node omits anything that is zero or unset, so owner_permission, active_permission, latest_withdraw_time and others are simply absent on many accounts; always read defensively. And assetV2 lists every TRC10 token ever airdropped to the address, which on mainnet is routinely 250–300 entries, so this response is tens of kilobytes. For a symbol-resolved view use GET /api/v1/trx/account/{address}/assets instead. An address that has never appeared on chain answers 200 with an empty array [].

🛠️ Parameters

Name	In	Type	Required	Description
address	path	string	true	Base58 Tron address.

Example responses

200 Response

{
  "address": "TMuA6YqfCeX8EhbfYEg5y7S4DqzSJireY9",
  "balance": 35216519,
  "create_time": 1533891702000,
  "latest_opration_time": 1729421388000,
  "latest_withdraw_time": 1635774720000,
  "latest_consume_time": 1780501704000,
  "latest_consume_free_time": 1729421289000,
  "net_window_size": 28800000,
  "net_window_optimized": true,
  "account_resource": {
    "latest_consume_time_for_energy": 1785534303000,
    "energy_window_size": 28800000,
    "energy_window_optimized": true
  },
  "frozenV2": [
    [],
    {
      "type": "ENERGY"
    },
    {
      "type": "TRON_POWER"
    }
  ],
  "assetV2": [
    {
      "key": "1004108",
      "value": 10399700
    },
    {
      "key": "1001510",
      "value": 100
    }
  ],
  "free_asset_net_usageV2": [
    {
      "key": "1004108",
      "value": 0
    },
    {
      "key": "1001510",
      "value": 0
    }
  ],
  "asset_optimized": true
}

500 Response

{
  "error": "Could not connect to TRX node."
}

🔁 Responses

Status	Meaning	Description	Schema
200	OK	Account details	Inline
500	Internal Server Error	Could not connect to TRX node	Inline

🔄 Response Schema

Status Code 200

Name	Type	Required	Restrictions	Description
» address	string	false	none	none
» balance	integer(int64)	false	none	TRX balance in SUN.
» create_time	integer(int64)	false	none	Milliseconds since the Unix epoch.
» latest_opration_time	integer(int64)	false	none	Spelled `opration` — this is java-tron's own typo, reproduced verbatim. There is no `latest_operation_time` field.
» latest_withdraw_time	integer(int64)	false	none	none
» latest_consume_time	integer(int64)	false	none	none
» latest_consume_free_time	integer(int64)	false	none	none
» net_window_size	integer	false	none	none
» net_window_optimized	boolean	false	none	none
» account_resource	object	false	none	Energy counters.
» owner_permission	object	false	none	Absent on accounts that never customised their permissions.
» active_permission	[object]	false	none	none
» frozenV2	array	false	none	Staked positions. Note the mixed shape — the first element is an array, the rest are objects.
» assetV2	[object]	false	none	Every TRC10 token the address holds, as `{key, value}` where `key` is the numeric token id. Routinely 250–300 entries on mainnet because of airdrop spam; use `GET /api/v1/trx/account/{address}/assets` for a symbol-resolved view.
»» key	string	false	none	none
»» value	integer	false	none	none
» free_asset_net_usageV2	[object]	false	none	Free bandwidth used per TRC10 token, same keying as `assetV2`.
» asset_optimized	boolean	false	none	none

Status Code 500

Name	Type	Required	Restrictions	Description
» error	string	false	none	none
» details	object	false	none	Present only on a few validation errors.