Telegram sendRichMessage Explained: From Bot API 10.1 to 10.3

Telegram sendRichMessage Explained: From Bot API 10.1 to 10.3

TL;DR. Telegram's sendRichMessage method, added in Bot API 10.1 (June 11, 2026), lets bots post structured content — tables, headings, collapsible sections, media, and now buttons — instead of a wall of MarkdownV2 text. Two follow-up releases, Bot API 10.2 (July 14) and 10.3 (August 24), added programmatic block assembly and in-message buttons. A rich message can run up to roughly 32,768 characters, eight times the 4,096-character cap on a normal sendMessage. It's built for reports, documentation, and streaming AI replies — not a drop-in replacement for a scheduled channel post.

Most Telegram scheduling tools, Autogram included, still publish channel posts with standard MarkdownV2 formatting today. See Autogram's current plans if you're scheduling regular posts now — this article is about what sendRichMessage adds on top, and when it's actually worth reaching for.

What is sendRichMessage?

Photo by Tiger Lily on Pexels

sendRichMessage is a Telegram Bot API method, added in Bot API 10.1 on June 11, 2026, that sends a message built from structured blocks instead of a single formatted string (Telegram, Bot API changelog, June 2026). Where sendMessage takes a text string and a parse_mode, sendRichMessage takes a rich_message object — an InputRichMessage made of typed blocks: paragraphs, section headings, tables, photos, videos, block quotes, footnotes, and a dedicated RichBlockThinking block meant for streaming AI output.

Telegram's own announcement on its BotNews channel put it plainly: bots "can now deliver highly structured content like business reports or media slideshows, while AI agents can seamlessly stream complex replies in real time" (Telegram BotNews, June 11, 2026). That's the actual use case — not a nicer way to bold a headline, but a way to send something closer to a formatted document than a chat bubble.

Two companion methods shipped alongside it:

• sendRichMessageDraft — streams a rich message incrementally, block by block, so an AI agent's reply can render as it's generated instead of appearing all at once.
• editMessageText gained a new rich_message parameter, so an existing rich message can be edited in place.

How rich messages grew: 10.1 → 10.2 → 10.3

Photo by RDNE Stock project on Pexels

Rich Messages didn't stop at launch. Telegram shipped two follow-up releases within ten weeks, and the second one landed just two days before this article was published — which is exactly why "sendRichMessage 10.1" articles elsewhere are already out of date.

Version	Date	What it added
Bot API 10.1	June 11, 2026	sendRichMessage, sendRichMessageDraft, rich_message on editMessageText, the core RichBlock types
Bot API 10.2	July 14, 2026	InputRichMessageMedia and a media field on InputRichMessage, InputMediaVoiceNote, and a blocks field for assembling rich messages programmatically
Bot API 10.3	August 24, 2026	Buttons inside rich messages (RichMessageButton, RichTextButton, RichBlockButtons), compact tables (is_compact), expandable block quotes, document blocks, and tg://document?id= links

(Telegram, Bot API changelog, June–August 2026.)

The 10.3 release matters most for channel operators: before it, a rich message was read-only content. Now a bot can put an actual button — an inline action, not just a link — inside a table row or a report block. That closes a real gap between "structured message" and "interactive message."

What sendRichMessage actually holds — and doesn't

A standard sendMessage caps out at 4,096 UTF-8 characters (8,192 with Telegram Premium on the receiving client) (Telegram limits reference, checked August 2026). Rich messages raise that ceiling substantially: per a technical breakdown of the Bot API 10.1 spec, a rich message tops out around 32,768 UTF-8 characters — about eight times the standard limit — with up to 500 nested blocks, 16 levels of nesting, 50 media attachments, and tables up to 20 columns wide (Habr, 2026).

Two limits worth internalizing before you plan content around this:

• It's still one message. A rich message is one chat_id + one rich_message payload, subject to Telegram's normal per-chat and per-second rate limits — it doesn't exempt a bot from flood control.
• 32,768 characters is a ceiling, not a target. A report that needs 500 nested blocks to read well in a chat window is usually a sign the content belongs on a page your bot links to, not inside the chat itself.

When to use rich messages (and when MarkdownV2 is enough)

Rich messages solve a specific problem: presenting structured data — a table, a multi-section report, a step list with headings — inside a single Telegram message, without the reader leaving the chat. That's genuinely new. MarkdownV2 can bold, italicize, and link, but it can't render an actual <table>-equivalent or a collapsible section.

