Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telegram BotAPI Update July 26 #1165

code1mountain opened this Issue Jul 26, 2018 · 0 comments


None yet
1 participant
Copy link

commented Jul 26, 2018

The Telegram Bot API got a new update. Changelog is here:

New Features:

  1. Added support for Telegram Passport. See the official announcement on the blog and the manual for details.

  2. Added support for editing the media content of messages: added the method editMessageMedia and new types inputMediaAnimation, [inputMediaAudio]/bots/api(#inputmediaaudio), and inputMediaDocument.

  3. Added the field thumb to the Audio object to contain the thumbnail of the album cover to which the music file belongs.

  4. Added support for attaching custom thumbnails to uploaded files. For animations, audios, videos and video notes, which are less than 10 MB in size, thumbnails are generated automatically.

  5. tg:// URLs now can be used in inline keyboard url buttons and text_link message entities. (No changes needed?)

  6. Added the method sendAnimation, which can be used instead of sendDocument to send animations, specifying their duration, width and height. (PR #1172 )

  7. Added the field animation to the Message object. For backward compatibility, when this field is set, the document field will be also set. (PR #1172 )

  8. Added two new MessageEntity types: cashtag and phone_number.

  9. 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. (PR #1170 )

  10. You can now create inline mentions of users, who have pressed your bot's callback buttons. (No changes needed?)

  11. You can now use the Retry-After response header to configure the delay after which the Bot API will retry the request after an unsuccessful response from a webhook.

  12. If a webhook returns the HTTP error 410 Gone for all requests for more than 23 hours successively, it can be automatically removed.

  13. Added vCard support when sharing contacts: added the field vcard to the objects Contact, InlineQueryResultContact, InputContactMessageContent and the method sendContact. (PR #1169 )

This issue can be used as reference for the pull requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.