Transferring ownership of bots
⁠⁠⁠⁠
Along with the update Bot API to version 5.0, it became possible to transfer ownership of a bot from one account to another.

For transmission:
- Two-factor authentication must be enabled at least 7 days prior to transfer. The password should not change during this time.
- The session from which the transfer takes place must exist for at least 24 hours.
- The user to whom the transfer is carried out must write to the bot and unblock it (if the bot was blacklisted by the user).

The transfer is carried out through the bot @botfather.

#BotAPI

Bot API has been updated to version 5.1

What's new:
— 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.

Warning: After one of the upcoming Bot API updates, 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.

core.telegram.org/bots/api-changelog#March-9-2021

#update #BotAPI

Bot API was updated to version 5.2

What's new:
- Payments 2.0 support
- Inline mode payments support
- Groups, supergroups, and channels payments support
- Optional tips support for sendInvoice method
- Now you can optionally allow paying for forwarded invoices
- Added chat_type field in inline mode, so a bot can identify from what kind of chat a request comes from
- Added scheduled Voice Chat message type
- Fixed mistakes in documentation

Important changes:
— In Bot API v5.3 a one-time change will happen which will update unique identifiers for photos
— Soon in large chats, join messages won't be displayed

Full changelog on the website.

#update #BotAPI

Bot API was updated to version 5.3

What's new?
Personalized Commands
— Bots can now show lists of commands tailored to specific situations - including localized commands for users with different languages, as well as different commands based on chat type or for specific chats, and special lists of commands for chat admins.
— Added the class BotCommandScope, describing the scope to which bot commands apply.
— Added the parameters scope and language_code to the method setMyCommands to allow bots specify different commands for different chats and users.
— Added the parameters scope and language_code to the method getMyCommands.
— Added the method deleteMyCommands to allow deletion of the bot's commands for the given scope and user language.
— Improved visibility of bot commands in Telegram apps with the new 'Menu' button in chats with bots, read more on the blog.

Custom Placeholders:
— Added the ability to specify a custom input field placeholder in the classes ReplyKeyboardMarkup and ForceReply.

And More:
— Improved documentation of the class ChatMember by splitting it into 6 subclasses.
— Renamed the method kickChatMember to banChatMember. The old method name can still be used.
— Renamed the method getChatMembersCount to getChatMemberCount. The old method name can still be used.
— Values of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto were changed.

Full changelog on the website.

#update #BotAPI

Bot API was updated to version 5.4

What's new:
— Added the the parameter creates_join_request to the methods createChatInviteLink and editChatInviteLink for managing chat invite links that create join requests.
— Added the fields creates_join_request and pending_join_request_count to the class ChatInviteLink.
— Added the field name to the class ChatInviteLink and the parameters name to the methods createChatInviteLink and editChatInviteLink for managing invite link names.
— Added updates about new requests to join the chat, represented by the class ChatJoinRequest and the field chat_join_request in the Update class. The bot must be an administrator in the chat with the can_invite_users administrator right to receive these updates.
— Added the methods approveChatJoinRequest and declineChatJoinRequest for managing requests to join the chat.
— Added support for the choose_sticker action in the method sendChatAction.

Full changelog on the website.

#update #BotAPI

Bot API was updated to version 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.

See the full changelog for details on the official website.

#update #BotAPI

Bot API was updated to version 5.6

— Improved support for Protected Content.
— Added the parameter protect_content to the methods sendMessage, sendPhoto, sendVideo, sendAnimation, sendAudio, sendDocument, sendSticker, sendVideoNote, sendVoice, sendLocation, sendVenue, sendContact, sendPoll, sendDice, sendInvoice, sendGame, sendMediaGroup, copyMessage, forwardMessage to allow sending messages with protected content to any chat.
— Added support for spoiler entities, which will work in Telegram versions released after December 30, 2021. Older clients will display unsupported message.
— Added new MessageEntity type “spoiler”.
— Added the ability to specify spoiler entities using HTML and MarkdownV2 formatting options.

See the full changelog for details on the official website.

#update #BotAPI

