TON RPC Endpoint

Flat-rate TON RPC provider and TON RPC node access: free tier, no KYC, HTTP.

TON mainnet RPC URL: https://rpc.swiftnodes.io/rpc/ton?key=YOUR_API_KEY

The Open Network (TON) is a sharded Layer 1 blockchain designed for high throughput and sub-second finality, with a native integration into Telegram's mini-app ecosystem. SwiftNodes exposes the TON Center v2 REST and JSON-RPC APIs on mainnet and testnet, so TON SDKs can read accounts, blocks and transactions through the same API key as every other chain.

Network: TON
Type: Non-EVM
Slug: ton
Native token: GRAM (Gram)
Block time: ~400 ms (mainnet, since April 2026)
Finality: Sub-second (~1 s target finalization lag)
Mainnet: November 2019; community relaunch in 2020
Category: Layer 1 (sharded, asynchronous messages, TVM)

TON on the SwiftNodes fleet, right now

Status: online
Latency: 405 ms
Latest block: 101,045,505
WebSocket: not available
Uptime, last 30 days: 100.00%

Status and latency from our health checks, refreshed about every 5 minutes. Uptime history. Network status

About TON

TON uses a masterchain plus dynamically sharded workchains. Smart contracts run in the TON Virtual Machine (TVM) and communicate by asynchronous messages rather than synchronous calls, so a transaction can trigger a chain of messages across shards. The native asset is Gram (GRAM), renamed from Toncoin (TON) on June 15, 2026; the network, addresses and contracts kept the TON name.

The Catchain 2.0 upgrade went live on mainnet in April 2026, cutting the block interval from about 2.5 seconds to roughly 400 ms and reducing the target finalization lag to about one second. TON Center v2 talks directly to liteservers for fresh chain state; the separate v3 indexer adds historical transactions, jettons, NFTs and traces.

Common Use Cases on TON

  • Telegram Mini Apps and TON Connect wallets
  • Jetton (TEP-74) and NFT (TEP-62) transfers
  • High-frequency payments and low-fee settlement
  • On-chain games and consumer apps
  • Account, block and transaction indexing through TON Center

TON Ecosystem

TON's consumer ecosystem is built around Telegram: TON Connect for wallet login, Tonkeeper and MyTonWallet, DEXes such as STON.fi and DeDust, and a large set of Mini Apps. Jettons are the fungible-token standard and NFTs follow TEP-62.

TON Mainnet RPC URL (HTTP)

https://rpc.swiftnodes.io/rpc/ton?key=YOUR_API_KEY

TON WebSocket RPC URL

Not available for TON right now: none of its upstreams currently accepts a subscription in our health checks. Poll the HTTP endpoint above instead.

TON Testnet RPC URL

Same API key, same plan: testnet requests count like any other request.

Testnet
HTTP: https://rpc.swiftnodes.io/rpc/ton-testnet?key=YOUR_API_KEY

Quick Start: Connect to TON

TON Center v2 (REST)

# Masterchain head
curl "https://rpc.swiftnodes.io/rpc/ton/getMasterchainInfo?key=YOUR_API_KEY"

# Account state
curl "https://rpc.swiftnodes.io/rpc/ton/getAddressInformation?address=EQCD39VS5jcptHL8vMjEXrzGaRcCVYto7HUn4bpAOg8xqB2N&key=YOUR_API_KEY"

# JSON-RPC 2.0 facade
curl -X POST "https://rpc.swiftnodes.io/rpc/ton/jsonRPC?key=YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"getMasterchainInfo","params":{}}'

TON uses its own methods, address format and cell/BOC serialization. EVM libraries such as ethers.js and viem do not apply; use a TON SDK such as @ton/ton or tonweb.

Get your free TON API key

30 seconds, no card, no KYC. Sign in with Google, GitHub, email or a wallet. Or try the requests above now with key=demo.

Get a free key →

Bridging to TON

TON connects to other ecosystems through bridges such as the TON Bridge and third-party routes. GRAM is the gas and staking asset; USDT is also issued natively on TON as a Jetton.

REST and JSON-RPC on the same endpoint

TON Center API v2 is a direct liteserver API. REST paths go after the chain slug, for example /rpc/ton/getMasterchainInfo or /rpc/ton/getAddressInformation?address=..., and every v2 method is also available through the JSON-RPC 2.0 facade at /rpc/ton/jsonRPC. The methods are TON-specific: getMasterchainInfo, getAddressInformation, getTransactions, sendBoc and so on. They are not Ethereum eth_* methods.

For indexed history, jettons, NFTs, traces and actions, TON Center v3 is the better data source. v3 is not exposed on this endpoint yet; the current integration is v2, which is what most TON SDKs use for direct chain access.

TON Center v2 documentation →TON Center v3 documentation →

Mainnet and testnet

Mainnet is /rpc/ton and testnet is /rpc/ton-testnet. Both use the same SwiftNodes API key and the same request budget. Testnet is a separate network with its own TON Center API key upstream; testnet GRAM comes from a faucet and has no value.

TON Center applies rate limits per API key. Requests without a key are limited to one request per second, so production workloads should use a key. SwiftNodes keeps the upstream key server-side; clients only send their SwiftNodes key.

Features of SwiftNodes for TON

  • Load-balanced across multiple upstream nodes wherever a chain has more than one, with automatic failover
  • Health-checked every 2 minutes with automatic failover
  • Free tier available — no credit card or KYC required
  • Flat-rate monthly pricing with no per-request fees
  • HTTP support (WebSocket not available for this chain right now)
  • One API key works across all 129 supported chains and their testnets, including TON

Rate Limits

PlanPriceHTTP req/sWS msg/sSign up
Free$0/mo201Start free →
Starter$49/mo7025Choose Starter →
Growth$89/mo15075Choose Growth →
Scale$149/mo300150Choose Scale →
Pro$249/mo600250Choose Pro →

Frequently Asked Questions: TON

Is TON EVM-compatible?

No. TON has its own account model, TVM, address format and cell/BOC serialization. Ethereum JSON-RPC methods such as eth_blockNumber and eth_getBalance do not apply; use a TON SDK or the TON Center methods.

Does TON have a chain ID?

No EVM chain ID. TON distinguishes mainnet and testnet by network, and uses workchain and shard identifiers internally. The masterchain seqno is the block height.

How do I query TON through SwiftNodes?

Use the v2 REST paths after /rpc/ton, for example GET https://rpc.swiftnodes.io/rpc/ton/getMasterchainInfo?key=YOUR_API_KEY, or POST a JSON-RPC 2.0 body to https://rpc.swiftnodes.io/rpc/ton/jsonRPC?key=YOUR_API_KEY. Point a TON SDK's TonClient at https://rpc.swiftnodes.io/rpc/ton and pass your SwiftNodes key as the API key.

What happened to Toncoin?

The TON network kept its name, but the native asset was renamed from Toncoin (TON) to Gram (GRAM) on June 15, 2026. Addresses, contracts and the 9-decimal base unit did not change.

Does SwiftNodes support TON testnet?

Yes. Use https://rpc.swiftnodes.io/rpc/ton-testnet with the same SwiftNodes API key. Testnet is a separate network and uses a separate TON Center API key upstream; testnet GRAM is available from a faucet.

Related chains

Explore RPC endpoints for other networks on SwiftNodes:

Ready to start building on TON? Get a free API key in 30 seconds. No KYC, no card: sign in with Google, GitHub, email or a wallet.