TONAPI and TON Console
📈 Analytical overview of Telegram channel TONAPI and TON Console
Channel TONAPI and TON Console (@tonconsole_com) in the English language segment is an active participant. Currently, the community unites 12 038 subscribers, ranking 8 226 in the Cryptocurrencies category and 53 644 in the Russia region.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 12 038 subscribers.
According to the latest data from 03 September, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by -156 over the last 30 days and by -1 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 7.54%. Within the first 24 hours after publication, content typically collects N/A% reactions from the total number of subscribers.
- Post reach: On average, each post receives 908 views. Within the first day, a publication typically gains 0 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 11.
📝 Description and content policy
Channel description not provided.
Thanks to the high frequency of updates (latest data received on 04 September, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Cryptocurrencies category.
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!window.tonapi object exists in your browser.
How it works →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.preview has been added to the JettonInfo object. It contains a link to a cached image of the Jetton logo, specifically prepared for fast and convenient display.
2. The field metadata.image in the JettonInfo object temporarily returns the same cached image as preview. Once the migration is complete, this field will start returning the original link to the logo from the Jetton metadata.
We now recommend to display logos using the field: preview
Why are we migrating:
The goal of the migration is to resolve the mismatch between the original metadata and what our API currently provides. At present, metadata.image returns a cached image instead of the original link. After the migration, the metadata will fully reflect the original data, without any modifications.
This eliminates the need for developers to parse contract cells to retrieve original image links.
Affected Schema: JettonInfo
Affected Methods:
• getJettonInfo (/v2/jettons/{account_id})
• getJettons (/v2/jettons)
• getJettonInfosByAddresses (/v2/jettons/_bulk)
JettonInfo:
type: object
required:
- mintable
- total_supply
- metadata
- verification
- holders_count
properties:
metadata: # <- will match the original metadata after migration
$ref: '#/components/schemas/JettonMetadata'
preview: # <- new field
type: string
example: "https://cache.tonapi.io/images/jetton.jpg"
# ... other fields
Backward compatibility:
This change does not break existing integrations—your applications will continue to work without modifications. However, the image URLs for Jettons will point to the original addresses, which may affect image loading speed and the privacy of the end user.custom_payload parameter in the supported_extension field in the request. For example, this link or direct jetton info this link:
{
"balance": "1000000000",
"wallet_address": {
"address": "0:405171f583a9e39e22ae9d8394769bc6e37299c59332012a51693b4d606780f3"
},
"jetton": {
"address": "0:fa67d0c7739331fbc3c8f08e018c65f47763616a969100ad760a0b2dc1e36832",
"name": "Mintless Points",
"symbol": "Points",
"decimals": 9,
"image": "https://cache.tonapi.io/imgproxy/DmmPn6dWmsmBgSMVbvjbhIDCChLWI3RmqDJ71whxYBA/rs:fill:200:200:1/g:no/aHR0cHM6Ly9pLmliYi5jby9TS010TlRHL21pbnRsZXNzLnBuZw.webp",
"custom_payload_api_uri": "https://claim-api.tonapi.io/jettons/EQD6Z9DHc5Mx-8PI8I4BjGX0d2NhapaRAK12CgstweNoMint"
},
"extensions": [
"custom_payload"
]
}
How to Support Mintless Jettons in Your Dapp
1. Request balances with ?supported_extensions=custom_payload.
2. Check if data["extensions"] contains "custom_payload" for the jetton.
3. If it contains and you want to autoclaim on transaction, when your dapp asks the user to send an outgoing jetton transfer via TonConnect, request custom payload and state init via the API: https://tonapi.io/v2/jettons/0:fa67d0c7739331fbc3c8f08e018c65f47763616a969100ad760a0b2dc1e36832/transfer/UQBDaa8UGaMVKiT8TKXiaJqlyWLmx-MoHYvT_wzHEpdUnIss/payload.
4. Add the received data to the message in your TonConnect request.
5. That's it. Now you support mintless jettons!