diff --git a/data/core.telegram.org/bots/api-changelog.html b/data/core.telegram.org/bots/api-changelog.html index da97d2c55b..f7743e51fb 100644 --- a/data/core.telegram.org/bots/api-changelog.html +++ b/data/core.telegram.org/bots/api-changelog.html @@ -51,6 +51,21 @@ To learn how to create…">

Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

+

November 5, 2021

+

Bot API 5.4

+ +
+
+

⚠️ WARNING! ⚠️
User identifiers will become bigger than 2^31 - 1 before 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

Bot API 5.3

Personalized Commands

diff --git a/data/core.telegram.org/bots/api.html b/data/core.telegram.org/bots/api.html index b52fb6dd29..571b978de8 100644 --- a/data/core.telegram.org/bots/api.html +++ b/data/core.telegram.org/bots/api.html @@ -50,11 +50,26 @@ To learn how to create…">

Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

+

November 5, 2021

+

Bot API 5.4

+ +
+
+

⚠️ WARNING! ⚠️
User identifiers will become bigger than 2^31 - 1 before 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

Bot API 5.3

Personalized Commands

-
-
-

⚠️ WARNING! ⚠️
After the next Bot API update (Bot API 5.3) there will be a one-time change of the value 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.

-
-
-
-

⚠️ WARNING! ⚠️
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.

-
-
-
-

⚠️ 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.

-
-
-

March 9, 2021

-

Bot API 5.1

-

Added two new update types

- -

Improved Invite Links

- -

Voice Chat Info

- -

And More

- -
-
-

⚠️ 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.

-
-
-

November 4, 2020

-

Introducing Bot API 5.0

-

Run Your Own Bot API Server

- -

Transfer Bot Ownership

- -

Webhooks

- -

Working with Groups

- -

Working with Files

- -

Multiple Pinned Messages

- -

File Albums

- -

Live Locations

- -

Anonymous Admins

- -

And More

- -

And Last but bot Least

-

See earlier changes »

Authorizing your bot

Each bot is given a unique authentication token when it is created. The token looks something like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11, but we'll use simply <token> in this document instead. You can learn about obtaining tokens and generating new ones in this document.

@@ -214,7 +117,7 @@ To learn how to create…">
  • application/json (except for uploading files)
  • multipart/form-data (use to upload files)
    • -

    The response contains a JSON object, which always has a Boolean field 'ok' and may have an optional String field 'description' with a human-readable description of the result. If 'ok' equals true, the request was successful and the result of the query can be found in the 'result' field. In case of an unsuccessful request, 'ok' equals false and the error is explained in the 'description'. An Integer 'error_code' field is also returned, but its contents are subject to change in the future. Some errors may also have an optional field 'parameters' of the type ResponseParameters, which can help to automatically handle the error.

    +

    The response contains a JSON object, which always has a Boolean field 'ok' and may have an optional String field 'description' with a human-readable description of the result. If 'ok' equals True, the request was successful and the result of the query can be found in the 'result' field. In case of an unsuccessful request, 'ok' equals false and the error is explained in the 'description'. An Integer 'error_code' field is also returned, but its contents are subject to change in the future. Some errors may also have an optional field 'parameters' of the type ResponseParameters, which can help to automatically handle the error.