Sign in with TelegramTelegram Bot Token Checker
Is this bot token still valid?
Your token stays on this device.
The check is a request from your browser straight to api.telegram.org. It does not pass through MemberPilot, and it is not stored, logged or sent to analytics.
Lost the token? Message @BotFather, send /mybots, pick the bot, then API Token.
Paste a token and the result appears here: whether Telegram still accepts it, and which bot it belongs to.
Running a bot that gates access to a paid channel? See how MemberPilot handles paid access.
What the check actually does
getMe is the Bot API’s cheapest call: it takes no arguments and returns the bot behind the token. That makes it the correct health check, because it separates “my credential is wrong” from every other possible bug in one request.
A 401 Unauthorized means Telegram rejected the token before it looked at the request at all. Nothing else in your code is implicated, and no amount of changing the chat ID or the message will help.
Where the token goes
Telegram serves CORS headers on api.telegram.org, which means a browser can call the Bot API directly. This page takes that route deliberately: there is no server-side proxy, so there is no request log on our side that could ever contain your token.
The token is held in a React state value for the life of the tab and nothing else. It is not written to localStorage, not put in the URL, and not included in any analytics event — the only thing recorded is whether a check returned valid or invalid.
Rotate anything that has leaked
When the token is fine and things still break
A valid token narrows the problem to the request. The usual next suspects are the chat — a bot cannot message a chat it is not in, and supergroup IDs start with -100 — or the message itself. The chat ID finder reads the IDs your bot can actually see, using the same browser-direct approach.
If Telegram returned something more specific, the Bot API error decoder will translate it into likely causes.
Common questions
How do I check if a Telegram bot token is valid?
Call getMe with the token. If Telegram answers with the bot's ID, name and username, the token works. If it answers 401 Unauthorized, the token is wrong or has been revoked. That is exactly what this page does, from your browser.
Is it safe to paste my bot token here?
The request goes from your browser directly to api.telegram.org — the token is never sent to a MemberPilot server, never written to a log, never stored in this browser, and never included in an analytics event. You can confirm it in your network inspector: the only request carrying the token goes to Telegram. That said, a token is a full credential, so treat any token that has been pasted anywhere as worth rotating.
Why does a token that used to work now return 401?
Tokens are invalidated the moment a new one is issued. /revoke and /token in BotFather both do that, and so does deleting and recreating the bot. If a deployment broke after someone regenerated a token, every environment holding the old one needs updating.
What does 'can read all group messages' mean?
It reflects the bot's privacy mode. With privacy mode on — the default — a bot in a group only receives commands addressed to it, replies to its own messages, and service events. Turning it off in BotFather lets the bot see every message in groups it joins, which is a much larger permission than it sounds.
Where do I find my bot token?
Message @BotFather in Telegram, send /mybots, choose the bot, then API Token. BotFather is the only legitimate source for a token — no third party can issue or recover one for you.
Sources
Everything this tool asserts about Telegram comes from Telegram’s own documentation.