getaddressinformation - TON

Example code for the getaddressinformation JSON-RPC method. Сomplete guide on how to use getaddressinformation JSON-RPC in GetBlock.io Web3 documentation.

This method returns basic information about a TON address, including its balance in nanotons, account state, contract code, contract data, and the identifier of the last transaction. It is the most commonly used method for reading account state on TON.

Parameters

Parameter
Type
Required
Description

address

string

Yes

Identifier of the target TON account in any form (user-friendly EQ… / UQ… or raw workchain:hex)

seqno

integer

No

Masterchain seqno at which to read state. Defaults to the latest block

Request Example

REST (GET):

curl --location --request GET 'https://go.getblock.io/<ACCESS-TOKEN>/getAddressInformation?address=EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2' \
--header 'Content-Type: application/json'

JSON-RPC (POST):

curl --location --request POST 'https://go.getblock.io/<ACCESS-TOKEN>/' \
--header 'Content-Type: application/json' \
--data-raw '{
    "jsonrpc": "2.0",
    "method": "getAddressInformation",
    "params": {
        "address": "EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2"
    },
    "id": "getblock.io"
}'

Response Example

Response Parameters

Field
Type
Description

ok

boolean

Whether the request succeeded

result.balance

string

Account balance in nanotons (1 TON = 10⁹ nanotons)

result.code

string

Account contract code as base64-encoded BOC

result.data

string

Account contract data as base64-encoded BOC

result.last_transaction_id.lt

string

Logical time of the last transaction

result.last_transaction_id.hash

string

Hash of the last transaction (base64)

result.state

string

Account state: active, uninitialized, or frozen

result.sync_utime

integer

Unix timestamp at which state was synchronised

id

string

Request identifier echoed back

jsonrpc

string

JSON-RPC protocol version (2.0)

Use Cases

  • Wallet balance and state displays

  • Smart contract state inspection

  • Determining whether an account is initialised before sending a transaction

  • Indexers and explorers reading account-level data

  • Detecting frozen or uninitialised accounts before interaction

Error Handling

Status Code
Error Message
Cause

403

Forbidden

Missing or invalid <ACCESS-TOKEN>

422

Validation Error

Request parameters are missing or malformed

429

Too Many Requests

Rate limit exceeded for your plan

504

Lite Server Timeout

Upstream TON liteserver timed out

SDK Integration

Last updated

Was this helpful?