Overview
Access TON data via public liteservers, hosted APIs (TON Center v2/v3, dTON), 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 | dTON |
|---|---|---|---|---|
| Can be self-hosted? | ✅ | ✅ | ✅ | ❌ |
| Open-source | ✅ | ✅ | ✅ | ❌ |
| Indexer1 | ❌ | ❌ | ✅ | ✅ |
| Archival2 | 🟡 Varies | 🟡 Depends on liteserver | ✅ | ✅ |
| Proofs3 | ✅ | ❌ | ❌ | ❌ |
| Mainnet endpoint | Config | Endpoint | Endpoint | GraphQL |
| Testnet endpoint | Config | Endpoint | Endpoint | GraphQL |
| Source / Deploy guide | Run node / liteserver | Deploy | Source | — |
| Documentation | Guide | Docs | Docs | Site |
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 | TON Center |
| Documentation | Docs |