Rate limits

To ensure stability and fair access, TON Center applies rate limits to all API requests.
If an application exceeds these limits, the API returns a 429 response.

Increase limits by requesting an API key and selecting a higher subscription plan. Without any API key, the default rate limit is 1 request per second.

Default limits

Plan	Tokens per network	Requests per second	Notes
Free	1	10	Shared liteservers suitable for low-volume testing and small projects.
Plus	3	25	Private liteservers that reduce contention compared to shared access.
Advanced	10	100	Private infrastructure with capacity for higher request rates.
Enterprise	Custom	Custom	Custom throughput and support. Contact @toncenter_support for details.

Rate limits apply to all API keys in total separately for every TON network, including mainnet and testnet. For example, the Plus plan users can create three API keys for the mainnet. The total limit for these three keys will be 25 requests per second.

Rate limit exceeded

When requests are sent faster than the allowed rate limit, the TON Center API temporarily blocks new ones. A JSON response indicates the rate limit is exceeded:

{
  "ok": false,
  "result": "Ratelimit exceed",
  "code": 429
}

When this occurs:

• Stop sending new requests and wait a few seconds before retrying.
• Implement exponential backoff to avoid repeated rate-limit violations.

Troubleshooting

If a paid plan is active but the rate remains 1 RPS:

• Check that the API key is included correctly in the requests. Requests without a valid API key are limited to 1 RPS, even if a subscription is active.

• Verify the correct key is used for the intended environment (mainnet or testnet). Each network requires its own key.

Wait up to 10 minutes after upgrading the plan or changing the API key. Subscription and key updates can take several minutes to propagate across TON Center’s rate-limiting system.