Represents a chat β a group, channel, contact, or bot conversation.
π‘ Most fields are only populated by getChat. Elsewhere you usually get justid,title, andtype.
Fields
Field | Type | Required | Description |
id | String | Yes | The chat. |
title | String | Optional | Chat title. |
name | String | Optional | Chat name, where one is set separately from the title. |
type | String | Optional | "Group", "Channel", "Contact", or "Bot". |
version | String | Optional | Version stamp of the last profile update. |
description | String | Optional | Chat description. Only in getChat. |
category | String | Optional | Chat category. Only in getChat. |
language_code | String | Optional | IETF language tag of the chat's main language. Only in getChat. |
regions | String | Optional | Allowed region. null means all regions. Only in getChat. |
member_count | Integer | Optional | Total members. Only in getChat. |
invite_link | String | Optional | Join link for the chat. Only in getChat. |
photo | Optional | Chat photo. Only in getChat. | |
tagsDefinition | Optional | Tags defined on the chat. |
Depending on the chat type, the server may include extra internal fields β scheduling, splash, and slot settings among them. They are not part of the documented contract and no SDK exposes them.
Example
json{ "chat": { "id": "74441125874452101", "title": "Hello", "type": "Channel", "version": "blake", "description": "Available", "category": "Materials", "language_code": null, "regions": null, "member_count": 3, "invite_link": "https://join.ndbx.me/join?id=SzzFPuoDUdTiF4k2iXyJFFSB4XLIcBUjVXYbfuuJfos%3D&type=Channel&pay=0", "tagsDefinition": null } }