account_id

account_ids

block ID: (workchain,shard,seqno,root_hash,file_hash)

block_id

collection

count

accept ton and all possible fiat currencies, separated by commas

currencies

currency

domain filter for current auctions "ton" or "t.me"

domain_name

event ID or transaction hash in hex (without 0x) or base64url format

event_id

exact

from

hash

Show only events that are initiated by this account

initiator

jetton_id

known block: (workchain,shard,seqno,root_hash,file_hash)

known_block

limit

masterchain_seqno

msg_id

method_name

mode

offset

period

public_key

shard

comma separated list supported extensions

supported_extensions

target block: (workchain,shard,seqno,root_hash,file_hash)

target_block

trace ID or transaction hash in hex (without 0x) or base64url format

trace_id

transaction_id

workchain

both a single boc and a batch of boc serialized in base64/hex are accepted

bag-of-cells serialized to base64/hex and additional parameters to configure emulation

Request body for executing a GET method on a blockchain account via POST. This format allows passing arguments in the request body instead of query parameters, which is especially useful for large or complex input data.


Is this account was marked as part of scammers activity

Display name. Data collected from different sources like moderation lists, dns, collections names and over.

An event is built on top of a trace which is a series of transactions caused by one inbound message. TonAPI looks for known patterns inside the trace and splits the trace into actions, where a single action represents a meaningful high-level operation like a Jetton Transfer or an NFT Purchase. Actions are expected to be shown to users. It is advised not to build any logic on top of actions because actions can be changed at any time.

Event is not finished yet. Transactions still happening

shortly describes what this action is about.

a link to an image for this particular action.

a link to an image that depicts this action's asset.

List of critical TON parameters, the change of which significantly affects the network, so more voting rounds are held.

This parameter indicates under what conditions proposals to change the TON configuration are accepted.

The cost of filing complaints about incorrect operation of validators.

The reward in nanoTons for block creation in the TON blockchain.

The limits on the number of validators in the TON blockchain.

The stake parameters configuration in the TON blockchain.

The cost of computations in the masterchain. The complexity of any computation is estimated in gas units.

The cost of computations in the basechains. The complexity of any computation is estimated in gas units.

The limits on the block in the masterchain, upon reaching which the block is finalized and the callback of the remaining messages (if any) is carried over to the next block.

The limits on the block in the basechains, upon reaching which the block is finalized and the callback of the remaining messages (if any) is carried over to the next block.

The cost of sending messages in the masterchain of the TON blockchain.

The cost of sending messages in the basechains of the TON blockchain.

The configuration for the Catchain protocol.

The configuration for the consensus protocol above catchain.

The address of the transaction fee collector.

The configuration for punishment for improper behavior (non-validation). In the absence of the parameter, the default fine size is 101 TON

The size limits and some other characteristics of accounts and messages.

The volume of each of the additional currencies in circulation.

Bridge parameters for wrapping TON in other networks.

Bridge parameters for wrapping tokens from other networks into tokens on the TON network.

The network version and additional capabilities supported by the validators.

List of mandatory parameters of the blockchain config.

Decimal price of the token in the requested currency

date of expiring. optional. not all domain in ton has expiration date

String representation of the value according to the specified type

Data type of the argument value:
- `nan`: Not-a-Number value
- `null`: Null value
- `tinyint`: Decimal integer (e.g., `100500`)
- `int257`: 257-bit integer in hex format with 0x prefix (e.g., `0xfa01d78381ae32`)
- `slice`: TON blockchain address (e.g., `0:6e731f2e...`)
- `cell_boc_base64`: Base64-encoded cell BOC (Binary Object Code) (e.g., `te6ccgEBAQEAAgAAAA==`)
- `slice_boc_hex`: Hex-encoded slice BOC (e.g., `b5ee9c72...`)


list of jettons, any of them can be used to pay for gas

sending excess to this address decreases the commission of a gasless transfer

this field currently returns a cached image URL (e.g., "https://cache.tonapi.io/images/jetton.jpg"). In the future, this will be replaced with the original URL from the metadata. The cached image is already available in the `preview` field of `JettonInfo` and will remain there.

Collection master contract confirmed that this item is part of collection

current nomination cycle ending timestamp

current nomination cycle beginning timestamp

