Bot API 10.3 🔁 Button Revolution • Buttons can now be placed is the focus of this TON Drop Hub update for readers following Telegram Mini Apps, TON ecosystem activity and related user risks. For users, this means interactive elements will become more seamless and visually integrated right inside complex messages, rather than appearing only beneath them. Bots can now replace messages with ephemeral overlays, edit them live with rich content or upload new media, and even attach documents or embed expandable quote blocks and tables. These changes from Bot API 10.3 🔁 Button Revolution open the door to streamlined experiences, richer content, and more efficient Mini App interfaces for both end users and creators on Telegram.
Placing Buttons in Rich Messages
With Telegram Bot API 10.3, buttons can be inserted directly into any rich message, opening up new ways for bots to create interactive content. Developers can utilize multiple native button styles and assign custom alignment inside each message, which means layouts are no longer bound to the bottom of the screen or a rigid menu format. Buttons inside rich messages now natively support actions such as callbacks, launching Mini Apps, accessing Login URLs, and copying text in one tap.
This release also allows bot builders to mark inline buttons as disabled, a practical update for flows where certain choices need to be locked or visually indicated as unavailable in real time. For the user, this makes navigation and multi-step processes more understandable and efficient. The update affects all bots using rich message formats, especially those integrating with Mini Apps or requiring granular, contextual user input within Telegram chats.
TON Drop Hub take: Rich message buttons let Mini Apps and bots deliver more focused, app-like experiences natively inside Telegram. For teams building interactive flows or onboarding processes, this flexibility makes every bot less clunky and far more visually expressive—without forcing users out of the chat.
Enhancements for Ephemeral and Rich Messages
With the Bot API 10.3 release, ephemeral messages and rich content upgrades change how users and builders interact through Telegram bots. Bots can now swap out standard replies with an ephemeral overlay and seamlessly update it with richer media or personalized responses inside the same message window. This mechanism removes clutter from chat histories and enables transactional content—such as payment confirmations, wallet updates, or onboarding flows—to stay focused and private inside a single interactive block.
Rich messages now support direct document attachments and easier embedding of previously uploaded media. Developers can add expandable quote blocks or embed compact tables, catering to structured data views and improved support workflows. For any process requiring stepwise guidance—think onboarding new users to a wallet or confirming DeFi interactions—these enhancements mean fewer message bursts and a clearer, less confusing conversation thread.
For bots that require user signatures, document review, or persistent interaction with files and tables, this update means less time wasted flipping through message history. Instead, users can engage with evolving, interactive content with every action or update captured within the same rich reply. This directly benefits onboarding, wallet management, and any flow that leans on document or data-rich communication.
AI Agent Updates and Partial Responses
The Bot API 10.3 update adds native support for AI agent controls inside Telegram bots. A new Stop button is now available for streamed drafts, allowing users to halt AI-generated content in real time. Bots can also preserve partial responses—meaning if an AI draft is interrupted, the incomplete output may still be accessible. This feature targets conversational bots, especially those leveraging large language models or similar streamed-response architectures.
Official documentation confirms these functions, but it does not define which AI frameworks or third-party APIs support streamed drafts out of the box. Bot developers must verify integration at the bot code level; there is no evidence these controls work universally across all AI bot implementations. User-facing limitations include possible mismatches between Stop button availability and actual underlying model stoppability.
TON Drop Hub take: The Stop button is a concrete step for user agency during AI interactions, but practical coverage depends on each bot’s backend. Builders should test end-user experience in real conversations, especially around response latency and message handoff. Ephemeral overlays or partial response handling may require user education to avoid confusion mid-interaction.
The Bot API 10.3 update dramatically ramps up the possibilities for Telegram bot interfaces. Developers can now place interactive buttons directly into any rich message with multiple native styles and custom alignments—plus instant support for callbacks, Mini App launches, Login URLs, and more. Bots even gain the ability to disable inline buttons as part of dynamic flows.
TON Drop Hub take: This round of updates sets a new bar for building interactive Mini Apps and transactional bots, especially where single-message flows or adaptive interfaces matter. Builders should experiment with new button flexibility and test how ephemeral overlays and rich messages impact response designs.
For more ecosystem coverage, see Latest TON news.
Source reference: original source.