Telegram API Setup
Telegram requires no admin configuration. Each end-user creates their own bot via @BotFather and pastes the token + chat IDs from /app/channels.
The admin page at /admin/api-integration/telegram is purely informational — it shows that no global app-level credentials exist.
Why no admin app
Unlike X or LinkedIn, Telegram doesn't issue a single global "app" that brokers many users' accounts. Instead, every Sosyabot user creates their own bot, owns it personally, and adds it to the chats they want Sosyabot to post to. The bot token is the credential — there is no separate Client ID/Secret.
What end-users do
End-users:
- Open Telegram → message @BotFather.
/newbot→ pick a display name and a unique@usernameending inbot.- BotFather returns the bot token (
123456789:ABC-DEF...). - Add the bot to every channel/group/chat they want Sosyabot to post to — bot must be member or admin depending on chat type.
/app/channels→ Connect → Telegram → paste token + chat IDs.
Connect endpoint: POST /api/v1/social/telegram/connect (validated server-side via getMe and getChatMember).
For the full user-facing flow see Connections → Telegram.
Pasting into Sosyabot admin panel
Nothing to paste. The admin page contains a static info card only.
Troubleshooting (admin perspective)
| Symptom | Cause | Fix |
|---|---|---|
| Multiple users complain they can't post to a channel | Their bots aren't admins on the target channel | Each user must add their own bot as admin to every target channel; admins cannot do this for them. |
| User Connect form rejects token | Token has whitespace or contains a typo | Paste exactly the BotFather output. |
ENV fallback
There is no TELEGRAM_* ENV block. Bot credentials are user-supplied at connect time.