Telegram's Bot API gets inline keyboards, support for 19 file types before Facebook's F8 event
Telegram has released an update for its Bot API that it calls the “biggest change” to its platform “since June 2015.” Included in version 2.0 are a slew of features, including new inline keyboards …
Context & Ripple Effects
Telegram is calling Bot API version 2.0 its biggest platform change since June 2015, and the substance backs the framing up: inline keyboards turn a bot reply from plain text into an interactive set of buttons inside the message thread, while support for 19 file types widens what developers can push through a chat. The release lands deliberately on the eve of Facebook's F8 developer conference, where the rival would be expected to lay out its own messaging-platform roadmap.
The arc matters because this is the foundation layer for what came after: within a year, Telegram 4.0 extended the bot platform into chatbot payments, converting the interactive surface built here into a transactional one. Bots were moving from novelty responders toward the primary way users touch services inside a chat app.
First-order effects
- Bot developers on Telegram can immediately ship richer experiences — tappable inline keyboards and 19 supported file types — without waiting for native apps or web views.
- Facebook enters F8 with Telegram having just raised the bar for what a messaging bot platform offers, putting pressure on its own bot announcements at the event.
Second-order effects
- Interactive bots create the surface for commerce: once users tap buttons rather than type commands, wiring in payments becomes the natural next step, which is exactly where Telegram took the platform with 4.0.
- Rival messaging platforms are pushed to match button-and-file interactivity in their own bot SDKs, since developers gravitate to whichever platform lets them build the most capable bot fastest.
Third-order effects
- If the pattern holds, messaging clients become operating layers of their own — the chat window hosts discovery, interaction, and payment for third-party services, displacing standalone apps for lightweight use cases and making the bot API, not the app store, the distribution gate.
The trend: Messaging platforms are evolving bots from text responders into interactive, eventually transactional work surfaces, with each platform's API cadence setting the pace of that shift.