Chainstack TON nodes now serve Toncenter API v4 — REST and WebSocket — on both Mainnet and Testnet, alongside the existing v2 and v3 support. Same endpoint, same API key: there’s nothing to migrate to start using it.
Toncenter is the HTTP API surface TON node operators expose for reading chain state, submitting transactions, and querying jettons and NFTs — Chainstack has served v2 and v3 since TON launched on the platform, and it’s the label you’ll see next to your endpoint in Access and credentials — Toncenter API v2, v3, and now v4. Neither surface has ever had a push channel, so every wallet, indexer, and bot built on top of them polls for new blocks and account changes on a timer. v4 is the first Toncenter version on Chainstack that can push instead.
What’s new in v4
- Typed responses — structured, typed JSON in place of the looser shapes v2 and v3 return, so client code spends less time guessing field types.
- Block-pinned, cacheable URLs — request state as of a specific block, so the same URL always returns the same answer and is safe to cache instead of re-fetched on every call.
- Real-time subscriptions over WebSocket — subscribe to new blocks and account changes directly, instead of re-running the same request every few seconds to notice a balance or a new block.
Nothing to migrate
v4 runs on the same endpoint and API key as v2 and v3 — point your client at the v4 path and it works. v2 and v3 keep serving traffic exactly as before, so there’s no cutover window and no reason to touch an integration that isn’t ready to move.