Channel
@tonxapi
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
1,113subscribers
-6 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002071749652 |
|---|---|
| Type | Channel |
| Username | @tonxapi |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/tonxapi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 12:02 | 1,113 | -3 |
| 8 Aug 2026, 15:05 | 1,116 | -3 |
| 6 Aug 2026, 12:05 | 1,119 | no change |
| 5 Aug 2026, 22:01 | 1,119 | first reading |
20 posts held, back to 30 October 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 1 July 2025. An engagement rate over an empty window would be a number about nothing.
271 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 40.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 109 | 40.2% | |
| ❤ | 80 | 29.5% | |
| 💩 | 25 | 9.23% | |
| 🔥 | 23 | 8.49% | |
| 😁 | 21 | 7.75% | |
| 🎉 | 6 | 2.21% | |
| 👌 | 3 | 1.11% | |
| 🤪 | 2 | 0.738% | |
| 🕊 | 1 | 0.369% | |
| 🤬 | 1 | 0.369% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 271reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 30 October 2024 to 1 July 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @tonxapi. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 30 October 2024 to 1 July 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
🤝 TONX API Transitioning to Enterprise-Only Access – Effective July 1 Starting July 1, 2025, TONX API will transition to an enterprise-only access model. As adoption scales, we’re evolving our core services into enterprise-grade infrastructure — ensuring enhanced security, compliance, and reliability for institutional use cases. This shift enables us to better support large-scale projects by focusing on high-perfor…
👍5❤4🕊1
🚀 TON Blockchain & Telegram Mini App Development Guide We've put together a comprehensive guide to TON blockchain development, packed with essential resources and tools to help you navigate TON’s technical landscape. Covering: - TON Architecture - Development Environment Setup - Smart Contracts - Token Standards - Telegram Mini Apps - TonConnect - API Integration - DApp Use Cases & Best Practices 🧑🏫 Explore the g…
❤4👍2
🚀 TONX.js SDK (@tonx/core): Modern TypeScript-First SDK for TON Blockchain Experience seamless TON blockchain development with our JavaScript SDK. Whether you're new to the TON ecosystem or an experienced developer, get your dApp running in seconds. ⚡️ Quick Setup: npm install @tonx/core 💻 Import & Initialize TONX API Client: import { TONXJsonRpcProvider } from "@tonx/core"; const client = new TONXJsonRpcProvider…
❤3🎉1🔥1
🔎 TONX API vs. TON Center: An In-Depth Comparison of TON's Leading API Providers We've just published a technical comparison examining architectural approaches, performance characteristics, and developer tooling. 👉 Read now: https://blog.tonxapi.com/2025/01/16/tonx-api-vs-ton-center-ton-blockchain-api-provider-comparison/ Key findings highlight crucial differences in: 🔹 Infrastructure reliability 🔹 Message proces…
❤6
🌟 Your Complete Guide to TON Blockchain APIs - Now on TONX API • Messages API Message & Fee Handling • Accounts API States & Events • Blocks API Headers & Consensus • Token Standards NFT & Jetton Operations • Advanced Tools Webhook & Trace APIs From lightning-fast message processing to real-time transaction tracking, think of it as your project's mission control center - every blockchain operation, every state chan…
👍4❤1
🚀 Get Started with TONX API Setting up your first TON blockchain project? TONX API brings you simplified setup, flexible plans, and powerful developer tools to accelerate your Web3 journey. ⚡️ Fast Setup in 4 Steps: 1️⃣ Create your app Create and name your first application through the TONX API dashboard. 2️⃣ Create your TONX API key Name your key and select your network (Mainnet/Testnet) to start building. 3️⃣ Ge…
❤2
🚀 TONX API is teaming up with MEXC Ventures to accelerate TON Blockchain adoption! ✨ As a pioneering force in the TON ecosystem, MEXC has emerged as the largest supporter among CEXs through MEXC Ventures. Their strategic investments and listings have empowered numerous early-stage TON projects, with their comprehensive fund managing $100M+ AUM across L1/L2 ecosystems. ⚡️ Through this strategic partnership, TONX API…
👍2
📣 Introducing the Webhooks API: Subscribe to Real-Time Events on the TON Blockchain The latest addition to TONX API enables developers to build applications that instantly respond to blockchain activities. Transform your development workflow with enterprise-grade event monitoring infrastructure. ⚙️ Technical Architecture: - Event-driven subscription system - Webhook UUID management - Secure endpoint validation - Re…
😁4🤬1
🚀 TONX API partners with Deepcoin, powering next-gen crypto trading on TON! ✨ Deepcoin is a leading cryptocurrency exchange which has amassed 10M+ registered users across 30+ countries, facilitating a cumulative trading volume exceeding $1 trillion. 🔼 Leveraging enterprise infrastructure from @TONXAPI, Deepcoin users enjoy instant scaling, 99.99% uptime, and optimized indexing for high-performance trading. ➡️ Read…
❤3
🎮 We’re thrilled to partner with GAMEE, the Web3 mobile games platform with 100M users! 🌐 Backed by Animoca Brands, GAMEE’s WatBird Universe has connected 6M+ wallets on TON, paving the way for mass Web3 social gaming adoption. 🚀 With @TONXAPI’s enterprise-grade infrastructure, offering 99.99% uptime and instant scaling, GAMEE continues to redefine what’s possible in Web3 gaming. Ready to bring your game to life o…
👍5
Dear TON Developers in India 🇮🇳 We’re thrilled to support your projects during TON Hacker House Bangalore by offering the @TONXAPI Scale Plan with 1,000 Requests Per Second (RPS)—completely FREE! (normally 30 $TON/month) Whether you’re attending or not, this is a great opportunity to access enterprise-level tools for your builds. 💪 💎 Special Offer Details: - Super Scale Code: TONINDIA - How to Redeem: Sign up → G…
❤5
🎉 TONX API Black Friday: GET 10X POWER BOOST! ⚡️ ✔️ Free Plan - 10 RPS (10X more than others🔼) - Perfect for testing & development ✔️ Growth Plan - 100 RPS + Premium Tools - Only 3 $TON per month - Includes BoC API & Estimation Fee ✔️ Scale Plan - 1000 RPS for higher needs - Only 30 $TON per month - Full access to all premium features ⏱ Try Growth Plan FREE with code “NOV30”! Delivering enterprise performance wi…
👍2
Showing the 12 most recent of 20 posts we hold for @tonxapi. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 658,710 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 11 August 2026 — this entry's latest reading, not the date you are reading this.
“TONX API” (@tonxapi), 1,113 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/tonxapi.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.