for liquid staking master account of jetton

this pool has verified source code or managed by trusted company

Risk specifies assets that could be lost if a message would be sent to a malicious smart contract. It makes sense to understand the risk BEFORE sending a message to the blockchain.

transfer all the remaining balance of the wallet.

Number of nanocoins to send. Decimal string.

Commission for the transaction. In nanocoins.

Support

REST api to TON blockchain explorer

Get human-friendly information about several accounts without low-level details.

name

Get human-friendly information about an account without low-level details.

start_date

end_date

Get events for an account. Each event is built on top of a trace which is a series of transactions caused by one inbound message. TonAPI looks for known patterns inside the trace and splits the trace into actions, where a single action represents a meaningful high-level operation like a Jetton Transfer or an NFT Purchase. Actions are expected to be shown to users. It is advised not to build any logic on top of actions because actions can be changed at any time.

filter actions where requested account is not real subject (for example sender or receiver jettons)

subject_only

before_lt

Emulate sending message to retrieve account-specific events

ignore_signature_check

Get the transfer history of extra currencies for an account.

Get all Jettons balances by owner address

Get the transfer jettons history for account

Get the transfer jetton history for account and jetton

Selling nft items in ton implemented usually via transfer items to special selling account. This option enables including items which owned not directly.

indirect_ownership

Update internal cache for a particular account

Get low-level information about an account taken directly from the blockchain.

args

Array of method arguments in string format. Supported value formats:
- "NaN" for Not-a-Number type
- "Null" for Null type
- Decimal integers for tinyint type (e.g., "100500")
- 0x-prefixed hex strings for int257 type (e.g., "0xfa01d78381ae32")
- TON blockchain addresses for slice type (e.g., "0:6e731f2e28b73539a7f85ac47ca104d5840b229351189977bb6151d36b5e3f5e")
- Base64-encoded BOC for cell type (e.g., "te6ccgEBAQEAAgAAAA==")
- Hex-encoded BOC for slice type (e.g., "b5ee9c72010101010002000000")

omit this parameter to get last transactions

after_lt

sort_order

used to sort the result-set in ascending or descending order by lt.

Get all blocks in all shards and workchains between target and previous masterchain block according to shards last blocks snapshot in masterchain.  We don't recommend to build your app around this method because it has problem with scalability and will work very slow in the future.

Get blockchain config from a specific block, if present.

Get raw blockchain config from a specific block, if present.

Get all transactions in all shards and workchains between target and previous masterchain block according to shards last blocks snapshot in masterchain. We don't recommend to build your app around this method because it has problem with scalability and will work very slow in the future.

Emulate sending message to retrieve general blockchain events

Get an event either by event ID or a hash of any transaction in a trace. An event is built on top of a trace which is a series of transactions caused by one inbound message. TonAPI looks for known patterns inside the trace and splits the trace into actions, where a single action represents a meaningful high-level operation like a Jetton Transfer or an NFT Purchase. Actions are expected to be shown to users. It is advised not to build any logic on top of actions because actions can be changed at any time.

Returns configuration of gasless transfers

Estimates the cost of the given messages and returns a payload to sign

master_id

Submits the signed gasless transaction message to the network

Get a list of all indexed jetton masters in the blockchain.

Get jetton metadata items by jetton master addresses

Get jetton metadata by jetton master address

Get jetton's custom payload and state init required for transfer

Decode a given message. Only external incoming messages can be decoded currently.

Get NFT collection items by their addresses

Get NFT items from collection by collection address

Get the transfer nfts history for account

Get the token price in the chosen currency for display only. Don’t use this for financial transactions.

accept ton and jetton master addresses, separated by commas

tokens

token

points_count

available_for

return also pools not from white list - just compatible by interfaces (maybe dangerous!)

include_unverified

Get TON storage providers deployed to the blockchain.

Emulate sending message to retrieve with a detailed execution trace

Get the trace by trace ID or hash of any transaction in trace

Emulate sending message to retrieve the resulting wallet state

Get human-friendly information about a wallet without low-level details.

Utilities

Operations

Utilities .swagger-anchor::after { content: url(/assets/swagger-icon.svg); height: 100%; vertical-align: middle; width: 1em; display: inline-block; }

Operations

Utilities