Telegram Bot Connectivity
Important information about bot connectivity and troubleshooting connection issues.
How We Check Your Bot
When you enter your Telegram bot token, our system calls the official Telegram API:
https://api.telegram.org/bot<TOKEN>/getMe
- If Telegram responds successfully → your bot is connected.
- If Telegram returns an error → your bot is marked as not working.
Example API Responses
Successful Connection:

A successful response returns bot information including ID, username, and permissions.
Failed Connection:

An unauthorized error indicates the bot token is invalid or the bot has been restricted.
Why Your Bot Might Show as "Forbidden" or "Not Working"
Telegram does not provide detailed reasons for failures. Common causes include:
- Your Telegram account or bot is restricted/flagged
Telegram may limit accounts due to suspicious activity or policy violations. - Your proxy, VPN, firewall, or network is blocking Telegram
Some networks block api.telegram.org or Telegram IP ranges. - Sensitive keywords/content used in bot info or messages
Certain terms can trigger automated bot bans. - Bot token is incorrect or mis-typed
Invalid tokens return the same error as restricted accounts.
What Our Platform Can Detect
- We can detect when a bot is not responding to Telegram's API.
- We cannot detect why it's happening (Telegram does not tell us).
- We cannot appeal or reverse Telegram bans.
- We never access or read your bot's messages.
What You Can Do If Your Bot Fails to Connect
If your bot appears as offline/forbidden:
- Try messaging your bot directly in Telegram (/start test).
- Create a new bot via BotFather and reconnect it.
- Disable or switch your VPN/proxy and try again.
- Avoid flagged keywords in your bot name/description.
- If issues continue, contact Trapyfy support (insert email here)
Important Note for Onboarding
- You can continue onboarding even if your bot is not yet active.
- You can replace the bot token at any time.
- Most issues are resolved simply by creating a fresh Telegram bot.
