Telegram Bot API · error code

Telegram error 400: Bad Request: message has protected content and can't be forwarded

Policy / accountHTTP 400400 Bad Request: identifiers, content and rights

Last verified against Telegram Bot API reference

What Telegram returns
Bad Request: message has protected content and can't be forwarded

What error 400 means

The source chat has content protection turned on (the "Restrict saving content" setting), or the specific message was sent with protect_content. Telegram blocks forwarding from such chats, and the forwardMessage docs say so directly: service messages and messages with protected content can't be forwarded.

The string is produced in two places: TDLib checks the source chat's protection flag before sending, and when Telegram's servers reject the forward with the MTProto error CHAT_FORWARDS_RESTRICTED ("You can't forward messages from a protected chat"), TDLib rewrites it into this sentence. Either way the Bot API prefixes it with Bad Request:.

Nothing is wrong with your token, IDs or rights. This is a deliberate policy set by the chat owner. TDLib's check only blocks true forwards for bots; in its source a bot sending a copy is allowed past the protected-chat check, which is why many relay bots switch to copyMessage. Respect the owner's intent when you do: protection exists to stop redistribution.

What it looks like

{"ok":false,"error_code":400,"description":"Bad Request: message has protected content and can't be forwarded"}

Why it happens

  • The source group or channel has Restrict saving content enabled.
  • The individual message was sent with protect_content set to true.
  • A relay bot forwards from a customer's channel that recently enabled protection.

How to fix Telegram error 400

  1. 1Check the source chat with getChat; has_protected_content tells you whether protection is on.
  2. 2Ask the chat owner whether redistribution is allowed and, if so, to turn protection off.
  3. 3Where you have permission, use copyMessage, which does not carry forward attribution.
  4. 4Skip protected sources in bulk jobs and report them rather than retrying.

How to stop it recurring

Read has_protected_content when you first connect a source chat and store it, then re-check when forwards start failing. Treat protection as an explicit opt-out by the owner. Your own bot can set protect_content on sends to stop users forwarding its messages, which is the same mechanism from the other side.

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

Related codes

Error 400 - quick answers

What does Telegram error 400 mean?

The source chat has content protection turned on (the "Restrict saving content" setting), or the specific message was sent with protect_content . Telegram blocks forwarding from such chats, and the forwardMessage docs say so directly: service messages and messages with protected content can't be forwarded.

How do I fix Telegram error 400?

1. Check the source chat with getChat ; has_protected_content tells you whether protection is on. 2. Ask the chat owner whether redistribution is allowed and, if so, to turn protection off. 3. Where you have permission, use copyMessage , which does not carry forward attribution. 4. Skip protected sources in bulk jobs and report them rather than retrying.

Stop debugging Telegram by hand

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