chat

Info about a 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).

See here » for an implementation of the logic to use when updating the local user peer database.

chat#3bda1bde flags:# creator:flags.0?true kicked:flags.1?true left:flags.2?true deactivated:flags.5?true call_active:flags.23?true call_not_empty:flags.24?true id:int title:string photo:ChatPhoto participants_count:int date:int version:int migrated_to:flags.6?InputChannel admin_rights:flags.14?ChatAdminRights default_banned_rights:flags.18?ChatBannedRights = Chat;

Parameters

Name Type Description
flags # Flags, see TL conditional fields
creator flags.0?true Whether the current user is the creator of the group
left flags.2?true Whether the current user has left the group
deactivated flags.5?true Whether the group was migrated
call_active flags.23?true Whether a group call is currently active
call_not_empty flags.24?true Whether there's anyone in the group call
noforwards flags.25?true Whether this group is protected, thus does not allow forwarding messages from it
id long ID of the group, see here » for more info
title string Title
photo ChatPhoto Chat photo
participants_count int Participant count
date int Date of creation of the group
version int Used in basic groups to reorder updates and make sure that all of them were received.
migrated_to flags.6?InputChannel Means this chat was upgraded to a supergroup
admin_rights flags.14?ChatAdminRights Admin rights of the user in the group
default_banned_rights flags.18?ChatBannedRights Default banned rights of all users in the group

Type

Chat

Related pages

Channels, supergroups, gigagroups and basic groups

How to handle channels, supergroups, gigagroups, basic groups, and what's the difference between them.

Peer database

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.

Admin, banned, default rights

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.