groupCallMessage
groupCallMessage
Section titled “groupCallMessage”No description provided by the pinned schema.
Signature
Section titled “Signature”groupCallMessage#1a8afc7e flags:# from_admin:flags.1?true id:int from_id:Peer date:int message:TextWithEntities paid_message_stars:flags.0?long = GroupCallMessage;Result type
Section titled “Result type”GroupCallMessage
Parameters
Section titled “Parameters”| Name | Type | Flag | Default | Description |
|---|---|---|---|---|
| flags | # | flag word | — | No description provided by the pinned schema. |
| from_admin | flags.1?true | flags.1 | — | No description provided by the pinned schema. |
| id | int | — | — | No description provided by the pinned schema. |
| from_id | Peer | — | — | No description provided by the pinned schema. |
| date | int | — | — | No description provided by the pinned schema. |
| message | TextWithEntities | — | — | No description provided by the pinned schema. |
| paid_message_stars | flags.0?long | flags.0 | — | No description provided by the pinned schema. |
| Parameter | Bit | Meaning |
|---|---|---|
| from_admin | 1 | Controlled by flags; present when this bit is set. |
| paid_message_stars | 0 | Controlled by flags; present when this bit is set. |
Python binding
Section titled “Python binding”from miniproto.raw.types import GroupCallMessagePublic access: miniproto.raw.types.GroupCallMessage.
Safe usage shape
Section titled “Safe usage shape”from miniproto.raw.types import GroupCallMessage
# Naming the raw constructor class is local only; it performs no I/O or network request.constructor_type = GroupCallMessageResult family
Section titled “Result family”Relationships
Section titled “Relationships”- Result family:
GroupCallMessage - Accepted by:
updateGroupCallMessage
Provenance
Section titled “Provenance”- layer: 228
- structural source:
tdlib - canonical schema: https://raw.githubusercontent.com/tdlib/td/refs/heads/master/td/generate/scheme/telegram_api.tl
- prose merge precedence: TDLib → Telegram Desktop → Core JSON
- source note: Canonical structure is the pinned TDLib telegram_api.tl; Layer 228 comes only from the matching Telegram Desktop end-of-file marker; core.telegram.org inputs enrich documentation and RPC error metadata without overriding structure.
Source-diff notes
Section titled “Source-diff notes”- tdlib_vs_core: changed_count=68; core_only_count=1; overlap_count=2302; tdlib_only_count=158
- tdlib_vs_tdesktop: changed_count=0; overlap_count=2448; tdesktop_only=null; tdlib_only=accessPointRule, ephemeral.editMessage, help.configSimple, inputPeerPhotoFileLocationLegacy, inputStickerSetThumbLegacy, invokeWithApnsSecretPrefix, invokeWithBusinessConnectionPrefix, invokeWithGooglePlayIntegrityPrefix, invokeWithReCaptchaPrefix, ipPort, ipPortSecret, updateEphemeralBotCallbackQuery