Full info about a channel, supergroup or gigagroup.
When updating the local peer database », all fields from the newly received constructor take priority over the old constructor cached locally (including by removing fields that aren't set in the new constructor).
channelFull#2d895c74 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_view_stats:flags.12?true can_set_location:flags.16?true has_scheduled:flags.19?true id:int about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?int migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?int location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int pts:int = ChatFull;| Name | Type | Description |
|---|---|---|
| flags | # | Flags, see TL conditional fields |
| can_view_participants | flags.3?true | Can we view the participant list? |
| can_set_username | flags.6?true | Can we set the channel's username? |
| can_set_stickers | flags.7?true | Can we associate a stickerpack to the supergroup? |
| hidden_prehistory | flags.10?true | Is the history before we joined hidden to us? |
| can_set_location | flags.16?true | Can we set the geolocation of this group (for geogroups) |
| has_scheduled | flags.19?true | Whether scheduled messages are available |
| can_view_stats | flags.20?true | Can the user view channel/supergroup statistics |
| blocked | flags.22?true | Whether any anonymous admin of this supergroup was blocked: if set, you won't receive messages from anonymous group admins in discussion replies via @replies |
| flags2 | # | Flags, see TL conditional fields |
| can_delete_channel | flags2.0?true | Can we delete this channel? |
| antispam | flags2.1?true | Whether native antispam functionality is enabled in this supergroup. |
| participants_hidden | flags2.2?true | Whether the participant list is hidden. |
| translations_disabled | flags2.3?true | Whether the real-time chat translation popup should be hidden. |
| stories_pinned_available | flags2.5?true | Whether this user has some pinned stories. |
| view_forum_as_messages | flags2.6?true | Users may also choose to display messages from all topics of a forum as if they were sent to a normal group, using a "View as messages" setting in the local client. This setting only affects the current account, and is synced to other logged in sessions using the channels.toggleViewForumAsMessages method; invoking this method will update the value of this flag. |
| restricted_sponsored | flags2.11?true | Whether ads on this channel were disabled as specified here » (this flag is only visible to the owner of the channel). |
| can_view_revenue | flags2.12?true | If set, this user can view ad revenue statistics » for this channel. |
| paid_media_allowed | flags2.14?true | Whether the current user can send or forward paid media » to this channel. |
| can_view_stars_revenue | flags2.15?true | If set, this user can view Telegram Star revenue statistics » for this channel. |
| id | long | ID of the channel |
| about | string | Info about the channel |
| participants_count | flags.0?int | Number of participants of the channel |
| admins_count | flags.1?int | Number of channel admins |
| kicked_count | flags.2?int | Number of users kicked from the channel |
| banned_count | flags.2?int | Number of users banned from the channel |
| online_count | flags.13?int | Number of users currently online |
| read_inbox_max_id | int | Position up to which all incoming messages are read. |
| read_outbox_max_id | int | Position up to which all outgoing messages are read. |
| unread_count | int | Count of unread messages |
| chat_photo | Photo | Channel picture |
| notify_settings | PeerNotifySettings | Notification settings |
| exported_invite | flags.23?ExportedChatInvite | Invite link |
| bot_info | Vector<BotInfo> | Info about bots in the channel/supergroup |
| migrated_from_chat_id | flags.4?long | The chat ID from which this group was migrated |
| migrated_from_max_id | flags.4?int | The message ID in the original chat at which this group was migrated |
| pinned_msg_id | flags.5?int | Message ID of the last pinned message |
| stickerset | flags.8?StickerSet | Associated stickerset |
| available_min_id | flags.9?int | Identifier of a maximum unavailable message in a channel due to hidden history. |
| folder_id | flags.11?int | Peer folder ID, for more info click here |
| linked_chat_id | flags.14?long | ID of the linked discussion chat for channels (and vice versa, the ID of the linked channel for discussion chats). |
| location | flags.15?ChannelLocation | Location of the geogroup |
| slowmode_seconds | flags.17?int | If specified, users in supergroups will only be able to send one message every slowmode_seconds seconds |
| slowmode_next_send_date | flags.18?int | Indicates when the user will be allowed to send another message in the supergroup (unixtime) |
| stats_dc | flags.12?int | If set, specifies the DC to use for fetching channel statistics |
| pts | int | Latest PTS for this channel |
| call | flags.21?InputGroupCall | Livestream or group call information |
| ttl_period | flags.24?int | Time-To-Live of messages in this channel or supergroup |
| pending_suggestions | flags.25?Vector<string> | A list of suggested actions for the supergroup admin, see here for more info ». |
| groupcall_default_join_as | flags.26?Peer | When using phone.getGroupCallJoinAs to get a list of peers that can be used to join a group call, this field indicates the peer that should be selected by default. |
| theme_emoticon | flags.27?string | Emoji representing a specific chat theme |
| requests_pending | flags.28?int | Pending join requests » |
| recent_requesters | flags.28?Vector<long> | IDs of users who requested to join recently |
| default_send_as | flags.29?Peer | Default peer used for sending messages to this channel |
| available_reactions | flags.30?ChatReactions | Allowed message reactions » |
| reactions_limit | flags2.13?int | This flag may be used to impose a custom limit of unique reactions (i.e. a customizable version of appConfig.reactions_uniq_max). |
| stories | flags2.4?PeerStories | Channel stories |
| wallpaper | flags2.7?WallPaper | Wallpaper |
| boosts_applied | flags2.8?int | The number of boosts the current user has applied to the current supergroup. |
| boosts_unrestrict | flags2.9?int | The number of boosts this supergroup requires to bypass slowmode and other restrictions, see here » for more info. |
| emojiset | flags2.10?StickerSet | Custom emoji stickerset associated to the current supergroup, set using channels.setEmojiStickers after reaching the appropriate boost level, see here » for more info. |
Associate a stickerset to the supergroup
Telegram offers detailed channel statistics for channels and supergroups.
Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.
Admins of supergroups with a certain number of members can choose to unleash the full proactive power of Telegram's own antispam algorithms – turning on the new Aggressive mode for the automated spam filters.
Telegram allows translating chat messages: Telegram Premium users may even enable real-time chat translation.
Telegram users and channels can easily post and view stories through the API.
Telegram allows creating forums with multiple distinct topics.
Users may also choose to display messages from all topics of a forum as if they were sent to a normal group, using a "View as messages" setting in the local client: this setting only affects the current account, and is synced to other logged in sessions using this method.
Invoking this method will update the value of the view_forum_as_messages flag of channelFull or dialog and emit an updateChannelViewForumAsMessages.
Telegram Premium users can grant their favorite channels and supergroups additional features like the ability to post stories by giving them boosts.
Telegram has one of the most generous reward systems in the history of social media. Telegram channel owners can now receive 50% of the revenue from ads displayed in their channels. This page describes the methods used to withdraw channel ad revenue, as well as view detailed revenue stats.
Content creators can accept Stars by publishing paid photos or videos on their channels. Subscribers will be allowed to view such posts only after paying the author to unlock them.
Telegram Stars are virtual items that allow users to purchase digital goods and services from bots and mini apps inside the Telegram ecosystem, send gifts to content creators on the Telegram platform, and more.
How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.
How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
Telegram allows pinning multiple messages on top of a specific chat.
Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.
How to subscribe to updates and handle them properly.
The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.
Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
Chats and channels may have a public username or a private invite link: private invite links may be further enhanced with per-user join requests.
Telegram allows users to react on any message using specific emojis, triggering cute lottie animations.
Telegram apps support generating, sharing and synchronizing chat backgrounds.
Telegram allows including animated and static custom emojis inside of messages.
Set a custom emoji stickerset for supergroups. Only usable after reaching at least the boost level » specified in the group_emoji_stickers_level_min » config parameter.
Many constructors in the API need to be stored in a local database upon reception and should only ever be updated reactively (passively) when received via updates or by other means (as specified in the documentation), to avoid overloading the server by continuously requesting changes for the same unchanged information.