Sending messages
The Channels API supports many of the features of Telegram; however, due to the omni-channel nature of the API, there may be some differences between the Channels API message and the native Telegram API.To send a Telegram message, you must have an active Telegram channel and perform an HTTP request to the following endpoint with a valid access key.
Send a message
Send a message to a channel
The ID of the workspace
The ID for a channel
If set to true, the frequency capping settings of the platform will be used
to either allow or reject the message to a contact. Can only be set to true
if the message is sent to a contact and .meta.extraInformation.useCase
is marketing
.
If set to true and message is a test/campaign message, web tracking parameters will be appended to the links in the message.
If set to true, quiet hours settings will be ignored and the message will be sent as soon as possible.
Tags to associate with the message. Tags are converted to lower case and tags that do not exist are automatically created. You can view your created tags in the UI. You can specify up to 10 tags per message.
SMS link shortening options. When using templates, please refer to
the template level shortLinks
instead.
Scheduled time to send message at. Must be formated as RFC3339 timestamp. When
set, the message status will be scheduled
until it's sent. Messages scheduled
for a time in the past or within 10 minutes of the request may be sent
immediately. Messages scheduled farther than 35 days will be rejected.
Validity determines for how many seconds a message is valid. If none is provided, the channel message type will be used to determine it. A promotional, conversational or transactional channel message is valid for 36 hours (129600 seconds). A message sent from a 2FA channel is valid for 10 minutes (600 seconds).
Message was accepted for processing
This field is used to store additional information related to the message status.
Tags to associate with the message. Tags are converted to lower case and tags that do not exist are automatically created. You can view your created tags in the UI. You can specify up to 10 tags per message.
SMS link shortening options. When using templates, please refer to
the template level shortLinks
instead.
Scheduled time to send message at. Must be formated as RFC3339 timestamp. When
set, the message status will be scheduled
until it's sent. Messages scheduled
for a time in the past or within 10 minutes of the request may be sent
immediately. Messages scheduled farther than 35 days will be rejected.
When sending outbound messages as well as setting the receiver information you must set message body field in all cases
Body
You can send messages to users who have interacted with your Telegram bot by either starting a conversation or responding to your messages. Telegram bots can also send messages in one-on-one chats, group chats, and channels where the bot has been added. However, users must initiate the interaction by messaging your bot, as bots cannot send unsolicited messages to users who have not engaged with them first.
The Channels API supports many of the features of the Telegram API. However, due to the omni-channel nature of the API, there may be some differences between the Channels API message formats and the native Telegram API. Here is an overview of Telegram message types and how they align with Channels API message types:
Telegram API type | Channels API |
---|---|
text | |
photo | |
audio / video | |
document | |
voice | |
location | |
venue | |
sticker | - |
contact | - |
poll | - |
dice | - |
game | - |
animation | |
video note |
Outbound messages
Markdown support
By default, all text and media messages sent through our platform are treated as plain text. However, we offer support for MarkdownV1 and MarkdownV2 formatting, which can be applied by specifying the parseMode option within message metadata.
MarkdownV1 enables basic formatting, such as bold, italic, and hyperlinks.
MarkdownV2 allows more complex formatting, with additional support for features like nested styles and stricter rules for escaping special characters (e.g.,
!
,?
,*
).
Message example using MarkdownV1 formatting
Message example using MarkdownV2 formatting
Text
Text message
Text message with reply buttons
Text message with postback actions
Text message with location request
Image
Single image message
Single image message with text
Multiple image message
Single image message with postback actions
Single image message with label and reply actions
Single image message with location request
GIF
Gif message
File
Single file message
Multiple files message
Location
Last updated