TON RPC node endpoint — read-only JSON-RPC API

Last updated: November 1, 2026

Get API key Read the documentation

Network details

What "TON RPC node" means: liteserver, ADNL and HTTP APIs

Choosing a TON RPC node starts with the surface your application needs. A direct liteserver client exchanges binary TL requests over ADNL and identifies a server by its address, port and ed25519 public key. That connection can return cryptographic proofs, but the node's retention determines which historical reads succeed. An HTTP facade lets application code work with JSON instead of managing that connection.

HTTP API v2 exposes direct blockchain reads. An indexer API v3 adds a database for queries such as transaction traces and jetton discovery. Streaming is another interface: subscriptions deliver updates through SSE or WebSocket instead of repeated reads. Choose based on the query you need to answer, rather than treating all four interfaces as interchangeable.

Triport occupies the JSON facade position: 13 read methods answered by a liteserver pool, with v2 request conventions rather than the complete TON Center API. There is no v3 indexer, streaming or sendBoc. For a known contract or transaction cursor, these reads can fit; for token discovery or message broadcasting, plan a separate service. The method map below shows the underlying calls, not a promise that every protocol feature or proof field is exposed through this facade.

What works today

Each method and the liteserver call behind it

Main calls are shown below; block resolution may add lookups. Without a cursor, getTransactions first reads account state. The budgets are configured, unmeasured. Protocol names were checked against lite_api.tl at the pinned commit on 2026-10-25.

What teams run on it

• Telegram Mini App and bot backends read account state and known jetton wallets with runGetMethod. A balance read does not discover the holder's entire token portfolio.
• Account-history workers store the oldest transaction's lt/hash pair and request older pages. Follow the transaction pagination rules to preserve exact logical-time values and handle retention boundaries.

What this endpoint does not do

Paging transactions: lt, hash, and a JavaScript trap

getTransactions has no offset. You page backwards by passing the lt and hash of the oldest item you already received, which returns the next, older page. Logical time values are larger than a JSON number can hold exactly, so send large lt values as strings — a silently rounded lt is the usual reason a paginator repeats or skips transactions.

One more boundary worth stating: reading a known jetton wallet with runGetMethod is not discovery. Nothing here enumerates every jetton an account holds, so token-portfolio features need your own index.

Archive depth is measured, not promised

History is served from two liteservers, with a measured floor around masterchain seqno 86.86M. That figure is an observation from our own probing rather than a commitment, so a read below it can fail — design deep-history work to detect that instead of assuming coverage.

Testnet

TON testnets: TON testnet. Triport serves mainnet only; switch the URL and chain ID for test work — TON testnet connection settings.

TON testnet uses global ID -3 in config parameter 19, checked 2026-10-24. This is a global ID, not an EVM chain ID.

Terms on this page: ADNL · Liteserver · Masterchain.

Limits and plans

2× burst buffer, included. Finite request-rate limits show sustained RPS and short burst capacity. A full buffer at 20 RPS can absorb up to 40 requests at once and refills at 20 requests per second. There is no quota on the number of bursts and no extra charge for them. Size ongoing traffic to sustained RPS. Categories with no per-category cap have no numeric burst ceiling. How burst capacity works.

Both TON budgets are the same on every plan, and they are operational defaults rather than a TON load test. Plans: Basic $20, Pro $249, Business $499, Enterprise from $999 per month; Free is a 7-day trial with a single key in the EU region. See TON rate limits and tiers.

Every plan with its limits on every network, and what a plan costs at its cap: RPC pricing.

Quickstart

No keyless TON endpoint from Triport — the 7-day trial key is the way to try.

# Masterchain head
curl https://triport.io/rpc/ton \
  -H "x-token: $TRIPORT_API_KEY" -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"getMasterchainInfo","params":{}}'

# Account state
curl https://triport.io/rpc/ton \
  -H "x-token: $TRIPORT_API_KEY" -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"getAddressInformation","params":{"address":"EQCD39VS5jcptHL8vMjEXrzGaRcCVYto7HUn4bpAOg8xqB2N"}}'

# Next (older) page: lt as a STRING
curl https://triport.io/rpc/ton \
  -H "x-token: $TRIPORT_API_KEY" -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"getTransactions","params":{"address":"EQCD39VS5jcptHL8vMjEXrzGaRcCVYto7HUn4bpAOg8xqB2N","limit":20,"lt":"48123456000001","hash":"<hash-of-oldest-item>"}}'

FAQ source: TON Center official API rate limits, checked 2026-10-25.

TON JSON-RPC methods

• getAddressInformation
• getBlock
• getBlockHeader
• getConfigAll
• getConfigParam
• getMasterchainInfo
• getShards
• getTime
• getTransactions
• getVersion
• lookupBlock
• runGetMethod
• runSmcMethod