getextendedaddressinformation - TON

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

This method returns extended information about a TON address, including parsed details for known contract types. It is based on tonlib's getAccountState function and provides more structure than getAddressInformation. For detecting wallets specifically, prefer getWalletInformation.

Parameters

Parameter
Type
Required
Description

address

string

Yes

Identifier of the target TON account in any form

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>/getExtendedAddressInformation?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": "getExtendedAddressInformation",
    "params": {
        "address": "EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2"
    },
    "id": "getblock.io"
}'

Response Example

Response Parameters

Field
Type
Description

ok

boolean

Whether the request succeeded

result.address.account_address

string

User-friendly representation of the account address

result.balance

string

Balance in nanotons

result.account_state.@type

string

Parsed account state type (e.g. wallet.v4.accountState)

result.account_state.seqno

integer

Wallet seqno for wallet contracts (used as nonce when sending)

result.account_state.wallet_id

string

Wallet subwallet identifier where applicable

result.revision

integer

Contract revision number for typed contracts

result.sync_utime

integer

Unix timestamp at which state was synchronised

Use Cases

  • Detecting wallet type and version (v3, v4, w5, etc.)

  • Retrieving wallet seqno before constructing a transfer

  • Building explorers that show parsed contract state

  • Validating known contract types 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?