For a typical scheduled channel post — an announcement, a promo, a link-out with a caption — MarkdownV2 formatting is still the right tool. It's simpler to author, every existing bot library already supports it, and a channel post rarely needs 20-column tables or 16 levels of nesting. Where rich messages earn their complexity is AI-agent tooling (streaming a generated answer as RichBlockThinking content), internal reporting bots, and documentation or support bots that need to show structured reference material without redirecting the user to a webpage.

That's also where the current generation of Telegram scheduling tools sits. Autogram, like most channel-scheduling products today, builds and schedules posts through Telegram's standard MarkdownV2 formatting — the same formatting every existing post in a channel already uses. sendRichMessage is new enough (10.3 shipped two days before this piece went live) that no channel-scheduling workflow has had time to build around it yet; adoption is going to follow use cases like AI-reply bots and reporting tools before it reaches routine channel content.

Pitfalls and gotchas

Photo by Ravi Roshan on Pexels

• Don't assume every client renders it the same way. Rich Messages are a Bot API-side structure; how a table or a collapsible block actually displays depends on the Telegram client version. Older clients may fall back to a plainer rendering.
• A rich message is not a Telegram Mini App. If you need real interactivity — forms, multi-step flows, persistent state — a Mini App is still the right tool; rich-message buttons cover simple actions, not application logic.
• Streaming needs sendRichMessageDraft, not repeated sendRichMessage calls. Calling sendRichMessage repeatedly to simulate streaming burns your rate limit fast; the draft method exists specifically to avoid that.
• Version-check before you build. A bot written against the 10.1 spec won't know about 10.3's button blocks. If your bot library wraps the Bot API, confirm which Bot API version it targets before you rely on RichBlockButtons.

Related reading

• Telegram Bot API 10.0 Guest Mode: What Channel Operators Need to Know — the release that came one month before Rich Messages, covering guest bots and bot-to-bot communication.
• Telegram MarkdownV2 Escaping: Why Posts Fail Silently (and the Fix) — the formatting most scheduled channel posts still use today.
• Telegram Bot API Rate Limits at Scale: What Breaks (and How to Stay Under) — rich messages don't change these limits; they still apply per chat.
• Telegram Managed Bots: What We Know Before the April Launch — another 2026 Bot API feature aimed at how bots operate inside channels.

FAQ

What is sendRichMessage in the Telegram Bot API?

It's a Bot API method, added in Bot API 10.1 (June 11, 2026), that sends a message built from structured blocks — tables, headings, media, quotes — instead of a single formatted text string like sendMessage does.

How is sendRichMessage different from sendMessage with MarkdownV2?

MarkdownV2 formats a single text string (bold, italic, links, code). sendRichMessage sends a structured object made of typed blocks, supports up to roughly 32,768 characters versus 4,096 for a standard message, and can include tables, collapsible sections, and (as of Bot API 10.3) buttons.

What did Bot API 10.2 and 10.3 add to Rich Messages?

Bot API 10.2 (July 14, 2026) added programmatic block-assembly support and media attachments on rich messages. Bot API 10.3 (August 24, 2026) added buttons inside rich messages, compact table mode, expandable block quotes, and document-link blocks.

Can I stream an AI-generated reply with sendRichMessage?

Yes — use sendRichMessageDraft to stream a rich message incrementally as it's generated, and the RichBlockThinking block type is built specifically for that use case.

Do Telegram scheduling tools like Autogram support sendRichMessage yet?

Not as of this writing. Autogram schedules channel posts using Telegram's standard MarkdownV2 formatting, the same formatting every existing post in a channel already uses. Rich Messages are new enough that adoption is still concentrated in AI-agent and reporting bots rather than channel-scheduling workflows.

Is sendRichMessage a replacement for a Telegram Mini App?

No. Rich messages add structure and (since 10.3) simple buttons to a single message, but they don't provide application state, multi-step forms, or persistent interactivity — that's still what Mini Apps are for.

Bottom line

sendRichMessage gives Telegram bots a genuinely new capability — structured, document-like messages instead of formatted text — and Telegram has iterated on it fast, from launch in June 2026 to buttons and compact tables by August. For most channel operators, today's scheduled posts still run on MarkdownV2, and that's fine. If you're building a reporting bot, a support bot, or anything that streams AI output, this is worth a closer look now. See how Autogram schedules and formats channel posts today.

Image credits

• Hero + inline 1 images by Tiger Lily and RDNE Stock project on Pexels
• Inline 2 image by Ravi Roshan on Pexels