-The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram. -To learn how to create and set up a bot, please consult our Introduction to Bots »
+The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram.
To learn how to create and set up a bot, please consult our Introduction to Bots »
You will find all changes to our Bot API on this page.
-Recent changes
+Recent changes
-Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk
April 16, 2022
+April 16, 2022
Bot API 6.0
- Added support for Web Apps, see the detailed manual here. (blog announcement)
- Added the class WebAppInfo and the fields web_app to the classes KeyboardButton and InlineKeyboardButton. -
- Added the class SentWebAppMessage and the method answerWebAppQuery for sending an answer to a Web App query, which originated from an inline button of the 'web_app' type. +
- Added the class SentWebAppMessage and the method answerWebAppQuery for sending an answer to a Web App query, which originated from an inline button of the 'web_app' type.
- Added the class WebAppData and the field web_app_data to the class Message. -
- Added the class MenuButton and the methods setChatMenuButton and getChatMenuButton for managing the behavior of the bot's menu button in private chats. -
- Added the class ChatAdministratorRights and the methods setMyDefaultAdministratorRights and getMyDefaultAdministratorRights for managing the bot's default administrator rights. +
- Added the class MenuButton and the methods setChatMenuButton and getChatMenuButton for managing the behavior of the bot's menu button in private chats. +
- Added the class ChatAdministratorRights and the methods setMyDefaultAdministratorRights and getMyDefaultAdministratorRights for managing the bot's default administrator rights.
- Added support for t.me links that can be used to add the bot to groups and channels as an administrator.
- Added the field last_synchronization_error_date to the class WebhookInfo.
- Renamed the field can_manage_voice_chats to can_manage_video_chats in the class ChatMemberAdministrator. The old field will remain temporarily available. @@ -72,30 +71,29 @@ To learn how to create and set up a bot, please consult our WARNING!
- Added support for Video Stickers.
- Added the field is_video to the classes Sticker and StickerSet.
- Added the parameter webm_sticker to the methods createNewStickerSet and addStickerToSet.
- 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 new MessageEntity type “spoiler”.
- Added the ability to specify spoiler entities using HTML and MarkdownV2 formatting options.
- Bots are now allowed to contact users who sent a join request to a chat where the bot is an administrator with the can_invite_users administrator right – even if the user never interacted with the bot before. +
- Bots are now allowed to contact users who sent a join request to a chat where the bot is an administrator with the can_invite_users administrator right – even if the user never interacted with the bot before.
- Added support for mentioning users by their ID in inline keyboards. This will only work in Telegram versions released after December 7, 2021. Older clients will display unsupported message.
- Added the methods banChatSenderChat and unbanChatSenderChat for banning and unbanning channel chats in supergroups and channels.
- Added the field has_private_forwards to the class Chat for private chats, which can be used to check the possibility of mentioning the user by their ID. @@ -105,7 +103,7 @@ After the next update, only HTTPS links will be allowed in login_url in
- Added the the parameter
creates_join_requestto the methods createChatInviteLink and editChatInviteLink for managing chat invite links that create join requests (read more about this on our blog).
@@ -117,11 +115,10 @@ After the next update, only HTTPS links will be allowed in login_url in
- Added the class BotCommandScope, describing the scope to which bot commands apply.
- Added the parameters
scopeandlanguage_codeto the method setMyCommands to allow bots specify different commands for different chats and users. - Added the parameters
scopeandlanguage_codeto 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. +
- 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.
- Support for Payments 2.0, see this manual for more details about the Bot Payments API.
- Added the type InputInvoiceMessageContent to support sending invoices as inline query results.
- Allowed sending invoices to group, supergroup and channel chats.
- Added the fields max_tip_amount and suggested_tip_amounts to the method sendInvoice to allow adding optional tips to the payment. -
- The parameter start_parameter of the method sendInvoice became optional. If the parameter isn't specified, the invoice can be paid directly from forwarded messages. +
- The parameter start_parameter of the method sendInvoice became optional. If the parameter isn't specified, the invoice can be paid directly from forwarded messages.
- Added the field chat_type to the class InlineQuery, containing the type of the chat, from which the inline request was sent.
- Added the type VoiceChatScheduled and the field voice_chat_scheduled to the class Message. -
- Fixed an error in sendChatAction documentation to correctly mention "record_voice" and "upload_voice" instead of "record_audio" and "upload_audio" for related to voice note actions. Old action names will still work for backward compatibility. +
- Fixed an error in sendChatAction documentation to correctly mention “record_voice” and “upload_voice” instead of “record_audio” and “upload_audio” for related to voice note actions. Old action names will still work for backward compatibility.
- Bot API source code is now available at telegram-bot-api. You can now run your own Bot API server locally, boosting your bots' performance. +
- Bot API source code is now available at telegram-bot-api. You can now run your own Bot API server locally, boosting your bots' performance.
- Added the method logOut, which can be used to log out from the cloud Bot API server before launching your bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive all updates.
- Added the method close, which can be used to close the bot instance before moving it from one local server to another.
- The getChat request now returns the user's bio for private chats if available. +
- The getChat request now returns the user's bio for private chats if available.
- The getChat request now returns the identifier of the linked chat for supergroups and channels, i.e. the discussion group identifier for a channel and vice versa.
- The getChat request now returns the location to which the supergroup is connected (see Local Groups). Added the class ChatLocation to represent the location.
- Added the parameter only_if_banned to the method unbanChatMember to allow safe unban. @@ -253,7 +245,7 @@ After one of the upcoming Bot API updates, some user identifiers will become big
- Added the field live_period to the class Location, representing a maximum period for which the live location can be updated. -
- Added support for live location [heading](https://en.wikipedia.org/wiki/Heading_(navigation)): added the field heading to the classes Location, InlineQueryResultLocation, InputLocationMessageContent and the parameter heading to the methods sendLocation and editMessageLiveLocation. +
- Added support for live location heading: added the field heading to the classes Location, InlineQueryResultLocation, InputLocationMessageContent and the parameter heading to the methods sendLocation and editMessageLiveLocation.
- Added support for proximity alerts in live locations: added the field proximity_alert_radius to the classes Location, InlineQueryResultLocation, InputLocationMessageContent and the parameter proximity_alert_radius to the methods sendLocation and editMessageLiveLocation.
- Added the type ProximityAlertTriggered and the field proximity_alert_triggered to the class Message.
- Added possibility to specify the horizontal accuracy of a location. Added the field horizontal_accuracy to the classes Location, InlineQueryResultLocation, InputLocationMessageContent and the parameter horizontal_accuracy to the methods sendLocation and editMessageLiveLocation. @@ -277,14 +269,14 @@ After one of the upcoming Bot API updates, some user identifiers will become big
- Supported the new football and slot machine animations for the random dice. Choose between different animations (dice, darts, basketball, football, slot machine) by specifying the emoji parameter in the method sendDice.
- Added the new field via_bot to the Message object. You can now know which bot was used to send a message.
- Supported video thumbnails for inline GIF and MPEG4 animations.
- Supported the new basketball animation for the random dice. Choose between different animations (dice, darts, basketball) by specifying the emoji parameter in the method sendDice.
- Supported explanations for Quizzes 2.0. Add explanations by specifying the parameters explanation and explanation_parse_mode in the method sendPoll. @@ -294,19 +286,19 @@ After one of the upcoming Bot API updates, some user identifiers will become big
- Supported the new darts animation for the dice mini-game. Choose between the default dice animation and darts animation by specifying the parameter emoji in the method sendDice.
- Added the field emoji to the Dice object.
- Added the method sendDice for sending a dice message, which will have a random value from 1 to 6. (Yes, we're aware of the "proper" singular of die. But it's awkward, and we decided to help it change. One dice at a time!) +
- Added the method sendDice for sending a dice message, which will have a random value from 1 to 6. (Yes, we're aware of the “proper” singular of die. But it's awkward, and we decided to help it change. One dice at a time!)
- Added the field dice to the Message object. -
- Added the method getMyCommands for getting the current list of the bot's commands. -
- Added the method setMyCommands for changing the list of the bot's commands through the Bot API instead of @BotFather. +
- Added the method getMyCommands for getting the current list of the bot's commands. +
- Added the method setMyCommands for changing the list of the bot's commands through the Bot API instead of @BotFather.
- Added the ability to create animated sticker sets by specifying the parameter tgs_sticker instead of png_sticker in the method createNewStickerSet.
- Added the ability to add animated stickers to sets created by the bot by specifying the parameter tgs_sticker instead of png_sticker in the method addStickerToSet.
- Added the field thumb to the StickerSet object.
- Added the ability to change thumbnails of sticker sets created by the bot using the method setStickerSetThumb.
- Supported Polls 2.0. @@ -318,19 +310,19 @@ After one of the upcoming Bot API updates, some user identifiers will become big
- Added more information about the bot in response to the getMe request: added the fields can_join_groups, can_read_all_group_messages and supports_inline_queries to the User object.
- Added the optional field language to the MessageEntity object.
- Added support for two new MessageEntity types, underline and strikethrough.
- Added support for nested MessageEntity objects. Entities can now contain other entities. If two entities have common characters then one of them is fully contained inside the other.
- Added support for nested entities and the new tags
<u>/<ins>(for underlined text) and<s>/<strike>/<del>(for strikethrough text) in parse mode HTML. - Added a new parse mode, MarkdownV2, which supports nested entities and two new entities
__(for underlined text) and~(for strikethrough text). Parse mode Markdown remains unchanged for backward compatibility.
- - Added the field file_unique_id to the objects Animation, Audio, Document, PassportFile, PhotoSize, Sticker, Video, VideoNote, Voice, File and the fields small_file_unique_id and big_file_unique_id to the object ChatPhoto. The new fields contain a unique file identifier, which is supposed to be the same over time and for different bots, but can't be used to download or reuse the file. +
- Added the field file_unique_id to the objects Animation, Audio, Document, PassportFile, PhotoSize, Sticker, Video, VideoNote, Voice, File and the fields small_file_unique_id and big_file_unique_id to the object ChatPhoto. The new fields contain a unique file identifier, which is supposed to be the same over time and for different bots, but can't be used to download or reuse the file.
- Added the field custom_title to the ChatMember object.
- Added the new method setChatAdministratorCustomTitle to manage the custom titles of administrators promoted by the bot.
- Added the field slow_mode_delay to the Chat object.
- Added support for animated stickers. New field is_animated in Sticker and StickerSet objects, animated stickers can now be used in sendSticker and InlineQueryResultCachedSticker. @@ -338,48 +330,49 @@ After one of the upcoming Bot API updates, some user identifiers will become big
- The field all_members_are_administrators has been removed from the documentation for the Chat object. The field is still returned in the object for backward compatibility, but new bots should use the permissions field instead.
- Added support for more permissions for group and supergroup members: added the new field can_send_polls to ChatMember object, added can_change_info, can_invite_users, can_pin_messages in ChatMember object for restricted users (previously available only for administrators).
- The method restrictChatMember now takes the new user permissions in a single argument of the type ChatPermissions. The old way of passing parameters will keep working for a while for backward compatibility. -
- Added description support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to setChatDescription and receive the group's description in the Chat object in the response to getChat method. -
- Added invite_link support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to exportChatInviteLink and receive the group's invite link in the Chat object in the response to getChat method. +
- Added description support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to setChatDescription and receive the group's description in the Chat object in the response to getChat method. +
- Added invite_link support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to exportChatInviteLink and receive the group's invite link in the Chat object in the response to getChat method.
- File identifiers from the ChatPhoto object are now invalidated and can no longer be used whenever the photo is changed. -
- All webhook requests from the Bot API are now coming from the subnets
149.154.160.0/20and91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
+ - All webhook requests from the Bot API are now coming from the subnets
149.154.160.0/20and91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks. - As of the next Bot API update (version 4.5), nested MessageEntity objects will be allowed in message texts and captions. Please make sure that your code can correctly handle such entities.
- Added support for Seamless Telegram Login on external websites.
- Added the new object LoginUrl and the new field login_url to the InlineKeyboardButton object which allows to automatically authorize users before they go to a URL specified by the bot. Users will be asked to confirm authorization in their Telegram app (needs version 5.7 or higher) when they press the button:
- Added the field
reply_markupto the Message object, containing the inline keyboard attached to the message. - If a message with an inline keyboard is forwarded, the forwarded message will now have an inline keyboard if the keyboard contained only url and login_url buttons or if the message was sent via a bot and the keyboard contained only url, login_url, switch_inline_query or switch_inline_query_current_chat buttons. In the latter case, switch_inline_query_current_chat buttons are replaced with switch_inline_query buttons.
- Bots now receive the edited_message Update even if only Message.reply_markup has changed.
- Bots that have the can_edit_messages right in a channel can now use the method editMessageReplyMarkup for messages written by other administrators forever without the 48 hours limit. -
- Don't forget that starting in July 2019, webhook requests from Bot API will be coming from the subnets
149.154.160.0/20and91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
+ - Don't forget that starting in July 2019, webhook requests from Bot API will be coming from the subnets
149.154.160.0/20and91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks. - Added support for native polls: added the object Poll, the methods sendPoll and stopPoll and the field poll in the Message and Update objects.
- The method deleteMessage can now be used to delete messages sent by a user to the bot in private chats within 48 hours. -
- Added support for pinned messages in basic groups in addition to supergroups and channel chats: you can pass group's chat_id to pinChatMessage and unpinChatMessage, and receive the pinned group message in Chat object. +
- Added support for pinned messages in basic groups in addition to supergroups and channel chats: you can pass group's chat_id to pinChatMessage and unpinChatMessage, and receive the pinned group message in Chat object.
- Added the field is_member to the ChatMember object, which can be used to find whether a restricted user is a member of the chat.
- Added the field forward_sender_name to the Message object, containing name of the sender who has opted to hide their account. -
- Starting in July 2019, webhook requests from Bot API will be coming from the subnets
149.154.160.0/20and91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
+ - Starting in July 2019, webhook requests from Bot API will be coming from the subnets
149.154.160.0/20and91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks. - Document thumbnails now should be inscribed in a 320x320 square instead of 90x90.
- Added support for translated versions of documents in Telegram Passport.
- New field translation in EncryptedPassportElement.
- New errors: PassportElementErrorTranslationFile and PassportElementErrorTranslationFiles and PassportElementErrorUnspecified.
- Added support for Telegram Passport. See the official announcement on the blog and the manual for details. @@ -391,35 +384,35 @@ After one of the upcoming Bot API updates, some user identifiers will become big
- Added the field animation to the Message object. For backward compatibility, when this field is set, the document field will be also set.
- Added two new MessageEntity types: cashtag and phone_number.
- Added support for Foursquare venues: added the new field foursquare_type to the objects Venue, InlineQueryResultVenue and InputVenueMessageContent, and the parameter foursquare_type to the sendVenue method. -
- You can now create inline mentions of users, who have pressed your bot's callback buttons. +
- You can now create inline mentions of users, who have pressed your bot's callback buttons.
- You can now use the
Retry-Afterresponse header to configure the delay after which the Bot API will retry the request after an unsuccessful response from a webhook. - If a webhook returns the HTTP error
410 Gonefor all requests for more than 23 hours successively, it can be automatically removed. - Added vCard support when sharing contacts: added the field vcard to the objects Contact, InlineQueryResultContact, InputContactMessageContent and the method sendContact.
- Supported text formatting in media captions. Specify the desired parse_mode (Markdown or HTML) when you provide a caption. -
- In supergroups, if the bot receives a message that is a reply, it will also receive the message to which that message is replying – even if the original message is inaccessible due to the bot's privacy settings. (In other words, replying to any message in a supergroup with a message that mentions the bot or features a command for it acts as forwarding the original message to the bot). -
- Added the new field connected_website to Message. The bot will receive a message with this field in a private chat when a user logs in on the bot's connected website using the Login Widget and allows sending messages from your bot. +
- In supergroups, if the bot receives a message that is a reply, it will also receive the message to which that message is replying – even if the original message is inaccessible due to the bot's privacy settings. (In other words, replying to any message in a supergroup with a message that mentions the bot or features a command for it acts as forwarding the original message to the bot). +
- Added the new field connected_website to Message. The bot will receive a message with this field in a private chat when a user logs in on the bot's connected website using the Login Widget and allows sending messages from your bot.
- Added the new parameter supports_streaming to the sendVideo method and a field with the same name to the InputMediaVideo object.
- Added the new method sendMediaGroup and two kinds of InputMedia objects to support the new albums feature.
- Added support for pinning messages in channels. pinChatMessage and unpinChatMessage accept channels.
- Added the new fields provider_data, send_phone_number_to_provider, send_email_to_provider to sendInvoice for sharing information about the invoice with the payment provider.
- Bots can now send and receive Live Locations. Added new field live_period to the sendLocation method and the editMessageLiveLocation and stopMessageLiveLocation methods as well as the necessary objects for inline bots.
- Bots can use the new setChatStickerSet and deleteChatStickerSet methods to manage group sticker sets. -
- The getChat request now returns the group's sticker set for supergroups if available. +
- The getChat request now returns the group's sticker set for supergroups if available.
- Bots now receive entities from media captions in the new field caption_entities in Message.
- Bots can now mention users via inline mentions, without using usernames. @@ -427,13 +420,13 @@ After one of the upcoming Bot API updates, some user identifiers will become big
- Added the new fields author_signature and forward_signature to the Message object.
- Added the new field is_bot to the User object.
- Added new methods for working with stickers: getStickerSet, uploadStickerFile, createNewStickerSet, addStickerToSet, setStickerPositionInSet, and deleteStickerFromSet.
- Added the fields set_name and mask_position to the Sticker object, plus two new objects, StickerSet, and MaskPosition.
- Added new methods restrictChatMember and promoteChatMember to manage users and admins, added new parameter until_date to kickChatMember for temporary bans. @@ -441,10 +434,10 @@ After one of the upcoming Bot API updates, some user identifiers will become big
- Added the new fields photo, description and invite_link to the Chat object.
- Added the new fields until_date, can_be_edited, can_change_info, can_post_messages, can_edit_messages, can_delete_messages, can_invite_users, can_restrict_members, can_pin_messages, can_promote_members, can_send_messages, can_send_media_messages, can_send_other_messages and can_add_web_page_previews to the ChatMember object.
- Your bot can now accept payments for goods and services via Telegram.
- Added new kinds of updates, shipping_query and pre_checkout_query, and new types of message content, invoice and successful_payment. @@ -458,7 +451,7 @@ After one of the upcoming Bot API updates, some user identifiers will become big
- The User object now may have a language_code field that contains the IETF language tag of the user's language. +
- The User object now may have a language_code field that contains the IETF language tag of the user's language.
- Thanks to this, your bot can now offer localized responses to users that speak different languages.
- Inline keyboards with switch_inline_query and switch_inline_query_current_chat can no longer be sent to channels because they are useless there.
- New fields gif_duration in InlineQueryResultGif and mpeg4_duration in InlineQueryResultMpeg4Gif.
- Use the new field max_connections in setWebhook to optimize your bot's server load +
- Use the new field max_connections in setWebhook to optimize your bot's server load
- Use allowed_updates in setWebhook and getUpdates to selectively subscribe to updates of a certain type. Among other things, this allows you to stop getting updates about new posts in channels where your bot is an admin.
- deleteWebhook moved out of setWebhook to get a whole separate method for itself.
-
-
Modified bot privacy mode for the sake of consistency.
+ - Modified bot privacy mode for the sake of consistency. +
Your bot can now get updates about posts in channels. Added new fields channel_post and edited_channel_post to Update.
--
-
Your bot can now get updates about posts in channels. Added new fields channel_post and edited_channel_post to Update.
-
- -
-
You can now update high scores to a lower value by using the new force parameter in setGameScore. Handy for punishing cheaters or fixing errors in your game's High Score table.
-
- -
-
Starting today, messages with high scores will be updated with new high scores by default. Use disable_edit_message in setGameScore if you don't want this.
-
- -
-
The edit_message parameter from setGameScore is no longer in use. For backward compatibility, it will be taken into account for a while, unless disable_edit_message is passed explicitly.
-
- -
-
Added the new field forward_from_message_id to Message.
-
- -
-
Added the new parameter cache_time to answerCallbackQuery. Will eventually work in Telegram apps — somewhere after version 3.14, maybe 3.15.
-
- -
-
Renamed hide_keyboard to remove_keyboard in ReplyKeyboardRemove for clarity. hide_keyboard will still work for a while for backward compatibility.
+ You can now update high scores to a lower value by using the new force parameter in setGameScore. Handy for punishing cheaters or fixing errors in your game's High Score table.
+- Starting today, messages with high scores will be updated with new high scores by default. Use disable_edit_message in setGameScore if you don't want this. +
- The edit_message parameter from setGameScore is no longer in use. For backward compatibility, it will be taken into account for a while, unless disable_edit_message is passed explicitly. +
- Added the new field forward_from_message_id to Message. +
- Added the new parameter cache_time to answerCallbackQuery. Will eventually work in Telegram apps — somewhere after version 3.14, maybe 3.15. +
- Renamed hide_keyboard to remove_keyboard in ReplyKeyboardRemove for clarity. hide_keyboard will still work for a while for backward compatibility.
- New tools for building HTML5 games.
- New method sendGame, new object InlineQueryResultGame, new field game in Message. @@ -519,50 +497,40 @@ If you're not a developer, you may like Guide to All Things Webhook that describes every pothole you can run into on the webhook road. +
- Making life easier for webhook users. Added a detailed Guide to All Things Webhook that describes every pothole you can run into on the webhook road. +
New method getWebhookInfo to check current webhook status.
--
-
New method getWebhookInfo to check current webhook status.
-
- -
-
Added the option to specify an HTTP URL for a file in all methods where InputFile or file_id can be used (except voice messages). Telegram will get the file from the specified URL and send it to the user. Files must be smaller than 5 MB for photos and smaller than 20 MB for all other types of content.
-
- -
-
Use the new url parameter in answerCallbackQuery to create buttons that open your bot with user-specific parameters.
-
- -
-
Added new field switch_inline_query_current_chat in InlineKeyboardButton.
-
- -
-
Added caption fields to sendAudio, sendVoice, InlineQueryResultAudio, InlineQueryResultVoice, InlineQueryResultCachedAudio, and InlineQueryResultCachedVoice.
+ Added the option to specify an HTTP URL for a file in all methods where InputFile or file_id can be used (except voice messages). Telegram will get the file from the specified URL and send it to the user. Files must be smaller than 5 MB for photos and smaller than 20 MB for all other types of content.
+- Use the new url parameter in answerCallbackQuery to create buttons that open your bot with user-specific parameters. +
- Added new field switch_inline_query_current_chat in InlineKeyboardButton. +
- Added caption fields to sendAudio, sendVoice, InlineQueryResultAudio, InlineQueryResultVoice, InlineQueryResultCachedAudio, and InlineQueryResultCachedVoice.
- New field all_members_are_administrators in the Chat object.
- Certain server responses may now contain the new parameters field with expanded info on errors that occurred while processing your requests.
- Inline keyboards may now be used in group chats. Channels coming soon.
- Check out @vote and @like for examples.
- Bot API 2.1. Added more tools for group administrator bots. Your bot can now get a list of administrators and members count in a group, check a user's current status (administrator, creator, left the group, kicked from the group), and leave a group. +
- Bot API 2.1. Added more tools for group administrator bots. Your bot can now get a list of administrators and members count in a group, check a user's current status (administrator, creator, left the group, kicked from the group), and leave a group.
- Added new methods: getChat, leaveChat, getChatAdministrators, getChatMember, getChatMembersCount.
- Added support for edited messages and new mentions from Telegram v.3.9. New fields: edited_message in Update, edit_date in Message, user in MessageEntity. New value text_mention for the type field in MessageEntity.
- Added consistency to what messages bots get in groups and supergroups. See updated FAQ for details »
- Added the field emoji to the Sticker object. Your bot can now know the emoji a sticker corresponds to.
- Added the field forward_from_chat to the Message object for messages forwarded from channels.
- New inline keyboards with callback and URL buttons. Added new objects InlineKeyboardMarkup, InlineKeyboardButton and CallbackQuery, added reply_markup fields to all InlineQueryResult objects. Added field callback_query to the Update object, new method answerCallbackQuery. @@ -582,70 +550,71 @@ If you're not a developer, you may like Message object. Added new objects MessageEntity and Venue, new methods sendVenue and sendContact.
- Renamed the fields new_chat_participant and left_chat_participant of the Message object to new_chat_member and left_chat_member.
- Added the disable_notification parameter to all methods that send messages or any kind.
- Removed backward compatibility from the method sendAudio. Voice messages now must be sent using the method sendVoice. There is no more need to specify a non-empty title or performer while sending the audio by file_id.
- By the way, you can use both HTML-style and markdown-style formatting in your bot's messages to send bold, italic or fixed-width text and inline links. All official Telegram clients support this. See Formatting options for details. +
- By the way, you can use both HTML-style and markdown-style formatting in your bot's messages to send bold, italic or fixed-width text and inline links. All official Telegram clients support this. See Formatting options for details.
- You can now collect feedback on which results provided by your inline bot get chosen by the users. Added the
setinlinefeedbackcommand for Botfather, new type ChosenInlineResult, new field chosen_inline_result to the Update object. - Added support for Inline Mode, a new way for people to contact your bot by typing its username and a query in the text input field in any chat. Enable by sending
/setinlineto @BotFather. - New optional field inline_query added to the Update object.
- Added new method answerInlineQuery and new objects InlineQuery, InlineQueryResultArticle, InlineQueryResultPhoto, InlineQueryResultGif, InlineQueryResultMpeg4Gif and InlineQueryResultVideo.
- Added support for supergroups. The Type field in the Chat object can now contain 'supergroup'. +
- Added support for supergroups. The Type field in the Chat object can now contain 'supergroup'.
- New optional fields added to the Message object: supergroup_chat_created, migrate_to_chat_id, migrate_from_chat_id and channel_chat_created.
- Added initial channel support for bots (no Telegram clients support this at the moment, please wait for updates):
- The Chat field in the Message is now of the new type Chat. -
- You can now pass a channel username (in the format
@channelusername) in the place of chat_id in all methods (and instead of from_chat_id in forwardMessage). For this to work, the bot must be an administrator in the channel (and that's exactly what Telegram clients don't support yet — adding bots as administrators coming soon).
+ - You can now pass a channel username (in the format
@channelusername) in the place of chat_id in all methods (and instead of from_chat_id in forwardMessage). For this to work, the bot must be an administrator in the channel (and that's exactly what Telegram clients don't support yet — adding bots as administrators coming soon). - You can now pass parameters using application/json (please note that this doesn't work for file uploads: use multipart/form-data to upload files). +
- You can now pass parameters using application/json (please note that this doesn't work for file uploads: use multipart/form-data to upload files).
- Added very basic markdown support. New field parse_mode added to sendMessage. For the moment messages with markdown will be displayed correctly only in Telegram for Android. Other official apps will catch up soon.
- Added support for self-signed certificates: upload your certificate using the certificate parameter in the setWebhook method.
- You can now make new requests when responding to webhook updates.
- Added new type Voice and new method sendVoice for sending voice messages.
- Earlier Audio and sendAudio should now be used for sending music files. Telegram clients will show such files in the in-app music player. If you were using sendAudio for your bot to send voice messages, please use sendVoice instead.
- Added optional fields performer, title to the Audio object and sendAudio method.
- Added optional field voice to the Message object.
- The thumb field is now optional for Video, Sticker and Document objects
- The API now supports both video and photo captions. The caption field has been removed from the Video object and added to the Message object instead.
- caption and duration optional fields have been added to the sendVideo method.
- Fixed typo: user_id in the Contact object is now correctly labeled as Integer, not String
-After the next update, only HTTPS links will be allowed in login_url inline keyboard buttons.
+ WARNING!
After the next update, only HTTPS links will be allowed in login_url inline keyboard buttons.
-
January 31, 2022
+January 31, 2022
Bot API 5.7
December 30, 2021
+December 30, 2021
Bot API 5.6
December 7, 2021
+December 7, 2021
Bot API 5.5
-
-
Note: After this update it will become impossible to forward messages from some chats. Use the fields has_protected_content in the classes Message and Chat to check this.
Note: After this update users are able to send messages on behalf of channels they own. Bots are expected to use the field sender_chat in the class Message to correctly support such messages.
Note: 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.
-November 5, 2021
+November 5, 2021
Bot API 5.4
-+
WARNING!
2^31 - 1before the end of this year 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.
User identifiers will become bigger than2^31 - 1before the end of this year 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.
-
June 25, 2021
+June 25, 2021
Bot API 5.3
Personalized Commands
-
@@ -129,8 +126,8 @@ User identifiers will become bigger than
2^31 - 1 before the end of
Custom Placeholders
-
@@ -145,39 +142,35 @@ User identifiers will become bigger than
2^31 - 1 before the end of
-+
2^31 - 1and 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.
After one of the upcoming Bot API updates, user identifiers will become bigger than2^31 - 1and 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.
-
April 26, 2021
+April 26, 2021
Bot API 5.2
-+
file_unique_idin objects of the type PhotoSize and of the fieldssmall_file_unique_idandbig_file_unique_idin objects of the type ChatPhoto.
After the next Bot API update (Bot API 5.3) there will be a one-time change of the value of the fieldfile_unique_idin objects of the type PhotoSize and of the fieldssmall_file_unique_idandbig_file_unique_idin objects of the type ChatPhoto.
-+
Service messages about non-bot users joining the chat will be soon removed from large groups. We recommend using the “chat_member” update as a replacement.
-+
2^31 - 1and 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.
After one of the upcoming Bot API updates, user identifiers will become bigger than2^31 - 1and 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.
-
March 9, 2021
+March 9, 2021
Bot API 5.1
Added two new update types
-
@@ -206,15 +199,14 @@ After one of the upcoming Bot API updates, user identifiers will become bigger t
-+
2^31 - 1and 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.
After one of the upcoming Bot API updates, some user identifiers will become bigger than2^31 - 1and 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.
-
November 4, 2020
+November 4, 2020
Introducing Bot API 5.0
Run Your Own Bot API Server
-
-
Working with Groups
-
-
Live Locations
June 4, 2020
+June 4, 2020
Bot API 4.9
April 24, 2020
+April 24, 2020
Bot API 4.8
March 30, 2020
+March 30, 2020
Bot API 4.7
-
-
January 23, 2020
+January 23, 2020
Bot API 4.6
December 31, 2019
+December 31, 2019
Bot API 4.5
July 29, 2019
+July 29, 2019
Bot API 4.4
May 31, 2019
+May 31, 2019
Bot API 4.3
- 
+
+
Also in this update:
April 14, 2019
+April 14, 2019
Bot API 4.2
August 27, 2018
+August 27, 2018
Bot API 4.1
July 26, 2018
+July 26, 2018
Bot API 4.0.
February 13, 2018
+February 13, 2018
Bot API 3.6.
November 17, 2017
+November 17, 2017
Bot API 3.5.
October 11, 2017
+October 11, 2017
Bot API 3.4.
August 23, 2017
+August 23, 2017
Bot API 3.3.
July 21, 2017
+July 21, 2017
Bot API 3.2. Teach your bot to handle stickers and sticker sets.
June 30, 2017
+June 30, 2017
Bot API 3.1. Build your own robotic police force for supergoups with these new methods for admin bots:
May 18, 2017
+May 18, 2017
Introducing Bot API 3.0.
NEW Payment Platform
-See Introduction to Bot Payments for a brief overview. If you're not a developer, you may like this user-friendly blog post better.
+See Introduction to Bot Payments for a brief overview. If you're not a developer, you may like this user-friendly blog post better.
NEW Multilingual Bots
-
-
More power to admin bots
@@ -472,44 +465,29 @@ After one of the upcoming Bot API updates, some user identifiers will become bigDecember 4, 2016
+December 4, 2016
Introducing Bot API 2.3.1, a nifty little update that will give you more control over how your bot gets its updates.
-
-
November 21, 2016
+November 21, 2016
Bot API 2.3
-
-
October 3, 2016
-Bot API 2.2. Introducing a new Gaming Platform! See this introduction for a brief overview. -If you're not a developer, you may like this user-friendly blog post better.
+October 3, 2016
+Bot API 2.2. Introducing a new Gaming Platform! See this introduction for a brief overview.
If you're not a developer, you may like this user-friendly blog post better.
May 25, 2016
+May 25, 2016
May 22, 2016
+May 22, 2016
-
-
May 12, 2016
+May 12, 2016
May 6, 2016
+May 6, 2016
April 9, 2016
+April 9, 2016
Introducing Bot API 2.0. Check out this page for a review of this major update.
February 20, 2016
+February 20, 2016
January 20, 2016
+January 20, 2016
-
-
January 14, 2016
+January 14, 2016
January 4, 2016
+January 4, 2016
November, 2015
+November, 2015
-
-
October 8, 2015
+October 8, 2015
September 18, 2015
+September 18, 2015
-September 7, 2015
+September 7, 2015
-
-
August 29, 2015
+August 29, 2015
August 15, 2015
+August 15, 2015
July 2015
+July 2015
June 24, 2015
+June 24, 2015
The bot platform was officially launched.
-