Telegram widgets: what a business bot in Uzbekistan can do with them since 9 November 2026

Since 9 November 2026 a Telegram bot can send a private chat an interactive widget built in HTML and JavaScript. It does not replace a website: the widget has no network access, for now works only in the private chat, and talks to the bot in short requests.

Key points

  • On 9 November 2026 Telegram released Bot API 10.4 with HTML widgets and a sendWidget method; in production they work only in a private chat with the bot.
  • A widget is one HTML document of up to 32,768 bytes and 4,096 bytes after compression, running in a QuickJS sandbox: all network calls are blocked, and data moves only through the bot.
  • A widget's request to its bot is 1 to 64 bytes, at most 5 per 5 seconds per user and bot; the bot must answer within 15 seconds.
  • The payment flow in the documentation is a TON wallet transaction the user confirms; the docs we read do not mention Payme, Click or Uzum.

Telegram released Bot API 10.4 on 9 November 2026, and with it HTML widgets: a bot can now put a small interactive block, written in HTML, CSS and JavaScript, straight into a chat message. We read the widget documentation and the changelog on 10 November 2026 to see what a business bot in Uzbekistan can and cannot do with it today.

What is a widget, exactly?

A widget is one self-contained HTML document that a bot sends inside a message. The code is fixed at the moment of sending. Only the widget's state changes, and only the bot can change it; the widget can ask the bot for a change, nothing more. The docs describe two kinds of state: chat state tied to one message, and shared state, seen wherever the widget is shown. A shared widget, one object on the server like a poll, keeps one shared state for every message that shows it.

Telegram Info reported that the feature arrives with Telegram 13.2 for Android, iOS and macOS and 7.4 for Telegram Desktop. The widget docs themselves state no minimum app version.

What can a widget not do?

The limits are the useful part:

  • Private chat only. In production, sendWidget works only in the private chat with the bot, and sent widgets are protected: users cannot forward them. Groups, inline mode and forwarding exist only on the test server.
  • No network. The widget runs in a QuickJS sandbox, not a browser view. Every network call throws, external scripts and fonts never load, and navigation is blocked.
  • Small. The HTML is capped at 32,768 bytes (4,096 bytes after zlib compression). Chat state and shared state are 1,024 bytes each. The bubble is 200 to 600 px wide and 50 to 600 px high; anything beyond is clipped.
  • Short requests to the bot. The widget sends 1 to 64 bytes, at most 5 requests per 5 seconds per user and bot. The bot answers within 15 seconds with up to 1,024 bytes, or the widget gets a timeout.
  • No secrets. The docs say to treat the code and the shared state as public (forwards carry them to any chat, and in a group every member sees the chat state) and never to put secrets in a widget.

What it means for a business in Uzbekistan

For a shop, clinic or restaurant that already runs a Telegram bot, a widget can replace a stack of inline buttons with one live element in the private chat: a size picker, an order-status card, a small queue counter. The data comes from your own system through the bot, which is the only part that can reach it.

Three limits decide the rest. A bot cannot send a widget to a channel, and groups work only on the test server for now, so a widget does not help with public reach today. The widget has no network, so it never talks to your CRM or website itself. And in production it currently lives only in the private chat, so nobody can find it from outside: a website stays the place people find you in Google, Yandex or an AI answer.

On payments, the only flow the documentation describes is a TON wallet transaction that the user confirms in the app; the docs we read do not mention Payme, Click or Uzum. The docs add that TelegramWidget.wallet is null where the user has no wallet in this app (an older app, or a country where the wallet is unavailable). Check this before promising a client "pay inside the message".

Telegram says the widget profile is version 1 and that features outside it are removed without breaking the rest. Building against these limits now is cheap: a whole widget is one small file.

What we ran

We opened the Bot API changelog (entry of 9 November 2026) and the widget documentation on 10 November 2026. We did not run a bot with widgets, so nothing here is a test result. Spot.uz and Telegram Info cover the release; the limits above come from Telegram's own pages.

Questions and answers

What is a Telegram widget?
A small interactive block inside a message: one HTML document with inline CSS and JavaScript, sent by a bot. The code is fixed when it is sent; only the state changes, and only the bot can change it.
Can a widget be sent to a group or channel?
Not to a channel: channels refuse widgets, sent directly or via the bot. Not to a group yet: in production widgets work only in the private chat with the bot, and users cannot forward them. Groups, inline mode and forwarding (including into channels) are only on the test server for now.
Can a widget call a company's website or API itself?
No. All network calls are blocked in the sandbox. The widget sends the bot a short request (1 to 64 bytes); the bot talks to your systems and changes the widget's state.
Do users need to update Telegram to see widgets?
Yes, users need an app version that supports widgets: per Telegram's docs, apps without support show the message as unsupported media with its caption. According to the Telegram Info channel (6 November 2026), widgets came with version 13.2 for Android, iOS and macOS and 7.4 for Telegram Desktop. The widget docs give no minimum version.

Sources

Prepared by the Nusrat Tech team with AI assistance, from the sources below.

  1. Bot API changelog: Bot API 10.4 — Telegram, 2026-11-10
  2. HTML widgets (Telegram Bots documentation) — Telegram, 2026-11-10
  3. Telegram 13.2 and Desktop 7.4 update (post 4448) — Telegram Info (secondary), 2026-11-10
  4. В Telegram появились интерактивные сообщения с HTML и JavaScript — Spot.uz (secondary), 2026-11-10

More news

  1. Search Console API now splits branded queries and filters several countries at once: what it means for sites in Uzbekistan

    On 16 November 2026 Google added three Performance report features to the Search Analytics API: a branded vs non-branded split, web multimodal search data, and filtering several countries or devices in one request. It matters to anyone who pulls Search Console data into their own reports.

  2. How to tell in analytics that a visit came from Google: what Google wrote and what it means for a site in Uzbekistan

    The referrer shows that Google sent a visit, but not the query, and not always the source: Search, Discover and Images send the same values. Queries are in Search Console.

  3. Google's November 2026 core update: what a site in Uzbekistan should do and when to read the traffic

    Google released its November core update on 10 November 2026; it applies worldwide and in all languages, so it covers Russian- and Uzbek-language sites too. The rollout can take up to two weeks, and Google advises waiting at least a week after it ends before analysing Search Console data.

All news

Want this working for your business?

Tell us what you sell and to whom. We answer in Telegram the same day.

Reach usDiscuss your project on Telegram

  • We reply the same working day, Tashkent time.
  • You write to Nodirkhon; he brings in whichever of us your problem needs.