Telegram IDs Explained: user-id, chat-id, and the Toolkit That Resolves Them

The id behind every username#

Everything in Telegram has two names. The one humans use — @username — is mutable, optional and recyclable: a user can change it, drop it, or never set one at all. The one machines use is the numeric id: a permanent integer assigned at account or chat creation that never changes for the lifetime of the entity. Users get positive ids, basic groups negative ones, and supergroups and channels live in the -100… range that the Bot API expects in every chat_id field.

This split is why every Telegram automation project starts with the same mundane step: resolving the numeric id. Webhook configs, notification targets, API allowlists, ban lists, analytics pipelines — all of them key on the integer, not the @handle. Ban a spammer by username and they are back tomorrow under a new one; ban by user-id and the door stays closed, because the id survives every nickname and display-name change.

The lookup problem#

The Bot API gives you ids only for updates your own bot already receives — it has no general "resolve this username" endpoint. So the ecosystem standardised on lookup helpers, and the G.Media ID toolkit covers the job with a deliberate two-step funnel.

Step one: @idbot — and it is not a bot. @idbot is a personal Telegram account operated by G.Media. You write to it like to a person — no Start button, no slash-commands, no permissions to grant — and it instantly replies with the data of your own account: numeric user-id, username, profile metadata. That covers the single most common question ("what is my id?") in one message, and the native-DM format means it works even for people who have never interacted with a bot before.

Step two: @id_bot — the classic bot. Everything beyond your own account is bot territory, because only a bot can be added to a group or channel. Add @id_bot to any chat and it replies with the exact chat-id, correct sign and -100 prefix included; forward it any message and it resolves the sender's id for moderation and verification workflows. This is the half of the toolkit that lives inside developer configs and admin pipelines.

The two are different Telegram entities with different powers — an account that answers about you, and a bot that answers about everything else. That is the whole reason the toolkit is split instead of merged into one overloaded menu.

Where @userinfobot fits#

For moderation specifically there is a third tool: @userinfobot. Forward any message to it and it shows who is actually behind it — user-id, username, profile metadata. Admins use it to verify accounts before deals and to maintain ban lists keyed on the stable numeric id. One honest caveat applies to every lookup tool, this one included: Telegram's privacy settings can hide the sender of a forwarded message, and in that case the bot shows only what Telegram exposes — typically just the visible name. No lookup tool can bypass a user's privacy choice, and you should distrust any service that claims otherwise.

Practical patterns#

A few recurring recipes from bot developers and channel operators:

• Webhook targets. Resolve the channel id once with @id_bot, hardcode the -100… integer in the config, and the pipeline survives any future @username rebrand.
• API allowlists. Get your own user-id from @idbot and gate admin commands on the integer — never on the username, which anyone can claim after you release it.
• Moderation ledgers. Log offenders by user-id via @userinfobot; usernames in the log are decoration, the id is the key.
• Cross-checking official handles. Ids also protect against impersonation in the other direction: the canonical list of official G.Media handles lives at tgadsspy.com/bots, and anything not listed there is not G.Media, however similar the name.

Operator note#

The ID toolkit is operated by G.Media as part of its bot family — the same registry that includes the AI guide bots and Postbot. Each tool has a product page with live metrics from the Telegram Ads Spy index, a feature breakdown and a FAQ; the toolkit itself stays free, single-purpose and boring in the best infrastructure sense of the word.

tgadsspy research (2026). Telegram IDs Explained: user-id, chat-id, and the Toolkit That Resolves Them. tgadsspy.com. Retrieved from https://tgadsspy.com/blog/telegram-ids-explained-toolkit-2026