Connect Telegram

Aegis sends operational alerts to a Telegram chat. In the current beta, Telegram notifications use a single-tenant, operator-owned model: one bot token and one target chat ID are configured at the infrastructure level via environment variables. There is no per-user Telegram setup and no dashboard configuration UI for this at this time.

How it works

The Aegis bot process reads two environment variables at startup:

TELEGRAM_BOT_TOKEN — the Telegram Bot API token for the operator-owned bot
TELEGRAM_CHAT_ID — the numeric chat ID (personal, group, or channel) that receives alerts

Both values must be set as a pair. If either is absent, the notification adapter starts in a no-op state and no alerts are sent.

All runtime alerts (position opened, position closed, margin warnings, errors, etc.) are sent to this single chat. See Alert Types for the full list of events.

Obtaining a bot token and chat ID

Open Telegram and search for @BotFather.
Send /newbot and follow the prompts to create a bot. Copy the token.
Add your bot to the target chat (personal chat, group, or channel).
To find the chat ID, send a message from that chat and call:
```
https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates
```
The chat.id field in the response is the value to use.

Provide both values to your Aegis infrastructure operator so they can be set as environment variables before the bot process starts.

Beta note: per-user Telegram linking

A future release will allow individual users to link their own Telegram accounts directly from the dashboard using a verification code flow. This is not available in the current beta.