TONAPI and TON Console

The new TON Console is ready to try! We’ve refreshed the interface to make it easier to navigate and work with your projects. Try the staging version here: https://console.tonapi.io/ We’d love to hear your feedback!

Get account's NFT history in 80 ms. That's the new baseline

Testnet flood, and how we manage it Today testnet is receiving a huge performance benchmark. 🥵 Load has peaked at ~500 jetton transfer per second, about 1500 raw TPS. This is about 30x of current mainnet baseline. How TONAPI indexer was feeling? We have two independent setup for testnet indexing. And with this flood we were lucky to see the difference between two setups under the performance load. Because one of them just got a huge update ✨ The update is how we interact public liteservers and internal archive node to index data. 1) ⚖️ each liteserver performance and lag is measured to sustain nice and stable flow of blocks from the network 2) 🧮 account state is derived from block's merke update from the block data to minimize interaction with liteserver (they are usually unable to give account states during such load) So how did it help. Well old indexer basically stuck for half an hour though it catches up quickly once liteservers are back alive. New indexer was behind the head of the blockchain at most 35 seconds - this only after sustained 30x mainnet load, and it recovers immediately once load gets a little. This shows continuing improvement and development of TONAPI to deliver our users most recent data as fast as possible even with future-proof performance.

❗️`/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!

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).

Toncoin → Gram В соответствии с принятыми изменениями в сети в TONAPI и Tonviewer поддержан новый нейминг валюты – Gram. Мы постарались сохранить обратную совместимость там, где это возможно. Список изменений: 1. Принимаем оба варианта во входных параметрах В методе /v2/rates/chart поддержана новый тип currency: * https://tonapi.io/v2/rates/chart?token=usdt&currency=ton&points_count=5 * https://tonapi.io/v2/rates/chart?token=usdt&currency=gram&points_count=5 В ответе возвращается то наименование валюты, которое было передано во входных параметрах. 2. Новые поля для Gram В схеме ответов TONAPI (https://tonapi.io/api-v2) во всех полях упоминающих TON поддержана логика и для Gram: Например, в методе GET /v2/multisig/{account_id} к полю orders[].risk.ton добавился orders[].risk.gram. Аналогично, в других методах: ton_balance + gram_balance и т.д. 3. Переименования token_name в строках Поле token_name теперь содержит значение Gram вместо TON. 4. Некоторые другие поля В структурах, где поля влияют прежде всего на отображение пользователю, упоминания Toncoin изменено на Gram. Например, в структуре Action (методы /v2/accounts/{account_id}/events, /v2/gasless/estimate/{master_id} и т.д.): * simple_preview.name: "Ton Transfer" -> "Gram Transfer" * simple_preview.description, prefix.simple_preview.value: "5 TON" -> "5 Gram"

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!

🚀 Billing Update: USDT Top-Ups We’ve rolled out an update that makes USDT the primary way to top up your balance and pay for services in TON Console. What’s new • Top up in USDT and pay for services in USDT • Improved charge history with CSV export • Multiple UX improvements across the Console 📝 TON top-ups will still be available only for projects with an existing TON balance at the time of the update.. Also, charges are deducted from one balance type only — you can’t split a single charge between TON and USDT.

⚠️ 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 us get 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.

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.

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

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.

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

🏆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

💻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

📝 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 →