The Open Network (TON)
GetBlock provides fast and reliable access to TON RPC nodes via JSON-RPC API. Connect to the TON network without running your own infrastructure.
The Open Network (TON) is a high-performance, decentralized Layer 1 blockchain originally designed by Telegram developers Nikolai and Pavel Durov and now maintained by the independent TON Foundation and community. Built around a sharded multi-blockchain architecture and Byzantine Fault Tolerant Proof-of-Stake consensus, TON is designed to scale horizontally through dynamic sharding while maintaining ~5-second block times on its masterchain. The network is natively integrated with Telegram’s 800M+ user base and powers payments, DeFi, NFTs, and decentralized services such as TON DNS, TON Sites, and TON Storage.
Key Features
Dynamic Sharding: Masterchain coordinates a configurable set of workchains, each of which can split into shardchains as load increases — enabling horizontal scalability
High Throughput: Architecture designed for parallel transaction processing across shards, with documented benchmarks above 100,000 TPS
Fast Finality: ~5 second masterchain block times with deterministic finality
BFT Proof-of-Stake: Validators are elected from stakers and rotate every election cycle
TON Virtual Machine (TVM): Stack-based VM that runs smart contracts compiled from FunC, Tact, or Tolk — not EVM-compatible
Native Token Standards: Jettons (TIP-3 fungible tokens) and NFTs (TIP-4 non-fungible tokens)
Toncoin (TON): Native gas and staking token, 9 decimals (1 TON = 1,000,000,000 nanotons)
Telegram Integration: First-class integration with the Telegram Mini Apps platform and TON Connect wallet protocol
Low Fees: Sub-cent transaction fees for typical wallet and contract operations
Decentralized Services: TON DNS, TON Sites, TON Storage, and TON Proxy for fully on-chain web infrastructure
TECHNICAL DISCLAIMER: AUTHORITATIVE TON HTTP API SPECIFICATION
GetBlock’s TON API reference documentation is provided exclusively for informational purposes and to optimize the developer experience. The canonical and normative specification for the TON HTTP API (v2) is maintained by TON Foundation and published at toncenter.com/api/v2/ with the upstream source at github.com/toncenter/ton-http-api. For underlying protocol details, consult the official TON documentation at docs.ton.org.
Network Information
Network Name
TON Mainnet
Native Currency
Toncoin (TON)
Decimals
9 (1 TON = 1,000,000,000 nanotons)
Block Time
~5 seconds (masterchain)
Consensus
Byzantine Fault Tolerant Proof-of-Stake
Architecture
Sharded — masterchain (workchain -1) + workchains
Smart Contract VM
TVM (TON Virtual Machine)
EVM Compatible
No
Address Format
User-friendly (EQ… / UQ…) or raw (workchain:hex)
Base URL
The TON HTTP API exposes every method on two parallel transports behind your endpoint:
REST (GET):
GET https://go.getblock.io/<ACCESS-TOKEN>/<method>?<query-params>JSON-RPC (POST):
POST https://go.getblock.io/<ACCESS-TOKEN>/jsonRPCwith a standard JSON-RPC 2.0 body
A handful of state-mutating methods (sendBoc, sendBocReturnHash, runGetMethod, runGetMethodStd, estimateFee) are POST-only.
Supported Networks
Mainnet
✅
✅
✅
✅
Quickstart
In this section, you will learn how to make your first call with either:
Axios (JavaScript / Node.js)
Python (Requests library)
Before you begin, you must have already installed npm or yarn on your local machine (for the Axios example) or Python and pip (for the Python example).
Available API Methods
GetBlock provides access to the full TON HTTP API v2 surface — every method is available both as a REST GET and as a JSON-RPC POST to /jsonRPC, except for the POST-only methods marked below.
Account Methods
getAddressInformation
Get basic information about an address
getExtendedAddressInformation
Get extended information about an address
getWalletInformation
Get wallet-specific information about an address
getAddressBalance
Get address balance in nanotons
getAddressState
Get address state (active, uninitialized, or frozen)
getShardAccountCell
Get the raw TVM cell representing the shard account
getTokenData
Get Jetton or NFT metadata from a token smart contract
Block Methods
getMasterchainInfo
Get up-to-date masterchain state
getMasterchainBlockSignatures
Get validator signatures for a masterchain block
getShardBlockProof
Get the Merkle proof of a shardchain block
getConsensusBlock
Get the block confirmed by consensus
lookupBlock
Look up a block by seqno, shard, and workchain
getShards
Get shards info by masterchain block seqno
getBlockHeader
Get block header information
getOutMsgQueueSize
Get the size of the outbound message queue
Transaction Methods
getTransactions
Get transactions for a specified address
getTransactionsStd
Standardized version of getTransactions
getBlockTransactions
Get transactions in a specified block
getBlockTransactionsExt
Get transactions in a block with extended information
tryLocateTx
Locate the outgoing transaction at the destination by inbound message
tryLocateResultTx
Same as tryLocateTx — locate the outgoing transaction
tryLocateSourceTx
Locate the source transaction by destination transaction parameters
Configuration Methods
getConfigParam
Get a single blockchain configuration parameter
getConfigAll
Get all blockchain configuration parameters
getLibraries
Get library code by their hashes
Run-Method (POST only)
runGetMethod
Run a get-method of a smart contract
runGetMethodStd
Standardized version of runGetMethod
Send Methods (POST only)
sendBoc
Send a Bag of Cells (signed message) to the chain
sendBocReturnHash
Send a BoC and return its hash for tracking
estimateFee
Estimate fees for a given message
Utility Methods
detectAddress
Get all possible forms of a TON address
detectHash
Get all possible forms of a 256-bit hash
packAddress
Pack an address into base64 form
unpackAddress
Unpack an address from base64 form
JSON-RPC Endpoint
jsonRPC
Generic JSON-RPC 2.0 entrypoint — all of the methods above are callable here
Support
For technical support and questions:
Support Email: support@getblock.io
See Also
Last updated
Was this helpful?