Telegram bot token checker and chat ID finder

A bot token and a chat ID are the two values every Telegram integration asks for: the token says which bot is speaking, the chat ID says where. This page checks the first and finds the second, by asking Telegram itself — from your browser, with nothing in between.

Chat ID without a token

The box at the top answers the most common question — the ID of a channel or a group — with no bot of your own. For a public chat, paste its @username or t.me link: AdminHub’s server asks Telegram with getChat, the method the Bot API documents for “the username of the target supergroup or channel”, and shows the ID together with the chat’s title, so you can see it is the right one. For a private channel or supergroup, paste a link to any of its posts: a t.me/c/ link carries the chat’s internal number, and the Bot API ID is built from it right in your browser — minus the sum of 1,000,000,000,000 and that number.

Some things the page will not look up. A username that belongs to a person or a bot is answered without an ID: turning someone’s public username into their permanent ID is not a page’s business, and the bot below does it only when you pick the person yourself. An invite link (t.me/+…) carries no ID at all. For all of these, @getid_adminhub_bot reads your own chat list through Telegram’s chat picker. Usernames you look up are not kept beyond a short cache.

What a bot token is

A bot token is the key to one bot. @BotFather hands it out when you create a bot with /newbot, and it looks like 110201543:AAHdqTcvCH1vGWJxfSeofSAs0K5PALDsaw — digits, a colon, then a long run of letters, digits, dashes and underscores. Every request to the Bot API carries it in the address, behind the word bot: https://api.telegram.org/bot<token>/getMe. Telegram’s documentation is plain about what follows from that: the token authenticates the bot, not your account, anyone who has it can control the bot, and it should be treated like a password. It can be revoked at any time in @BotFather; if it leaked or got lost, the /token command there generates a new one, and the @BotFather Mini App does the same with buttons.

The first step on this page is getMe, the method the Bot API keeps for exactly this — testing a token. When the token works, Telegram answers with the bot it belongs to: its name, its username, its ID, and two settings worth knowing before you go further — whether the bot can be added to groups at all, and whether privacy mode is on. When the token is mistyped or has been replaced, Telegram refuses it, and the page says so in plain words.

Where chat IDs come from

The Bot API has no method that lists a bot’s chats. A bot learns the ID of a chat only when something from that chat reaches it as an update — a message, a post, the bot being added or removed — and getUpdates is the method that hands those updates out. Telegram keeps them for 24 hours, so the chat you need has to have done something recently. Which something depends on the chat:

To get the ID of	Do this	It shows up as
Yourself	Send /start to the bot	A private chat, positive number
A group	Add the bot to the group	A group or supergroup, negative number
A channel	Make the bot an admin, or forward a post from the channel to the bot	A channel, starting with -100
Another person	Forward one of their messages to the bot	A private chat, unless their privacy settings hide them

Adding the bot to a group is enough on its own: the bot is told about its own membership, and Telegram’s privacy-mode rules let every bot see service messages and the messages of channels it belongs to whatever the setting. What privacy mode does hide is ordinary chatter in groups — with it on, a bot gets commands meant for it, replies to its own messages and service messages, so a plain “hello” in a group may never arrive. A command addressed to the bot by name, such as /start@your_bot_name, always does. Forwarding works for channels the bot is not in, because a forwarded post carries the channel it came from; a person who restricts forwarding of their messages arrives as an unknown sender, with no ID to show.

No bot of your own yet, or the chat is one your bot is not in? @getid_adminhub_bot answers with the ID of any person, bot, group or channel you pick from your own chat list, with Telegram’s chat picker — no token, no forwarding, private channels included. It joins none of the chats you pick and does not keep their IDs, and since a chat has the same ID for every bot, the number it gives works for your bot too.

What the numbers mean

Chat IDs are not arbitrary. Telegram’s reference for Bot API dialog IDs puts people, groups and channels on one number line so that the sign and the size of a number say what kind of chat it is: a person’s ID is positive and is also the ID of their private chat with any bot; a basic group’s ID is its internal ID with a minus sign; a supergroup’s or channel’s ID is minus the sum of 1,000,000,000,000 and its internal ID. With internal IDs of today’s length, that last rule is why channel IDs read as -100 followed by more digits — and why the link generator drops exactly that -100 when it builds a t.me/c/ link to a post in a private channel. Copy the full number with its minus sign: that is what chat_id expects. The same reference notes that an ID can be longer than 32 bits but never more than 52, so a 64-bit integer stores it safely.

A chat can also change its ID once. When a basic group is upgraded to a supergroup, the group gets a new, -100 ID, and the old one stops being the right address: Telegram answers a request to it with an error that names the new ID. If the bot saw the moment of the upgrade, this page shows the new ID next to the old one.

When the updates cannot be read

There are two ways for a bot to receive updates, and Telegram’s documentation calls them mutually exclusive: getUpdates, which this page uses, or a webhook, where Telegram posts every update to a server. If the bot has a webhook, getUpdates is refused, and this page says so rather than removing the webhook — deleting it would cut your server off from its own bot. Two ways around it: read chat.id in the updates your server already receives, or add a second, spare bot to the same chat and check its token here, since a chat has the same ID for every bot.

A bot that is already running with getUpdates — a script or a framework polling for updates — takes each update the moment it arrives and confirms it, so nothing is left for this page to read, and the list stays empty however often you check. Stop the bot for a minute, do the step that makes the chat appear, check here, then start the bot again: the updates the page saw are still waiting for it, because this page never takes updates out of the bot’s queue. Stopping it first matters for one more reason. When two getUpdates requests for one bot overlap, Telegram can answer one of them with a Conflict error, and some bot frameworks stop polling when they get one; if the error lands here instead, the page says so.

What the page sends, and to whom

The token half of the page calls two methods, getMe and getUpdates, and both only read. It calls getUpdates with no parameters at all, on purpose: an offset would confirm updates, which takes them out of the queue your bot reads, and a list of allowed updates would be saved by Telegram as the bot’s own setting. It never sets or deletes a webhook and never sends a message. The requests go from your browser to api.telegram.org and nowhere else — the Network tab of your browser’s developer tools shows them — so AdminHub’s server never receives the token. The page keeps the token only in the open tab, never in browser storage, and the field and the results are excluded from the site’s analytics and session recordings. If you would rather do it by hand, open https://api.telegram.org/bot<token>/getUpdates in a browser with your token in place of <token>: it is the same request, answered as raw JSON, with each chat’s ID under “chat” and “id”. The username lookup at the top is the one part that goes through AdminHub’s server — the username, never a token.

If the token and the chat ID are for an AI agent that should post to your channel, there is a way to skip handing the agent a token at all: AdminHub’s MCP server connects Claude, ChatGPT or Cursor to the channel, and the posts go out through your own bot.

---

Sources, checked October 2026: Telegram Bot API — Authorizing your bot for the token format and the request address, getMe, getUpdates for the 100-update page, offset confirmation and the stored allowed_updates setting, Getting updates for the 24-hour retention and the two mutually exclusive ways, Update and ChatMemberUpdated for the bot’s own membership changes, MessageOrigin for forwarded messages, ResponseParameters for migrate_to_chat_id; Bot features for privacy mode and for creating a bot and generating a new token in @BotFather; Bot API dialog IDs for the ID ranges of people, groups, supergroups and channels; Bot tutorial for revoking a token and treating it like a password; Bots FAQ for getUpdates not working while a webhook is set.