diff --git a/data/web/corefork.telegram.org/api/giveaways.html b/data/web/corefork.telegram.org/api/giveaways.html index 9d5ad7a052..8b735e5626 100644 --- a/data/web/corefork.telegram.org/api/giveaways.html +++ b/data/web/corefork.telegram.org/api/giveaways.html @@ -88,9 +88,9 @@
option.users
subscribers to the channel specified in purpose.boost_peer
(only new subscribers starting from the giveaway creation date if the purpose.only_new_subscribers
field is set).additional_peers
.countries_iso2
.until_date
; at that date, Telegram will randomly choose option.users
subscribers according to the conditions specified above, and send them a Telegram Premium giftcode as a messageActionGiftCode constructor, that should be used client-side to generate a giftcode link .until_date
, and it must be at most giveaway_period_max seconds in the future; at that date, Telegram will randomly choose option.users
subscribers according to the conditions specified above, and send them a Telegram Premium giftcode as a messageActionGiftCode constructor, that should be used client-side to generate a giftcode link .boost_peer
will receive giveaway_boosts_per_premium boosts from each user, that cannot be reassigned to another channel for the duration of the gifted subscription. purpose.users
) of the channel specified in purpose.boost_peer
, which will receive giveaway_boosts_per_premium boosts from each user, that cannot be reassigned to another channel for the duration of the gifted subscription. purpose.users
, max giveaway_add_peers_max users) of the channel specified in purpose.boost_peer
, which will receive giveaway_boosts_per_premium boosts from each user, that cannot be reassigned to another channel for the duration of the gifted subscription. Then, follow the invoice payment flow as described in the payments documentation ยป.
Two alternative payment flows are also available, offering more affordable pricing: