APIs
Available options for reading TON data and interacting with it from the off-chain world
Access TON data via public liteservers, hosted APIs (TON Center v2/v3), or self-hosted options.
For available SDKs that rely on some of these APIs, see the SDK overview in the Applications section.
Comparison table
Requests
| Feature | Public liteservers | TON Center v2 | TON Center v3 |
|---|---|---|---|
| Can be self-hosted? | ✅ | ✅ | ✅ |
| Open-source | ✅ | ✅ | ✅ |
| Indexer1 | ❌ | ❌ | ✅ |
| Archival2 | 🟡 Varies | 🟡 Depends on liteserver | ✅ |
| Proofs3 | ✅ | ❌ | ❌ |
| Mainnet endpoint | Config | Endpoint | Endpoint |
| Testnet endpoint | Config | Endpoint | Endpoint |
| Source / Deploy guide | Run node / liteserver | Deploy | Source |
| Documentation | Guide | Docs | Docs |
1 Indexer means the service maintains its own database derived from blockchain data for richer queries (traces, jettons, NFTs, etc.), beyond raw liteserver RPC.
2 Archival indicates historical data retention. For liteservers, this depends on the node's archival configuration; hosted indexers typically keep full history, but exact retention policies are service-specific.
3 Proofs denote responses that can be verified without trust using cryptographic proofs from the network (liteserver/tonlib-based). HTTP indexers typically do not return proof bundles in their REST/GraphQL responses.
Streaming
| Feature | TON Center Streaming API v2 |
|---|---|
| Protocol compatibility | Native reference implementation |
| Mainnet endpoints | SSE, WebSocket |
| Testnet endpoints | SSE, WebSocket |
| Authentication | API key |
| Documentation | Docs |
TON Center
TON Center is the official provider of HTTP APIs for TON: read blockchain data, query smart contracts, send transactions.
API v2
Direct liteserver for balances, sending transactions, contract queries.
API v3
Indexed database for traces, Jettons, NFTs, and historical queries.
Streaming API v2
Low-latency updates on subscriptions through SSE or WebSockets.