Telegram Bot API · error code

Telegram error 400: Bad Request: member list is inaccessible

ConfigurationHTTP 400400 Bad Request: identifiers, content and rights

Last verified against Telegram Bot API reference

What Telegram returns
Bad Request: member list is inaccessible

What error 400 means

The bot asked for information about channel members that it is not allowed to see. In TDLib, looking up a participant of a broadcast channel when the current account is not an administrator there returns this sentence. From the Bot API side the usual triggers are getChatMember and getChatAdministrators against a channel where the bot is only a subscriber or is not present at all.

The reference for getChatMember sets the expectation: the method is only guaranteed to work for other users if the bot is an administrator in the chat. In channels that guarantee is effectively a requirement, because subscriber lists are private.

This shows up most in subscription gates, where a bot checks whether a user has joined a channel before unlocking content. The check works in a test channel where the bot is an admin, then fails in production because the bot was added as a plain member or never added. The user ID and channel ID are fine.

What it looks like

{"ok":false,"error_code":400,"description":"Bad Request: member list is inaccessible"}

Why it happens

  • The bot is not an administrator of the channel it is querying.
  • A subscription-check bot was never added to the target channel.
  • Admin rights were removed from the bot after setup.

How to fix Telegram error 400

  1. 1Add the bot to the channel as an administrator; no special right is needed beyond admin status for member lookups.
  2. 2Re-run getChatMember(channel_id, user_id) and confirm a status is returned.
  3. 3Catch this error in subscription checks and show the operator a setup message instead of denying users.

How to stop it recurring

For any feature that verifies channel membership, check the bot's own admin status at configuration time and refuse to enable the gate until it passes. Fail open or closed deliberately when the check errors, and log which channel caused it so misconfigured channels are easy to find.

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 bot asked for information about channel members that it is not allowed to see. In TDLib, looking up a participant of a broadcast channel when the current account is not an administrator there returns this sentence. From the Bot API side the usual triggers are getChatMember and getChatAdministrators against a channel where the bot is only a subscriber or is not present at all.

How do I fix Telegram error 400?

1. Add the bot to the channel as an administrator; no special right is needed beyond admin status for member lookups. 2. Re-run getChatMember(channel_id, user_id) and confirm a status is returned. 3. Catch this error in subscription checks and show the operator a setup message instead of denying users.

Stop debugging Telegram by hand

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