Telegram Chat ID Finder

Almost every Telegram automation task — a deploy notifier, an alerting bot, a script that DMs you when a job finishes — needs one number: the chat ID of the conversation you want to post into. The frustration is that the Telegram app never shows it. There is no "copy chat ID" option in a chat's menu, no field in settings, nothing in a group's info panel. The ID exists only inside the Bot API, and the only way to see it is to make the API hand you an update that contains it. That is exactly what this tool does: it asks Telegram for the next message your bot receives and reads the chat.id out of the response.

A bot is a headless account created through @BotFather, Telegram's bot-management bot. When you create one, BotFather issues a token that looks like 123456789:AAExampleTokenCharacters. The number before the colon is the bot's own user ID; the part after it is the secret. That token is the bot — anyone who has it can send messages, read updates, and change the bot's settings — which is why this tool talks to Telegram straight from your browser and never routes the token through a server.

Telegram delivers a bot's incoming messages in exactly one of two ways, and they are mutually exclusive. With a webhook, you register a public HTTPS URL and Telegram pushes each update to it as a POST the moment it happens — the model production bots use. With long polling (getUpdates), your code repeatedly asks Telegram "anything new?" and Telegram holds the request open until a message arrives or a timeout passes. Polling needs no public server, no open firewall port, and no TLS certificate, which makes it perfect for a browser tool and for local development.

This tool polls. It cannot also use a webhook, and neither can your bot use both at once — that is a hard rule enforced by Telegram, not a limitation here. So if a bot already has a webhook set (which every bot that has ever run in production does), getUpdates replies with 409 Conflict: can't use getUpdates method while webhook is activeand no message will ever reach this page. That single error is behind most "it just says listening forever" reports. When it happens, the tool detects the 409 and offers to call deleteWebhook for you so polling can take over. Be aware of the trade-off: if that bot is live in production, its server will simply re-register the webhook on its next update call, so plan to re-point it once you have the ID.

Everything here happens in your browser. Before listening, the tool calls getMeto confirm the token is valid and to show you the bot's username, so a mistyped or wrong token fails immediately instead of leaving you waiting on a bot that will never answer. It then calls getUpdates with offset=-1 to skip the backlog, so it only reacts to a message you send from that point on, and it advances the offset past every update it reads so no message is processed twice. When a group is involved it scans the whole batch of updates — adding a bot to a group emits several at once — rather than only the last one, which is why it reliably catches group IDs.

Security note: a bot token is a full credential. Requests here go directly from your device to api.telegram.org over HTTPS and are never proxied or logged by us, but the safest practice is still to use a dedicated test bot for ID lookups, or to revoke and reissue the token in BotFather once you have collected the IDs you need.