Full info about a basic group.
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).
chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;| Name | Type | Description |
|---|---|---|
| flags | # | Flags, see TL conditional fields |
| can_set_username | flags.7?true | Can we change the username of this chat |
| has_scheduled | flags.8?true | Whether scheduled messages are available |
| translations_disabled | flags.19?true | Whether the real-time chat translation popup should be hidden. |
| id | long | ID of the chat |
| about | string | About string for this chat |
| participants | ChatParticipants | Participant list |
| chat_photo | flags.2?Photo | Chat photo |
| notify_settings | PeerNotifySettings | Notification settings |
| exported_invite | flags.13?ExportedChatInvite | Chat invite |
| bot_info | flags.3?Vector<BotInfo> | Info about bots that are in this chat |
| pinned_msg_id | flags.6?int | Message ID of the last pinned message |
| folder_id | flags.11?int | Peer folder ID, for more info click here |
| call | flags.12?InputGroupCall | Group call information |
| ttl_period | flags.14?int | Time-To-Live of messages sent by the current user to this chat |
| groupcall_default_join_as | flags.15?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.16?string | Emoji representing a specific chat theme |
| requests_pending | flags.17?int | Pending join requests » |
| recent_requesters | flags.17?Vector<long> | IDs of users who requested to join recently |
| available_reactions | flags.18?ChatReactions | Allowed message reactions » |
| reactions_limit | flags.20?int | This flag may be used to impose a custom limit of unique reactions (i.e. a customizable version of appConfig.reactions_uniq_max). |
Telegram allows scheduling messages
Telegram allows translating chat messages: Telegram Premium users may even enable real-time chat translation.
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.
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.
The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.
How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.
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.