Skip to main content

GET

PathDescriptionEst. CU
direct/v1/TonAPI/v2/accounts/
/jettons/history
Get the transfer jettons history for account20
direct/v1/TonAPI/v2/accounts//nfts
/history
Get the transfer nft history20
direct/v1/TonAPI/v2/accounts//tracesGet traces for account20
direct/v1/TonAPI/v2/blockchain/accounts
//transactions
Get account transactions20
direct/v1/TonAPI/v2/blockchain/blocks/Get blockchain block data20
direct/v1/TonAPI/v2/blockchain/blocks/
/transactions
Get transactions from block20
direct/v1/TonAPI/v2/blockchain/masterchain
//transactions
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.20
direct/v1/TonAPI/v2/blockchain/transactions
/
Get transaction data20
direct/v1/TonAPI/v2/blockchain/messages/
/transaction
Get transaction data by message hash20
direct/v1/TonAPI/v2/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.20
direct/v1/TonAPI/v2/nfts//historyGet the transfer nfts history for account20
direct/v1/TonAPI/v2/liteserver
/list_block_transactions/
Get raw list block transactions20
direct/v1/TonAPI/v2/liteserver/get_transactions
/
Get raw transactions20
direct/v1/TonAPI/v2/traces/Get the trace by trace ID or hash of any transaction in trace20

POST

PathDescriptionEst. CU
direct/v1/TonAPI/v2/traces/emulateEmulate sending message to blockchain20