GeezerVison is showing github.com — Full Support for Bot API 10.1 · Issue #5261 · python-telegram-bot/python-telegram-bot
Full Support for Bot API 10.1 #5261DescriptionWhat kind of feature are you missing? Where do you notice a shortcoming of PTB?
API 10.1
Telegram released Bot API 10.1 on June 11, 2026:
https://core.telegram.org/bots/api-changelog#june-11-2026
This release introduces Rich Messages and a few additional Bot API changes that are not yet exposed by PTB as far as I can tell. In particular, libraries and downstream integrations currently cannot use the new rich message methods and types through PTB's typed API.
Important
- Comment here or in the dev group what you want to work on so it can be assigned and tracked.
- Please copy the relevant part of the checklist from this issue to your PR and make sure to cover everything.
- If this is your first contribution, please read the contribution guide and feel free to reach out with any questions via https://t.me/pythontelegrambotchannel/105.
Describe the solution you'd like
Add full support for Bot API 10.1.
Rich Messages
- Added support for Rich Messages, allowing bots to send highly structured text and stream AI-generated replies with seamless rich formatting.
- Added the classes RichTextBold, RichTextItalic, RichTextUnderline, RichTextStrikethrough, RichTextSpoiler, RichTextDateTime, RichTextTextMention, RichTextSubscript, RichTextSuperscript, RichTextMarked, RichTextCode, RichTextCustomEmoji, RichTextMathematicalExpression, RichTextUrl, RichTextEmailAddress, RichTextPhoneNumber, RichTextBankCardNumber, RichTextMention, RichTextHashtag, RichTextCashtag, RichTextBotCommand, RichTextAnchor, RichTextAnchorLink, RichTextReference, and RichTextReferenceLink.
- Added the class RichText.
- Added the class RichBlockCaption.
- Added the class RichBlockTableCell.
- Added the class RichBlockListItem.
- Added the classes RichBlockParagraph, RichBlockSectionHeading, RichBlockPreformatted, RichBlockFooter, RichBlockDivider, RichBlockMathematicalExpression, RichBlockAnchor, RichBlockList, RichBlockBlockQuotation, RichBlockPullQuotation, RichBlockCollage, RichBlockSlideshow, RichBlockTable, RichBlockDetails, RichBlockMap, RichBlockAnimation, RichBlockAudio, RichBlockPhoto, RichBlockVideo, RichBlockVoiceNote, and RichBlockThinking.
- Added the class RichBlock.
- Added the class RichMessage.
- Added the field
rich_message to the class Message.
- Added the class InputRichMessage, describing a rich message to send.
- Added the class InputRichMessageContent and allowed it to be used as InputMessageContent in results of inline, guest, and Web App queries.
- Added the method sendRichMessage, allowing bots to send rich messages.
- Added the method sendRichMessageDraft, allowing bots to stream partial rich messages.
- Added the parameter
rich_message to the method editMessageText, allowing bots to edit rich messages.
Join Request Queries
Polls
Describe alternatives you've considered
For now, users can call the new methods through the raw Bot API request layer and build the InputRichMessage payloads as plain dictionaries. That works around the missing typed support, but it bypasses PTB's typed interface and convenience methods.
Additional context
Rich Messages are especially relevant for bots that render structured or AI-generated output: headings, lists, tables, code blocks, collapsible sections, LaTeX/math expressions, media blocks, and streamed draft replies. Reacted by Tengxiang Yang, Chiro, Alex, Egor M., nebenwelt, Viktor Oreshkin, Makar Korolenko, Sowtyy, Rich Lin, Mahdi Soleimani and 14 more Reacted by HZH, Aether/Pneuma, Tim Kleinschmidt, Chiro, Viktor Oreshkin, Max Dmitriev, Mukhsin Mukhtorov, Sergey Ivanychev, zotabee, RememberTheAir and 1 more ActivityAether0Pneuma commented on Jun 12, 2026 Poolitzer commented on Jun 12, 2026 mcar2107 commented on Jun 15, 2026 nebenwelt commented on Jun 16, 2026 tymrtn commented on Jun 18, 2026 I'd like to work on an initial Rich Messages slice, starting with the send-side API surface rather than the full type hierarchy in one large PR.
Proposed first PR scope:
InputRichMessageInputRichMessageContentBot.send_rich_messageBot.send_rich_message_draft- corresponding
User/Chat/Message shortcuts if they fit the existing patterns
- tests modeled after the existing
send_message_draft / send-method coverage
If you would prefer the foundational RichText* / RichBlock* classes first, or want the first PR split even smaller, I can adjust before opening the PR. harshil21 commented on Jun 18, 2026 To anyone wanting to contribute for this update right now - we are pausing development of this update until we complete major refactors which make implementing this and future API updates easier.
I know this is a very large and exciting update, but the wait should be worth it at the end. Reacted by Lelzin λ and zotabee tymrtn commented on Jun 18, 2026 Mukhsin0508 commented on Jul 1, 2026 capric98 commented on Jul 9, 2026
To anyone wanting to contribute for this update right now - we are pausing development of this update until we complete major refactors which make implementing this and future API updates easier.
I guess it will still take a while before the API 10.1 is available in this project.
Previously I made a simple vibe coding in my own project to implement (send|reply)_rich_message* functions and so far it works well. So I just put it here as a reference to anyone who want to use the new feature from bot API:
https://github.com/capric98/cyber-whaleyeah/blob/master/whaleyeah/rich_message.py AAraKKe commented on Jul 16, 2026 Well 10.2 is out now, I am guessing they might all be supported together? Or will you want to focus first in 10.1? I see this is tracking v23, by then I am guessing we will have multiple updates queuing up. tymrtn commented on Jul 17, 2026
To anyone wanting to contribute for this update right now - we are pausing development of this update until we complete major refactors which make implementing this and future API updates easier.
I know this is a very large and exciting update, but the wait should be worth it at the end.
Suggest we fork it and move on. All agree? Reacted by Poolitzer, AbelLykens, Eugene Dodin, Harshil, Javadz, RememberTheAir and Jose donoaga commented on Oct 15, 2026 Hi - I’d like to help implement Bot API 10.1 Rich Messages (part of #5261). I see several related PRs already ( #5263, #5275, #5356, #5359). I can work on either:
- the typed models / full RichText & RichBlock hierarchy (receiving side + Message.rich_message) or
- the remaining typed InputRichMessageContent / inline result support, or
- tests/docs and finishing any gaps for the send-side
Aweryc commented on Oct 21, 2026 tymrtn commented on Oct 21, 2026 Not sure, but this project appears to be stale. Given the work is already done and this is a high priority for many app/bot devs, perhaps a fork would be appropriate? harshil21 commented on Oct 21, 2026
29. Not sure, but this project appears to be stale. Given the work is already done and this is a high priority for many app/bot devs, perhaps a fork would be appropriate?
The work isn't done and the project is not stale, as you can clearly see in the git history Reacted by zotabee, Eugene Dodin, RememberTheAir and AbelLykens AbelLykens commented on Oct 23, 2026
29. > 29. Not sure, but this project appears to be stale. Given the work is already done and this is a high priority for many app/bot devs, perhaps a fork would be appropriate?
The work isn't done and the project is not stale, as you can clearly see in the git history
What's the best way to follow progress towards the rewrite which would allow working on this Bot API Support? harshil21 commented on Oct 23, 2026
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|