Inbox
Telegram direct messages, bot commands and inbox webhooks.
Telegram supports DMs with attachments, inline and reply keyboards, and a bot command menu. There are no comments.
Direct messages
| Feature | Supported |
|---|---|
| List conversations | |
| Fetch messages | |
| Send text messages | |
| Send attachments | (images, videos, documents) |
| Edit messages | (text and inline keyboard) |
| Inline keyboards | (buttons with callback data or URLs) |
| Reply keyboards | (one-time custom keyboards) |
| Reply to a message | (replyTo with the message id) |
| Archive and unarchive |
Attachments:
| Type | Max size |
|---|---|
| Images | 10 MB |
| Videos | 50 MB |
| Documents | 50 MB |
When a user taps an inline keyboard button, the callback data arrives on the incoming message in metadata.callbackData.
The Messages API has every endpoint.
Bot commands
Bot commands are the entries in the "/" menu users see when they chat with the bot.
Manage them with GET, PUT and DELETE /v1/accounts/{accountId}/telegram-commands (Account settings).
- Up to 100 commands.
- Each name is lowercase, at most 32 characters:
a-z,0-9,_, no leading slash. - Each description is at most 256 characters.
Webhooks
| Event | When it fires |
|---|---|
message.received | New incoming message to the bot |
message.sent | Outgoing message is sent |
message.edited | The user edits a sent message; also fires for edited_channel_post in channels where the bot is an administrator |
reaction.received | A participant adds or removes an emoji reaction. The bot must be an administrator of the chat; reactions in private chats are not delivered |
Messages are stored locally as webhooks arrive. The webhooks page has the payloads.
Telegram's Bot API exposes no deletion or read-receipt events for regular bot chats.
Delivery and read tracking exist only in the separate Telegram Business integration, which Zernio does not use.