Skip to main content
Telegram is the in-app direct channel: fast alerts, support bots, and conversations without relying on SMS or WhatsApp.

​
What is Telegram on Notifique?

It’s how you talk to customers on Telegram without building infrastructure from scratch. You connect a bot (the most common path) or, in specific cases, a personal account, and then you can:
  • Send text, media via HTTPS URL, and location (depending on mode)
  • Receive messages on the bot or account and react with automation
  • Track queue, status, and failures via API or webhooks
  • Edit or delete sent messages when Telegram allows it
Think of the bot as a support agent named @mybot: predictable, documented, and ideal for production.
Telegram Gateway (Meta SMS codes) is a different product. This documentation covers in-app Telegram messages only.

​
Bot or personal account?

Each instance is either a bot or an account. You cannot switch mode on the same line, if you change your mind, create a new one. Full comparison: Connection modes.

​
Rules every integrator should know

​
In bot mode (most common)

Telegram does not let the bot cold-DM users. In almost all cases:
  1. The user must speak first, open the bot and send /start (or tap “Start”).
  2. Only then can the bot reply and send in that chat.
  3. Use GET /v1/telegram/chats to find chatId and @username for users who already started.
This is not a Notifique limitation: it is Bot API anti-spam policy.

​
In personal account mode

You act with the account identity. Automating mass DMs or spam can violate Telegram Terms of Service. Use only when a bot does not fit, and responsibly. 2FA login may require a session string instead of QR.
Telegram webhook events start with telegram.*. On WhatsApp, it is message.*. If you use both channels, keep handlers separate.

​
How to connect

  1. Create an instance in the dashboard or API (bot with token or account with acceptUserTerms)
  2. For a bot, status is ACTIVE right away; for an account, the response already includes the QR in connection, or use generateShareableLink: true to send the link to someone else
  3. Send with instanceId, destination (chatId or @username), and content type
Step by step: Quick Start (Bot and Personal account tabs).
Each API Key belongs to one workspace. On v1 do not send x-workspace-id.

​
Comparison: what each mode can do

* Personal accounts have more freedom, but that is not permission to spam. Respect ToS and opt-in.

​
Message lifecycle

After POST, the message goes through QUEUED or SCHEDULED, then SENT or FAILED. Engagement (READ, RESPONDED, etc.) may arrive later via webhook. SENT means Telegram accepted it, not that the person read it. OTP and urgent alerts can use "options": { "priority": "high" }. Do not overuse on mass campaigns.

​
After you connect

  • Send from the dashboard or POST /v1/telegram/messages
  • List chats and inbound to build support flows
  • Set up webhooks (telegram.sent, telegram.received, …)
  • Restrict the key with instanceIds and minimal scopes

​
Next steps