The Testnet API will undergo planned maintenance on April 4, 2025, from 08:00 UTC to 12:00 UTC. It will be unavailable during this time.

Tracking Transactions on TON Just Got Easier! 🎉

Tracking external transactions (external-in) on the TON blockchain was challenging for all of us due to minor metadata differences.

Now TonAPI solves this with the normalized hash. With this method, tracking transactions is simple and reliable.

We've prepared clear examples to get you started:
- Tracking transactions from TonConnect for dApps
- Tracking manually constructed external messages

See code examples →

We’re excited to share this improvement, and soon more ecosystem tools will support it too!

We wrote an article to explain in more detail how external-in normalization works and how to use it to track transactions reliably. Read the article

🛠 wallet.ton.org runs on TON API

TON Core team becomes the latest customer of our development platform TON API, among @wallet, Trust Wallet, Tonstakers and many other big players in TON.

The latest upgrade of wallet.ton.org relies on TON API for its key features: token and NFT balances, and price feeds.

We are delighted to support and grow the TON ecosystem with our integrated approach to infrastructure, open standards, partnerships and deep product integration in Tonkeeper, Tonkeeper Pro and Ton Console.

📝 Sign Arbitrary Data with TON Connect

The latest update to our TON Connect implementation introduces a powerful new feature: the ability to sign arbitrary data — from plain text and binary blobs to BOC (cell) format.

This unlocks new use cases in the TON ecosystem: secure off-chain flows, verifiable signatures, and advanced on-chain logic — all through the familiar TON Connect interface.

Now supported in the latest versions of Tonkeeper on iOS and Android.

Explore the guide and start building →

💻TONAPI YouTube Contest — Now Open

We are inviting developers to create technical YouTube videos showcasing real use cases with TONAPI, from tutorials and code walkthroughs to project demos and tooling comparisons.

The top 5 videos will split a 5,000 USDT prize pool (Bitrefill Gift Card).

Winning entries will also receive visibility on Tonkeeper social channels, TONAPI discount codes, potential dApp Browser integrations, and invitations to our exclusive mentorship program.

👉 Submit by emailing contest@tonkeeper.com with subject “TONAPI Contest”

📆Submissions are open until July 18.

Full details

🏆TONAPI YouTube Contest — Winners Announced

Thank you to everyone who submitted a video for the TONAPI YouTube Contest. We loved seeing the range of projects built with TONAPI.

🥳Congratulations to the 5 winners who will share the 5,000 USDT prize pool in the form of Bitrefill gift cards, with 1,500 USDT awarded to first place.

Winning entries:

1st: link
2nd: link
3rd: link
4th: link
5th: link

We appreciate the effort from every participant. The number of submissions exceeded our expectations, so we needed a bit more time to review them all. Thank you for your patience.

📨Winners will be contacted by email to arrange prize distribution.

We look forward to seeing more builds with TONAPI.

Download Tonkeeper tonkeeper.com
Mini app | 𝕏 | ru | فارسی | 中文 | uz

Technical update about external messages for wallets v4

Tomorrow ~10:00 UTC we will deploy an emergency update that breaks backward compatibility. The decoded external message body for wallets_v4r2 will now use a SumType for the payload.
You can see the difference at the following two URLs:

https://dev.tonapi.io/v2/blockchain/transactions/3d3ad440cd5d1c5bb089695338f250d19707659e4444c98756fcc0d444558346 - new version
https://tonapi.io/v2/blockchain/transactions/3d3ad440cd5d1c5bb089695338f250d19707659e4444c98756fcc0d444558346 - old version

It doesn’t affect you if you haven’t used the decoded_body field for external messages in raw transactions or traces.

We plan maintenance work today at 14:00 UTC for approximately less than an hour. The tonconsole.com admin panel and analytics queries may be unavailable during this time. The functionality of the main API will not be affected.

We apologize for the prolonged migration. The service has been restored.

Dear users,

Please note that on October 20, the liteserver error codes in the service at https://tonconsole.com/tonapi/liteservers will be updated.
Alongside the standard liteserver error codes (such as 651, -400, etc.), the service may return additional codes.
Specifically, error code 5556 will be REPLACED with 228 (rate limit exceeded) for consistency.
Proper handling of these error codes is crucial for maintaining stable operation of client applications.
To prevent rate limit errors, consider implementing a rate limiter on the client side, configured slightly below the plan's maximum threshold.