4GB files support for bots

It was announced on the official Bot API channel that 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 Telegram Premium users will be able to upload.

The Telegram Info editors remind you that non-updated bots and clients cannot work with files of the new size.

#BotAPI

Bot API was updated to version 6.1

What's new:
— 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.
— 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.
— 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.

See the full changelog for details on the official website.

#update #BotAPI

Telegram’s Bot Documentation has been completely overhauled

The official messenger news channel announced the completion of the documentation for bot developers.

Newcomers now have an easy way to learn about all the powerful features, and can build a bot from the step-by-step tutorial with examples for popular programming languages.

Experienced developers can explore recent updates and advanced features, ready for 2022 and beyond.

#BotAPI

Bot API was updated to version 6.3

What's new:
— Bots now support Topics in Groups.
— Added the fields is_forum and is_topic_message to Chat and Message respectively.
— Bots can send messages to a topic via the new message_thread_id parameter.
— Added service messages about new, closed and reopened topics, each with an optional field in Message.
— Bots can now create, close, edit and delete topics.
— Added chat member permissions for topic management, see can_manage_topics as a field in all relevant classes and as a parameter in promoteChatMember.

Multiple Usernames and Emoji Status
— Multiple Usernames are listed by the active_usernames field in the Chat class.
— Custom user statuses are now shown in the emoji_status_custom_emoji_id field returned from getChat.

See the full changelog for details on the official website.

#update #BotAPI

Bot API was updated to version 6.4

Forums
• Bots can now open, close, edit and toggle the visibility of the General Topic.
• Added support for new service messages, like ForumTopicEdited, GeneralForumTopicHidden and more.
• The method sendChatAction can now send actions to any thread or topic via the message_thread_id parameter.

Spoilers
• Added spoiler detection via the new has_media_spoiler field in the Message class.
• Bots can send media covered by a spoiler animation via the has_spoiler field in sendPhoto, sendVideo and sendAnimation.

Web Apps
• Added a native QR scanner popup, controllable via showScanQrPopup and closeScanQrPopup.
• Web Apps launched from the attachment menu can request clipboard text via readTextFromClipboard.
• Added a platform field, showing which platform the web app is being used on.

General
• Added the is_persistent field, to keep ReplyKeyboards open by default.

See the full changelog for details on the official website.

#update #BotAPI

Bot API has been updated to version 6.5

Chat and User Selection
• Bots can now show a friendly interface that can be used to select any channel, group or user.
• Added the KeyboardButtonRequestUser and KeyboardButtonRequestChat keyboard buttons for private chats.
• Added support for "user_shared" and "chat_shared" service messages, which hold the identifiers of users and chats shared via the buttons.

Improved Permissions
• Added support for granular media permissions by replacing can_send_media_messages in ChatMemberRestricted and ChatPermissions with several separate fields for the respective media type.
• Added the parameter use_independent_chat_permissions to the methods restrictChatMember and setChatPermissions.


• Added the field user_chat_id to the class ChatJoinRequest.

• And more, see the full changelog for details.

#update #BotAPI

Bot API updated to version 6.6

Highlight: users can now create emoji sets that adapt to app's theme

Localized Descriptions
• Bots now support localized descriptions that are shown based on the user's language.
• Added the methods setMyDescription and setMyShortDescription to set the bot's localized description and short description.
• Added the methods getMyDescription and getMyShortDescription to obtain the bot's description or short description for a given language.

Stickers and Emoji
• Bots can now create custom emoji sticker sets with createNewStickerSet.
• Added support for adaptive custom emoji colors via the needs_repainting parameter in the createNewStickerSet method.
• Added the ability to specify search keywords for stickers added to sticker sets.
• Improved editing options for sticker sets, including changing the title, deleting a pack, editing emoji lists and more.

Visit the official website for the full changelog.

#update #BotAPI

Bot API has been updated to version 6.7

