BotNews
58.3K subscribers
55 links
The official source for news about the Telegram Bot API. https://core.telegram.org/bots
Download Telegram
Bot API 4.9 is ready for you.

Added the via_bot field to show through which bot a message was sent.
Supported video thumbnails for inline GIF and MPEG4 animations.
Supported the 🏀 animation for dice (in addition to 🎲 and 🎯).

Full change log:
https://core.telegram.org/bots/api-changelog#june-4-2020
This media is not supported in your browser
VIEW IN TELEGRAM
Introducing Bot API 5.0

• Run your own Bot API server.
Transfer Bot ownership to another account.
• New options for Webhooks.
• New method copyMessage to send a copy of any message.
• Support for Live Locations, including the latest changes.
• Support for Multiple Pinned Messages
• Support for File Albums
• Support for Anonymous Admins.
• Support for ⚽️ and 🎰 animated emoji.
• And much more, read the full changelog here:

https://core.telegram.org/bots/api-changelog#November-4-2020
Bot API 5.1

• Added updates about member status changes in chats: my_chat_member and chat_member
• Support for improved invite links
• Basic info about voice chats
• And more, read the full changelog here:

https://core.telegram.org/bots/api-changelog#march-9-2021

Warning: After one of the upcoming Bot API updates, some user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.
Bot API 5.2

• Added support for Payments 2.0, including inline mode for invoices.
• Added the field chat_type to the class InlineQuery.
• And more, see the full changelog for details.

https://core.telegram.org/bots/api-changelog#april-26-2021
Bot API 5.3

Personalized Commands
• Bots can now show commands that change to fit specific situations – like a user’s language, chat type, or admin status.
• A new Menu button now appears in chats with bots, making commands easier to see and send.

Custom Placeholders
• Bots can display a custom placeholder in the input field. See our latest blog for more on the bot menu and placeholders.

• And more, see the full changelog for details:

https://core.telegram.org/bots/api#june-25-2021
New payment provider added: Global Pay, Uzbekistan

More about bot payments:
https://core.telegram.org/bots/payments
If you are using a self-hosted instance of the Bot API, please update to version 5.3.3 that supports user identifiers larger than 2^31-1 as soon as possible.

Otherwise, please make sure that your code can correctly handle such user identifiers.
New payment providers added:

PSB
Portmone
Paymega
Cascad

More about bot payments:
https://core.telegram.org/bots/payments
Bot API 5.4

• Added support for new invite links with Join Requests. Bots can now manage users who requested to join a group or channel.
• And more, see the full changelog for details:
https://core.telegram.org/bots/api#november-5-2021
New payment provider added: LeoGaming 🇺🇦

More about bot payments:
https://core.telegram.org/bots/payments
Bot API 5.5

• Bots can now contact users who sent a join request to a chat where the bot is an admin – even if the user never interacted with the bot before.
• Added support for protected content in groups and channels.
• Added support for users posting as a channel in public groups and channel comments.
• Added support for mentioning users by their ID in inline keyboards.
• And more, see the full changelog for details:
https://core.telegram.org/bots/api#december-7-2021


Warning: As previously announced, user identifiers can now have up to 52 significant bits and require a 64-bit integer or double-precision float type to be stored safely.
Bot API 5.6

• Improved support for protected content: bots can now send it to any chat via the protect_content parameter.
• Implemented spoiler entities both as a new MessageEntity and a supported MarkdownV2 and HTML formatting option.

• See the full changelog for details:

https://core.telegram.org/bots/api-changelog#december-30-2021

Warning: Clients released before December 30, 2021 will display messages containing spoilers as "unsupported message".
Bot API 5.7

• Added support for Video Stickers.

https://core.telegram.org/bots/api-changelog#january-31-2022

Note: Clients released before January 31, 2022 will display messages containing video stickers as "unsupported message".
Bot API 6.0

• Added support for Web Apps.
KeyboardButton and InlineKeyboardButton can now be used to launch Web Apps.
• Added control over the bot's menu button via setChatMenuButton and getChatMenuButton.
• Added control over the bot's default admin rights via setMyDefaultAdministratorRights and getMyDefaultAdministratorRights.
• Added support for t.me links to add bots as admins.

• And more, see the full changelog for details:

https://core.telegram.org/bots/api-changelog#april-16-2022

Warning: After the next update, login_url will only allow HTTPS links.
New payment providers added:

Smart Glocal 🌎
Bank 131

More about bot payments:
https://core.telegram.org/bots/payments
New payment providers added:

Unlimint 🌎
ipay88 🇰🇭

More about bot payments:
https://core.telegram.org/bots/payments
As of the next update, it will no longer be possible to store the value of file_size fields in a signed 32-bit integer type. This change is necessary to support 4GB files which some users will be able to upload. We expect this update to arrive in June 2022.
Bot API 6.1

Telegram Premium
To support 4GB files uploaded by premium accounts, file_size in most media classes can no longer be stored in a signed 32-bit integer type.
Bots can now distinguish premium Users and Stickers with the new respective fields is_premium and premium_animation.

Web Apps
• Added several methods and fields to the class WebApp to handle API version, additional colors, haptic feedback and more.
• Added the events backButtonClicked, settingsButtonClicked and invoiceClosed.
• Updated ThemeParams, MainButton and WebAppInitData with new fields and methods.

Groups, Payments and Attachment Menu
• Bots can now process join requests created without an invite link – they will still receive a chat_join_request update.
• HTTP links for invoices can be generated with the new createInvoiceLink method.
• Bots can now detect when a user added them to their attachment menu via the new added_to_attachment_menu field. Integrated bots can now also be used in groups, supergroups and channels.

• Check that your bot's webhook was set by you with the new secret_token parameter.

• And more, see the full changelog for details:

https://core.telegram.org/bots/api-changelog#june-20-2022

Warning: Only HTTPS links are now allowed in login_url.
Bot API 6.2

Custom Emoji
Bots can identify custom emoji sent by Telegram Premium users via the new type "custom_emoji" and field custom_emoji_id added to the MessageEntity class.
Added the method getCustomEmojiStickers to obtain information about specific emoji.
Added the fields type and custom_emoji_id to the Sticker class.
Added sticker_type as a new field for StickerSet and as a new parameter for createNewStickerSet.

Web Apps
Implemented support for native dialog windows including alerts, popups with custom buttons and confirmation messages.
A confirmation dialog can now be shown when users close the web app. The dialog can be toggled via the enableClosingConfirmation and disableClosingConfirmation functions.
Added the field is_premium to the WebAppUser class — the standard User class already included this field, see version 6.1.

Added has_restricted_voice_and_video_messages to the Chat class to support the new premium setting.

And more, see the full changelog for details:

https://core.telegram.org/bots/api-changelog#august-12-2022

Note: The documentation for createNewStickerSet and StickerSet no longer mentions the contains_masks parameter and field respectively. In both instances, contains_masks will continue to work for backward compatibility but developers should use sticker_type instead.