SOC 2 Tipo II (se abre en una nueva pestaña)
ISO 27001 (se abre en una nueva pestaña)
99,99 %+ de tiempo de actividad (se abre en una nueva pestaña)Read balances, track Jetton transfers, and power Telegram Mini Apps with reliable, high-performance TON RPC infrastructure.
Connect to TON mainnet or testnet through one geo-balanced endpoint. Access API v2, v3, and v4 for account reads, indexed token data, and block streams without running your own node.
Read live account state, query indexed Jetton data, stream blocks, and scale TON workloads with one development stack.
Escala cargas de trabajo de RPC de gran volumen con un rendimiento constante, solicitudes ilimitadas dentro de tu nivel « RPS » y costes mensuales predecibles.
Retrieve account transaction history, historical blocks, and indexed traces. TON nodes include historical data; archive requests consume 2 request units.
Use v2 for node requests, v3 for indexed Jetton and NFT data, and v4 for block-pinned reads and WebSocket block streams on Global Nodes.
Connect wallet-enabled Mini Apps to TON account data and transaction status. Pair TON Connect for user signatures with Chainstack RPC for backend reads and payment tracking.
Explore TON tooling
Query indexed Jetton transfers, verify token master addresses, and reconcile deposits and payouts. Follow message outcomes before marking a payment as settled.
Explore Jetton transfers
Read native balances and Jetton holdings, retrieve transaction history, and submit signed messages. Build account views with TON-native SDKs and indexed APIs.
Explore TON APIs
Run smart contract get-methods, read pool state, and follow indexed transaction traces. Use node reads or processed data to match your application’s freshness requirements.
Choose a TON API
Retrieve NFT collections, items, transfers, and metadata through API v3. Connect asset ownership and transaction history to marketplaces and consumer applications.
Get a TON RPC endpointComentarios de los equipos que desarrollan carteras, herramientas de seguridad, herramientas de análisis y aplicaciones de negociación con Chainstack en las redes compatibles.
ChainstackSu sólida infraestructura ha mejorado considerablemente nuestra capacidad para proteger de forma eficaz los entornos Web3.Chainstack ha sido fundamental para mejorar la funcionalidad multicadena y la experiencia de usuario de Brave Wallet.El modelo de tarifa plana «Unlimited» de Node nos ofrece previsibilidad en los costes, y el rendimiento es muy sólido.ChainstackLa pasarela personalizada de […] y Global Nodes han tenido un impacto extraordinario en nuestra eficiencia operativa.Hemos pasado de tener incidentes semanales a no tener ninguno.
Power wallets and Telegram Mini Apps with geo-balanced TON APIs. Choose flat-fee Unlimited Node capacity for sustained workloads, or Dedicated Nodes with direct ADNL access for native network integrations.
Get a TON endpointGet free testnet tokens from the Chainstack TON faucet. Test wallet flows, deploy contracts, and exercise Jetton transfers before moving to TON mainnet.
Top up an eligible wallet to 1 testnet GRAM, with a claim available every 24 hours. Test tokens have no monetary value and cannot pay mainnet fees.
Get testnet tokens (se abre en una nueva pestaña)
Read a wallet’s native balance with getAddressBalance through TON API v2.
Infraestructura preparada para la IA
Recomiende y gane
Ethereum
Hyperliquid
Solana
Arbitrum
BNB Smart Chain
Base
Polygon
TRON
Sui
Robinhood
Más información
https://ton-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID/api/v2/jsonRPCwss://ton-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID/api/v4/block/watchCreate a TON node and copy your endpoint from Acceso y credenciales. Sustituye YOUR_ENDPOINT_ID with your endpoint ID. The request uses the documented /api/v2/jsonRPC route.
curl --request POST \
--url https://ton-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID/api/v2/jsonRPC \
--header 'Content-Type: application/json' \
--data '{
"jsonrpc": "2.0",
"id": 1,
"method": "getAddressBalance",
"params": {
"address": "EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2"
}
}'El result is a balance string in nanotons. This is a read-only request; it does not send a transaction.
Start with free TON RPC for mainnet or testnet. Scale wallets and Mini Apps with higher throughput, flat-fee capacity, and dedicated infrastructure.
Incluye:
Todas las funciones de « Developer », además de:
Los complementos y la infraestructura dedicada de Node se facturan por separado.
Asistencia excepcional en todos los planes de pagoAhorra más del 50 % con nuestro plan de élite de pago por uso
Chatea en Telegram (se abre en una nueva pestaña)Explore TON API versions, native libraries, and infrastructure for Telegram Mini Apps.
Understand block-pinned reads, WebSocket streams, and API versions.
Leer el artículo
Explore native protocols, SDKs, and application integrations.
Leer el artículo
Compare infrastructure options for wallets and production workloads.
Leer el artículo
Follow the Jetton development guide and test your contracts.
Leer el artículoExplora los proyectos de código abierto de nuestro equipo de experiencia en « developer ». Sigue las guías prácticas, mira los tutoriales y adapta el código a tu aplicación.
TypeScript · Fungible tokens
Build, test, and deploy a fungible token on TON. Follow the smart contracts, TypeScript wrappers, and deployment scripts used in the Jetton tutorial.
TypeScript · Token contracts
Extend a TON fungible-token project with custom behavior. Work through the contract code, wrappers, and tests alongside the step-by-step guide.
TypeScript · NFT development
Develop a non-fungible token on TON with contract source code, TypeScript wrappers, and tests. Follow the guide to understand the implementation.
TON RPC gives applications programmatic access to The Open Network. Use it to read account balances, call smart contract get-methods, retrieve transactions, and submit signed messages. TON is not EVM-compatible: its HTTP APIs and native ADNL protocol differ from Ethereum’s eth_* métodos. Véase el TON API reference.
Create a free Chainstack account, create a project, and deploy a TON Global Node on mainnet or testnet. Open Access and credentials to copy your endpoint URL. The Developer plan includes 3 million request units per month, up to 25 requests per second, and one node. No credit card is required.
Your authenticated base URLs follow https://ton-mainnet.core.chainstack.com/YOUR_ENDPOINT_ID y https://ton-testnet.core.chainstack.com/YOUR_ENDPOINT_ID. For v2 JSON-RPC, append /api/v2/jsonRPC. API v3 uses /api/v3, and Global Nodes also serve v4 at /api/v4. Copy your node’s full URL from Acceso y credenciales. See TON API setup.
Use v2 for direct node reads, smart contract get-methods, and signed-message submission. Use v3 for indexed transactions, Jettons, NFTs, and traces. Use v4 for block-pinned account reads, TonClient4, and WebSocket block streams on Global Nodes. v3 data can lag behind node reads while indexing catches up. Compare TON API v2, v3, and v4.
Llamar getAddressBalance through the v2 API with the wallet’s address. The balance is returned as a string in nanotons, with one billion nanotons per native coin. This reads the native balance, not a Jetton balance. Use v3 Jetton wallet methods for token balances. See the getAddressBalance reference.
Yes. Use a TON RPC endpoint for backend blockchain reads, transaction tracking, and signed-message submission. Use TON Connect to request wallet connections and user signatures in your application. RPC infrastructure does not replace Telegram’s Mini App APIs or TON Connect. See TON tooling and the official TON toolset.
Use the v3 indexer’s /jetton/transfers endpoint to retrieve Jetton transfer records and /jetton/wallets for wallet data. Validate the Jetton master address rather than trusting a token symbol alone. For payment reconciliation, track transaction and message outcomes rather than treating submission as settlement. See the Jetton transfers reference.
Yes. TON API v4 on Global Nodes offers /block/watch for new masterchain blocks and /block/watch/changed for changed accounts. Use your authenticated v4 URL with the wss:// scheme and the required route. Streams can skip block sequence numbers, so fetch missing blocks when completeness matters. See TON API v4 routes.
Chainstack’s TON documentation states that all historical data is available on every node, on mainnet and testnet. Full requests cost 1 request unit; archive requests cost 2. getTransactions is always archive. Block-based methods become archive when the requested sequence number is at least 128 behind the relevant chain tip. See TON request-unit rules.
ADNL is TON’s low-level network protocol. Chainstack Dedicated TON Nodes support ADNL for applications that need direct network-layer access. Global Nodes provide the application-facing HTTP APIs instead. Dedicated Nodes start from the Pro plan, with infrastructure billed separately. See TON tooling and ADNL access.
Use TonWeb or TonClient for compatible v2 integrations. Use TonClient4 from @ton/ton with your Global Node’s /api/v4 endpoint. Direct HTTP requests also work with JavaScript fetch and Python requests. Native liteserver libraries require ADNL connection details rather than an HTTPS URL. Follow the TON tooling guide.
Use the Chainstack TON testnet faucet to fund an eligible test wallet. The faucet currently tops balances up to 1 testnet GRAM, with a claim available every 24 hours. Test tokens have no monetary value and cannot pay mainnet fees. Connect your application and wallet to TON testnet.
Connect to Chainstack’s TON mainnet or testnet endpoint to read account state, query Jetton and NFT data, execute smart contract get-methods, and submit serialized signed messages. Use /api/v2/jsonRPC for v2 JSON-RPC calls such as getAddressBalance, runGetMethod, y sendBoc. API v3 provides indexed transactions, messages, Jettons, NFTs, and traces. See the TON API reference.
On Global Nodes, TON API v4 uses /api/v4 for block-pinned reads and WebSocket block streams. Match your SDK to its API surface: TonClient4 uses v4, while compatible TonWeb and TonClient integrations use v2. ADNL access is available on Dedicated Nodes. Historical data is available on every TON node; requests consume 1 RU for full data or 2 RUs for archive data according to the method and block depth. See API version guidance y TON billing rules.
