Overview

Access TON data via public liteservers, hosted APIs (TON Center v2/v3, TonAPI, dTON), or self-hosted options.

Comparison table

Requests

Feature	Public liteservers	TON Center v2	TON Center v3	TonAPI	dTON
Can be self-hosted?	✅	✅	✅	❌	❌
Open-source	✅	✅	✅	🟡 Limited1	❌
Indexer2	❌	❌	✅	✅	✅
Archival3	🟡 Varies	🟡 Depends on liteserver	✅	✅	✅
Proofs4	✅	❌	❌	❌	❌
Mainnet endpoint	Config	Endpoint	Endpoint	Endpoint	GraphQL
Testnet endpoint	Config	Endpoint	Endpoint	Endpoint	GraphQL
Source / Deploy guide	Run node / liteserver	Deploy	Source	OpenTonAPI1	—
Documentation	Guide	Docs	Docs	REST, Swagger	Site

¹ TonAPI’s full indexer is not open-source; OpenTonAPI is a limited open-source version.

² Indexer means the service maintains its own database derived from blockchain data for richer queries (traces, jettons, NFTs, etc.), beyond raw liteserver RPC.

³ 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.

⁴ 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	TonAPI Streaming API
Protocol compatibility	Native reference implementation	Compatible with TON Center
Mainnet endpoints	SSE, WebSocket	SSE, WebSocket
Testnet endpoints	SSE, WebSocket	SSE, WebSocket
Authentication	TON Center	Ton Console
Documentation	Docs	Same as TON Center

References

• TON node and liteserver source
• Mainnet liteserver config, testnet config
• TON Center landing page
• TON Center v2 (Python, older) source and deploy instructions
• TON Center v2 (C++, newer) source and deploy instructions
• TON Center v3 source and deploy instructions
• TonAPI site, REST docs, Swagger
• OpenTonAPI (limited open-source)
• dTON GraphQL