TON (v3) RPC Endpoint

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

TON (v3) mainnet RPC URL: https://rpc.swiftnodes.io/rpc/tonv3/<method>?key=YOUR_API_KEY

Get your free TON (v3) API key

250,000 requests/month · 20 req/s · all chains · no card · no KYC

Get my free API key →

TON (v3) serves the same TON mainnet through the TON Center v3 HTTP API. It is a separate SwiftNodes chain slug so applications can move to the v3 method names and response shapes without changing the v2 route they already depend on. Requests go to /rpc/tonv3/<method> with the same API key and billing.

Network: TON (v3)
Type: Non-EVM
Slug: tonv3
Native token: TON (Toncoin)
Block time: ~0.4 seconds
Finality: ~0.6 seconds
Mainnet: 2020
Category: Layer 1 (Proof-of-Stake, sharded, TVM)

TON (v3) on the SwiftNodes fleet, right now

Status: online
Latency: 56 ms
Latest block: 107,083,673
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 (v3)

TON is a sharded proof-of-stake Layer 1 built around the TVM and the jetton token standard. The v2 and v3 routes address the same network; the difference is the upstream HTTP API version and its path names.

Use TON (v3) when your client has already moved to TON Center v3 method names such as /masterchainInfo. Keep TON (v2) for older SDKs and integrations that still call /getMasterchainInfo and the v2 response envelope.

Common Use Cases on TON (v3)

  • TON Center v3 wallet and account lookups
  • Jetton transfers and wallet balances
  • Telegram Mini Apps and consumer payments
  • DEX trading on STON.fi and DeDust
  • TON DNS and account lookups

TON (v3) Mainnet RPC URL (HTTP)

https://rpc.swiftnodes.io/rpc/tonv3/<method>?key=YOUR_API_KEY

TON (v3) WebSocket RPC URL

TON is served through its HTTP REST API. There is no WebSocket subscription endpoint for TON on SwiftNodes; poll the REST method you need instead.

Quick Start: Connect to TON (v3)

HTTP REST

TON methods are paths after the chain name, not JSON-RPC methods in a request body. Start with the masterchain head:

curl "https://rpc.swiftnodes.io/rpc/tonv3/masterchainInfo?key=YOUR_API_KEY"

Address and account reads follow the same shape:

curl "https://rpc.swiftnodes.io/rpc/tonv3/addressInformation?address=EQCD39VS5jcptHL8vMjEXrzGaRcCVYto7HUn4bpAOg8xqB2N&key=YOUR_API_KEY"

TON uses its own REST and JSON shapes. The full method list is in the TON documentation.

Get your free TON (v3) 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 →

Features of SwiftNodes for TON (v3)

  • 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 REST API support (no WebSocket endpoint)
  • One API key works across all 139 supported chains and their testnets, including TON (v3)

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 (v3)

What is the difference between TON (v2) and TON (v3)?

They serve the same TON mainnet. TON (v2) uses the TON Center v2 API paths, such as /getMasterchainInfo. TON (v3) uses the TON Center v3 API paths, such as /masterchainInfo, and keeps the same API key, auth header and billing.

What is the TON (v3) endpoint?

Append the v3 method to the chain path, for example https://rpc.swiftnodes.io/rpc/tonv3/masterchainInfo?key=YOUR_API_KEY. Send the key as the key query parameter or the x-api-key header.

Does TON use JSON-RPC?

No. TON's public API is HTTP/REST, not JSON-RPC. JSON-RPC clients need an adapter or a TON-specific SDK.

Does SwiftNodes support a TON WebSocket endpoint?

TON is served over its HTTP REST API. There is no WebSocket subscription endpoint for TON on this route.

Related chains

Explore RPC endpoints for other networks on SwiftNodes:

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