What Is Telegram Bot API 10.4? HTML Widgets and TON Wallet Explained

2026-11-13
Telegram Bot API 10.4 turns message bubbles into interfaces. How HTML widgets and TON wallet queries work, and where the limits still are.
Telegram shipped Bot API 10.4 on 9 November 2026, and it does something no previous bot update has done: it lets a message bubble contain a working interface. Bots can now send HTML widgets that render inside the chat, respond to taps, update themselves in place, and talk to the user's TON wallet.
If you use Telegram on Android, you don't have to build anything to benefit. You just need to know what you're looking at the first time a bot sends you something that looks like an app instead of a paragraph.
What Telegram Bot API 10.4 adds
The update is one feature family dressed as several. There's a new Widget class, a sendWidget method, an answerWidgetQuery method, and edit methods that change a widget's data after it's already in a message.
The second half is the TON wallet. A widget query can carry the user's wallet card, data signed by their wallet, or a notification that a transaction was sent. Bots can also read wallet cards from chat info, including balances and NFT stickers, and detect service messages about transfers.
The third part is smaller but useful: ephemeral replies to button presses, and better quoting for rich messages. None of it changes how you chat. All of it changes what a bot can be.
How HTML widgets work inside a Telegram message
A widget is HTML that Telegram renders natively in the message bubble. It can have its own layout, its own sizing, and interactive elements that feel like buttons rather than links.
When you tap something in a widget, the client sends a widget query back to the bot. The bot answers, and the widget updates in place. That loop is the whole mechanic, and it's what separates this from the inline keyboards bots have used for years.
The practical difference is state. An inline keyboard sends a callback and the bot replies with a new message below. A widget keeps its position and its contents, so a bot can build a multi-step form, a small calculator, a poll with live results, or a game board without flooding the chat.
Shared widgets take it further. A bot can send the same widget to several people and update the public data from one place, which is how you'd build a group scoreboard or a live status panel without sending a new message every time something changes.
TON wallet queries make a chat bubble a payment sheet
This is the part with real-world consequences. A widget query can include a wallet card or a transaction notification, so a bot can ask the user's wallet to sign something and get an answer without opening a browser.
Read that carefully: the bot never gets your keys. Telegram's wallet does the signing, and the bot receives either signed data or a notification that a transfer happened. That's the same trust model as any payment confirmation flow, and it's the reason the feature is limited to private chats right now.
For users, the visible change is a payment or confirmation card inside a chat instead of a redirect to a website. For developers, it means a bot can run a checkout, a subscription confirmation or a tip flow without building a web app.
I'd still treat any wallet prompt from an unfamiliar bot as hostile until proven otherwise. The mechanism is safe; the people using it aren't automatically safe.
Ephemeral replies and the rest of the Telegram update
Two smaller changes deserve a mention because they'll show up in bots you already use.
Ephemeral replies let a button press trigger a message only the person who tapped can see. In a group, that solves the problem of bots answering everyone at once. In a channel, it keeps the comment section clean.
Rich message quoting means bots can quote formatted text from rich messages, which sounds like a developer detail until you use a bot that summarises long posts and wants to show you the exact line it's responding to.
Telegram also notes that the can_send_other_messages permission now covers widgets, so group admins get a switch for whether bots can post them.
What Telegram widgets look like in practice on Android
Three cases where this shows up immediately.
- A shop bot sends a product card with size options and a buy button. Tap the size, the card updates, tap buy, the TON wallet prompt appears. No browser, no mini app loading screen.
- A poll bot in a group posts a live result board. Votes update the shared widget instead of pushing a new message every time someone taps.
- An AI bot streams an answer with a Stop button, then keeps the partial text if you stop it. That's the same pattern the BotNews channel used to announce the release.
You may see this described as Telegram mini apps, and the two are related but not the same. Mini apps, also called Telegram Web Apps, open a full web page inside Telegram. Widgets render inside the message itself and are lighter, faster, and limited in what they can display. If a bot opens a full-screen page with a close button, that's a mini app. If the interface is sitting in the bubble, it's a widget.
Limits of Telegram interactive widgets
The limitations are specific and worth knowing before you get excited.
- In production, widgets can only be sent to private chats. Group and channel use isn't available yet.
- Sent widgets get protected content automatically, so they can't be forwarded. That also means they can't be copied with the copy methods.
- Widgets can't be sent in response to inline queries in production, even though the API includes the classes for it.
- A widget is HTML, not a full app. Anything that needs a camera, background processing or heavy rendering still belongs in a mini app.
- Wallet interactions depend on Telegram's own wallet, so regions where that wallet isn't available won't see the payment half of this update.
None of that makes the release less interesting. It makes it a first version, and the private-chat restriction is the one most likely to lift next.
What Telegram Bot API 10.4 means for Telegram bots
If you run a bot, the question is whether to rebuild your flows around widgets. For most bots, the answer is not yet.
Widgets pay off when the bot's job is a small structured interaction: picking an option, confirming an order, showing live status. They don't pay off for long forms or anything that needs a real screen. And with private-chat-only support in production, a bot that lives in groups has nothing to gain today.
The exception is commerce. A payment card inside a private chat, signed by a TON wallet, removes a step from every transaction, and that's worth building for now even if the API is still settling.
How to get the new Telegram build on Android
Bot features arrive server-side, so the Telegram app on your phone doesn't need a version bump to display a widget that a bot sends. What you do need is a current client, because older builds may not render the new message type at all.
- Open Telegram and check Settings > Advanced if you want to see your version number.
- If the app is out of date, install the current Telegram APK from APKPure over the existing app. Your chats and your session stay intact.
- Test with a bot you trust. Send it a command that returns a widget and confirm the interface renders and responds.
One security note worth repeating: a widget can ask your wallet to sign things. Treat any unexpected widget from a bot you don't recognise the same way you'd treat an unexpected payment request, and check which account a bot is tied to before you tap anything.
The verdict on Telegram Bot API 10.4
Bot API 10.4 is the update that turns Telegram messages into interface surfaces, and the TON wallet half is the part with real commercial weight. For users it's a quiet change until a bot you already use ships a widget, and for developers it's a decision about whether to build for private chats first.
Download Telegram from APKPure to make sure your Android client can render the new message type, then open the bots you use most and see which ones have already changed. The interesting ones won't look like chat any more, and that's the point.