Telegram Bot API · error code

Telegram error 403: Forbidden: bot is not a member of the supergroup chat

Permanent - do not retryHTTP 403403 Forbidden: blocked, kicked, not started

Last verified against Telegram Bot API reference

What Telegram returns
Forbidden: bot is not a member of the supergroup chat

What error 403 means

The bot is not currently in the supergroup it is trying to act in. It was never added, it left via leaveChat, or it was banned and later unbanned, which leaves it outside the chat rather than blocked. The Bot API server checks the bot's membership status before sending and returns this description when the bot is not a member.

The server distinguishes this from being kicked: a banned bot gets bot was kicked from the supergroup chat. "Not a member" covers the softer cases, which matters for recovery because a bot that merely left can be re-added straightforwardly.

Public and private supergroups behave slightly differently. For a public supergroup (one with a username) the server lets read-only calls through and blocks only actions that need membership, such as sending. For a private supergroup even reading is refused. So getChat might work while sendMessage fails with this error.

What it looks like

{"ok":false,"error_code":403,"description":"Forbidden: bot is not a member of the supergroup chat"}

Why it happens

  • The bot left the supergroup via leaveChat, or was unbanned after a removal but never re-added.
  • The bot was never added and the chat_id came from elsewhere, such as a user-supplied link.
  • The bot was added to a different supergroup with a similar name.
  • A test bot token is being used against chats where only the production bot was added.

How to fix Telegram error 403

  1. 1Ask an admin to add the bot to the supergroup, then retry.
  2. 2Mark the chat inactive in your database until a my_chat_member update shows the bot is a member again.
  3. 3Check which bot token is in use and confirm that bot is in the chat.
  4. 4Stop scheduled sends to the chat to avoid wasted requests.

How to stop it recurring

Track membership from my_chat_member updates (status member, administrator, left or kicked) and only send to chats marked active. When a user links a group to your service, verify the bot is in it before saving the configuration.

Official reference: Telegram Bot API reference. See all Telegram error codes or the Telegram limits and quotas.

Related codes

Error 403 - quick answers

What does Telegram error 403 mean?

The bot is not currently in the supergroup it is trying to act in. It was never added, it left via leaveChat , or it was banned and later unbanned, which leaves it outside the chat rather than blocked. The Bot API server checks the bot's membership status before sending and returns this description when the bot is not a member.

How do I fix Telegram error 403?

1. Ask an admin to add the bot to the supergroup, then retry. 2. Mark the chat inactive in your database until a my_chat_member update shows the bot is a member again. 3. Check which bot token is in use and confirm that bot is in the chat. 4. Stop scheduled sends to the chat to avoid wasted requests.

Should I retry after error 403?

No. Retrying the same request produces the same error; the condition has to be fixed first. Treat it as a permanent failure for that message and surface it, rather than looping.

Stop debugging Telegram by hand

Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.