updateChannel

Channel/supergroup (channel and/or channelFull) information was updated.

This update can only be received through getDifference or in updates/updatesCombined constructors, so it will always come bundled with the updated channel, that should be applied as usual », without re-fetching the info manually.

However, full peer information will not come bundled in updates, so the full peer cache (channelFull) must be invalidated for channel_id when receiving this update.

updateChannel#b6d45656 channel_id:int = Update;

Parameters

Name Type Description
channel_id long Channel ID

Type

Update

Related pages

channel

Channel/supergroup info

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).

The only exception to the above rule is when the min flag is set, in which case only the following fields must be applied over any locally stored version:

  • title
  • megagroup
  • color
  • photo
  • username
  • usernames
  • has_geo
  • noforwards
  • emoji_status
  • has_link
  • slow_mode_enabled
  • scam
  • fake
  • gigagroup
  • forum
  • level
  • restricted
  • restriction_reason
  • join_to_send
  • join_request
  • is_verified
  • default_banned_rights

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

channelFull

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).

Updates

Full constructor of updates

updatesCombined

Constructor for a group of updates.

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.