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

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

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!

Toncoin → Gram

Following the approved network changes, TONAPI and Tonviewer now support the new currency naming: Gram.

We have made every effort to preserve backward compatibility wherever possible.

List of Changes

1. Both Variants Are Accepted in Input Parameters

The /v2/rates/chart endpoint now supports a new currency value:

* 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

The response returns the currency name exactly as specified in the request parameters.

2. New Fields for Gram

Throughout the TONAPI response schema https://tonapi.io/api-v2, Gram support has been added to all fields that previously referenced TON.

For example, in the GET /v2/multisig/{account_id} endpoint, the field orders[].risk.gram has been added alongside orders[].risk.ton.

Similarly, corresponding Gram fields have been introduced across other endpoints, such as:

* ton_balance + gram_balance
* and other TON-related fields.

3. `token_name` Value Changes

The token_name field now contains the value Gram instead of TON.

4. Other User-Facing Fields

In structures where fields are primarily intended for user-facing display, references to Toncoin have been changed to Gram.

For example, in the Action structure (used by endpoints such as /v2/accounts/{account_id}/events, /v2/gasless/estimate/{master_id}, and others):

* simple_preview.name: "Ton Transfer" → "Gram Transfer"
* simple_preview.description, prefix.simple_preview.value: "5 TON" → "5 Gram"