TONAPI and TON Console

TonApi V2: Jetton Logo Field Migration Completed The migration of the Jetton logo field in TonApi V2 has been successfully completed today. Now, metadata.image returns the original logo link from the Jetton metadata, while the preview field continues to provide a cached version for display. If you haven’t yet, update your integration to use preview for displaying Jetton logos. Everything else remains unchanged, and no action is required for existing integrations.

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.

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.

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.

Help us become better. You probably use tonviewer.com, and you likely have ideas on how it could be improved or fixed. We’d really appreciate it if you took our survey and helped us make it better. Alternatively, you can share your feedback directly in the comments under this post.

⚠️ Planned TON Console Update When: 16 Feb, 06:30–08:30 UTC Impact: Console may be unavailable for up to 2 hours during this window. Services: Your products and APIs will continue running normally (no downtime expected). Please plan accordingly — you won’t be able to access Console to manage products while the migration is in progress

Help up become better. We want to make TON Console better and more useful for everyone, and we’re currently collecting some feedback from users. If you’ve used the console, we’d love to hear: - what you like about it - what feels confusing or inconvenient - what features you think are missing You can share your feedback through this short form or just leave a comment under this post. Any thoughts or suggestions would be really helpful Thanks!

How to get all jettons? And what's changing in TONAPI? In a nutshell There are two main ways: TONAPI (the /v2/jettons method) and Tonconsole.com (CSV export). When using the /v2/jettons method for pagination, it's recommended to use the cursor — the last_account_id parameter, which is taken from the previous response. It looks something like this: % curl -s 'https://tonapi.io/v2/jettons?limit=10' | jq -r '.jettons | last | .metadata.address' 0:249936139b63719c0afc44f883f4d8c15fd53bc6f93b6244debcf92b3e6c3ce1 % curl -s 'https://tonapi.io/v2/jettons?limit=10&last_account_id=0:249936139b63719c0afc44f883f4d8c15fd53bc6f93b6244debcf92b3e6c3ce1' | jq -r '.jettons | last | .metadata.address' 0:31bb2214dca832dd8091d90adc313e9834782934263764810cb28fc7f8fb3878 In more detail 1. The /v2/jettons method allows you to get real-time data. At the moment there are almost 1 million jettons on TON. One request lets you get 1000 data rows. Theoretically, on the Lite tier (10 RPS), you could download all jettons in about a minute and a half. But this method had a problem — the offset parameter. Until recently, this method's execution time grew proportionally to the offset parameter. To maintain compatibility and ensure high performance, we carried out an optimization that uses a cached jetton list when offset is used. This list is updated once a day. At the same time, we've added a new parameter — last_account_id. It provides a more correct and efficient way to paginate to the most up-to-date data. 2. For large exports like this, it may be more convenient to use Tonconsole. For example, a query like SELECT d.account_id FROM getmethods.get_jetton_data d lets you get the full list of jettons. In Tonconsole you can enable scheduled export runs. The "Download CSV" link is stable, and you can quickly get a ready-made dataset with a single request from the backend (for the query above, that's 60 MB). Feel free to ask question in comments ✍️

❗️`/v2/jettons/{addr}/holders` got pagination upgrade. offset parameter will be limited soon. GetJettonHolders method was always returning holders sorted by their balance (starting from the top). It also had offset parameter that users can use to traverse the top 10k holders. This approach has two problems: 1) inconsistency. Obviously, balances change constantly. So scanning data with limit+offset will get a lot of gaps due to volatile ordering 2) performance. Request time grows with the offset, because of how databases usually work We've just made optimization to speed this method ⚡️4x times! 🎚️Introducing cursor But O(n) is still O(n). So those who need real-time set of jetton holders can use new cursor-based pagination method, which has constant performance no matter what page it is. So similarly to /v2/jettons, we introduce two new parameters to the GetJettonHolders method: sort_by and last_account_id. Use /holders like before to get top holders (sort_by=balance is default). Offset can't be more than 9000. Use /holders?sort_by=address to scan through the whole holders set. Here is how it looks: # get first page % time curl -s 'https://tonapi.io/v2/jettons/EQCxE6mUtQJKFnGfaROTKOt1lZbDiiX1kCixRv7Nw2Id_sDs/holders?sort_by=address' | jq -r '.addresses | last | .address' 0:9dfaaafbc46bad3c46d9362d8e5d99f993e953034212c5f34689cac419ea9d2c curl -s 0.02s user 0.02s system 5% cpu 0.670 total # get second page % time curl -s 'https://tonapi.io/v2/jettons/EQCxE6mUtQJKFnGfaROTKOt1lZbDiiX1kCixRv7Nw2Id_sDs/holders?sort_by=address&last_account_id=0:9dfaaafbc46bad3c46d9362d8e5d99f993e953034212c5f34689cac419ea9d2c' | jq -r '.addresses | last | .address' 0:b6a096bdc189790abde43c11041f1f5a72daa92fa0ed24e918e7187515dce53b curl -s 0.01s user 0.01s system 4% cpu 0.533 total Have the set of holders of your jettons in real-time with these high-performance updates!