Yes, file_ids can be treated as persistent.
When sending messages inside a particular chat, avoid sending more than one message per second. We may allow short bursts that go over this limit, but eventually you'll begin receiving 429 errors.
-If you're sending bulk notifications to multiple users, the API will not allow more than 30 messages per second or so. Consider spreading out notifications over large intervals of 8—12 hours for best results.
-Also note that your bot will not be able to send more than 20 messages per minute to the same group.
+By default, bots are able to message their users at no cost – but have limitations on the number of messages they can broadcast in a single interval:
+Unfortunately, at this moment we don't have methods for sending bulk messages, e.g. notifications. We may add something along these lines in the future.
-In order to avoid hitting our limits when sending out mass notifications, consider spreading them over longer intervals, e.g. 8-12 hours. The API will not allow bulk notifications to more than ~30 users per second, if you go over that, you'll start getting 429 errors.
-See also: How to avoid hitting limits?
+Enabling paid broadcasts in @BotFather allows a bot to broadcast up to 1000 messages per second. Each message broadcasted over the free amount of 30 per second incurs a cost of 0.1 Stars per message, paid with Telegram Stars from the bot's balance. In order to enable this feature, a bot must have at least 100,000 Stars on its balance and at least 100,000 monthly active users.
+++Bots with increased limits are only charged for messages that are broadcasted successfully.
+
If you do not wish to enable paid broadcasts, consider spreading them over longer intervals (e.g. 8-12 hours) to avoid hitting the limit. The API will not allow bulk notifications to more than ~30 users per second – if you go over that, you'll start getting 429 errors.
If you've got questions that are not answered on this page, ping us at @BotSupport in Telegram.
diff --git a/data/web/core.telegram.org/bots/faq.html b/data/web/core.telegram.org/bots/faq.html index eab5a1dfe7..5129ff978c 100644 --- a/data/web/core.telegram.org/bots/faq.html +++ b/data/web/core.telegram.org/bots/faq.html @@ -159,13 +159,18 @@ You may also find the Bot API…">
We welcome any suggestions for the Bot Platform and API.Yes, file_ids can be treated as persistent.
Broadcasting to Users
My bot is hitting limits, how do I avoid this?
-When sending messages inside a particular chat, avoid sending more than one message per second. We may allow short bursts that go over this limit, but eventually you'll begin receiving 429 errors.
-If you're sending bulk notifications to multiple users, the API will not allow more than 30 messages per second or so. Consider spreading out notifications over large intervals of 8—12 hours for best results.
-Also note that your bot will not be able to send more than 20 messages per minute to the same group.
+By default, bots are able to message their users at no cost – but have limitations on the number of messages they can broadcast in a single interval:
++
- In a single chat, avoid sending more than one message per second. We may allow short bursts that go over this limit, but eventually you'll begin receiving 429 errors.
+- In a group, bots are not be able to send more than 20 messages per minute.
+- For bulk notifications, bots are not able to broadcast more than about 30 messages per second, unless they enable paid broadcasts to increase the limit.
+How can I message all of my bot's subscribers at once?
-Unfortunately, at this moment we don't have methods for sending bulk messages, e.g. notifications. We may add something along these lines in the future.
-In order to avoid hitting our limits when sending out mass notifications, consider spreading them over longer intervals, e.g. 8-12 hours. The API will not allow bulk notifications to more than ~30 users per second, if you go over that, you'll start getting 429 errors.
-See also: How to avoid hitting limits?
+Enabling paid broadcasts in @BotFather allows a bot to broadcast up to 1000 messages per second. Each message broadcasted over the free amount of 30 per second incurs a cost of 0.1 Stars per message, paid with Telegram Stars from the bot's balance. In order to enable this feature, a bot must have at least 100,000 Stars on its balance and at least 100,000 monthly active users.
+++Bots with increased limits are only charged for messages that are broadcasted successfully.
+If you do not wish to enable paid broadcasts, consider spreading them over longer intervals (e.g. 8-12 hours) to avoid hitting the limit. The API will not allow bulk notifications to more than ~30 users per second – if you go over that, you'll start getting 429 errors.
If you've got questions that are not answered on this page, ping us at @BotSupport in Telegram.
diff --git a/data/web/corefork.telegram.org/bots/faq.html b/data/web/corefork.telegram.org/bots/faq.html index 13e7973bbb..0ac176205c 100644 --- a/data/web/corefork.telegram.org/bots/faq.html +++ b/data/web/corefork.telegram.org/bots/faq.html @@ -159,13 +159,18 @@ You may also find the Bot API…">
We welcome any suggestions for the Bot Platform and API.Yes, file_ids can be treated as persistent.
Broadcasting to Users
My bot is hitting limits, how do I avoid this?
-When sending messages inside a particular chat, avoid sending more than one message per second. We may allow short bursts that go over this limit, but eventually you'll begin receiving 429 errors.
-If you're sending bulk notifications to multiple users, the API will not allow more than 30 messages per second or so. Consider spreading out notifications over large intervals of 8—12 hours for best results.
-Also note that your bot will not be able to send more than 20 messages per minute to the same group.
+By default, bots are able to message their users at no cost – but have limitations on the number of messages they can broadcast in a single interval:
++
- In a single chat, avoid sending more than one message per second. We may allow short bursts that go over this limit, but eventually you'll begin receiving 429 errors.
+- In a group, bots are not be able to send more than 20 messages per minute.
+- For bulk notifications, bots are not able to broadcast more than about 30 messages per second, unless they enable paid broadcasts to increase the limit.
+How can I message all of my bot's subscribers at once?
-Unfortunately, at this moment we don't have methods for sending bulk messages, e.g. notifications. We may add something along these lines in the future.
-In order to avoid hitting our limits when sending out mass notifications, consider spreading them over longer intervals, e.g. 8-12 hours. The API will not allow bulk notifications to more than ~30 users per second, if you go over that, you'll start getting 429 errors.
-See also: How to avoid hitting limits?
+Enabling paid broadcasts in @BotFather allows a bot to broadcast up to 1000 messages per second. Each message broadcasted over the free amount of 30 per second incurs a cost of 0.1 Stars per message, paid with Telegram Stars from the bot's balance. In order to enable this feature, a bot must have at least 100,000 Stars on its balance and at least 100,000 monthly active users.
+++Bots with increased limits are only charged for messages that are broadcasted successfully.
+If you do not wish to enable paid broadcasts, consider spreading them over longer intervals (e.g. 8-12 hours) to avoid hitting the limit. The API will not allow bulk notifications to more than ~30 users per second – if you go over that, you'll start getting 429 errors.
If you've got questions that are not answered on this page, ping us at @BotSupport in Telegram.
We welcome any suggestions for the Bot Platform and API.