Important changes:
• Now the web application can be opened via a link, inline button or inline mode, not only in private messages, but also in groups. This change allows all developers to create web bots for group chats. Previously, this feature was available only to those bots whose owners paid for the integration in the "Attach" menu. However, adding bots to the "Attach" menu is still possible only for a fee.
• BotFather now has commands for creating links to open web bots, and additional URL parameters can also be passed to them. Link example: t.me/fStikBot/catalog.

Other improvements:
• Added the ability to set different bot names for different user languages using the setMyName method.
• Added the ability to get the current bot name in the specified language as an object of the BotName class using the getMyName method.
• Added the ability to change bot settings from its profile in the official Telegram applications, including the ability to set animated profile pictures.
• Added support for custom emojis for bots with collectible username.

The full list of changes is on the official website.

#update #BotAPI

Bot API was updated to version 6.8

What's new:
• Added the field story to the class Message for messages with forwarded stories. Currently, it holds no information.
• Added the field voter_chat to the class PollAnswer, to contain channel chat voters in Polls. For backward compatibility, the field user in such objects will contain the user 136817688 (@Channel_Bot).
• Added the field emoji_status_expiration_date to the class Chat.
• Added the method unpinAllGeneralForumTopicMessages.
• Increased to 512 characters the maximum length of the startapp parameter in direct Web App links.

See the full changelog for details on the official website.

#update #BotAPI

Bot API was updated to version 6.9

What's new:
• Added the new administrator privileges can_post_stories, can_edit_stories and can_delete_stories to the classes ChatMemberAdministrator and ChatAdministratorRights.
• Added the parameters can_post_stories, can_edit_stories and can_delete_stories to the method promoteChatMember. Currently, bots have no use for these privileges besides assigning them to other administrators.
• Added the ability to set any header color using the setHeaderColor method.
• Added the field CloudStorage and the methods requestWriteAccess, requestContact to the class WebApp.
• Added the Web App events writeAccessRequested, contactRequested.
• Added the fields from_request and from_attachment_menu to the class WriteAccessAllowed.
• Added the fields added_to_attachment_menu, allows_write_to_pm to the class WebAppUser.

See the full changelog for details on the official website.

#update #BotAPI

Bot API was updated to version 7.1

Custom Emoji
• Bots can now get the custom emoji sticker set chosen by a group and use any custom emoji from it.

Boosts
• Added support for boost_added service messages, about new boosts added to the chat.
• Added the field sender_boost_count to the class Message, counting boosts added by the sender that are active on the message send date.

Stories
• Bots can now check if admins have the rights to post, edit and delete stories in supergroups.
• Added the field reply_to_story to the class Message.

See the full changelog for details on the official website.

#update #BotAPI

Biometrics in Mini Apps

A function named BiometricManager has been discovered in the source code of Telegram Mini Apps tools.

Presumably, this function will allow mini apps to request verification from the messenger to confirm your identity as the device owner. This will enable services to enhance the protection of your data or assets.

The @tginfo editorial team believes that mini apps will not receive any data related to biometrics. The tool will be able to process a response from the Telegram client, which has methods for biometric confirmation.

#BotAPI

Bot API Updated to Version 7.2

Integration with Business Accounts:
• Added the BusinessConnection class and updates about connecting or disconnecting a bot to a business account, represented by the field 'business_connection' in the Update class.
• Added updates about deleting messages in a business account connected to a bot.

Acting on Behalf of Business Accounts:
• Added the field 'business_connection_id' to the Message class.
• Added the field 'sender_business_bot' to the Message class.
• Added the parameter 'business_connection_id' to the sendChatAction method.

Business Account Information:
• Added the classes 'BusinessOpeningHours' and 'BusinessOpeningHoursInterval'.
• Added the field 'business_opening_hours' to the Chat class.

Sticker Sets with Mixed Format:
• Removed the fields 'is_animated' and 'is_video' from the StickerSet class.
• Added the field 'format' to the InputSticker class.
• Removed the parameter 'sticker_format' from the createNewStickerSet method.
• Increased the maximum number of stickers in any set to 120.
• Allowed uploading stickers in WEBM format using SendSticker.

The full list of changes is available on the official website.

#update #BotAPI