Webhook manager
setWebhook with secret token, allowed_updates, max_connections, fixed IP and self-signed certificate. Delete the webhook or drop pending updates safely.
Free · Open source · Bot API 10.3
Telegram Bot Manager: webhooks, commands and profile online
Set, check and delete your bot's webhook, edit commands, name, description, avatar, menu button and default admin rights — without writing code or running scripts.
- Works right in the browser — no install, no backend
- Supports the latest Telegram Bot API 10.3
- Shows webhook errors with hints on how to fix them
Webhook status
Danger zone
Bot profile
Name and descriptions can be set separately for every user language. “All languages” is the fallback.
Bot commands
Commands shown in the Menu button and when the user types “/”. Different lists can be set for each scope and language.
Default administrator rights
Rights suggested to users when they add the bot as an administrator. Users can still change them before confirming.
Developer tools
Raw API responses
Latest result of every get* method called in this session.
Request log
Last 100 requests. The bot token is never shown; secret tokens are masked.
Everything BotFather can't do in one place
getWebhookInfo checker
Pending updates, last delivery error and sync errors in your local time — with hints for SSL, DNS, timeouts and HTTP errors.
Commands editor
Edit setMyCommands as plain text with validation, per scope (private chats, groups, admins, a single chat) and per language.
Profile & avatar
Bot name, short description and description in any language. Upload a photo or video avatar or remove it.
Menu button
Switch the menu button between commands and your Mini App (Web App), globally or for a single chat.
Admin rights
Default administrator rights for groups and channels, including the newest rights from Bot API 10.3.
Developer tools
Raw JSON responses, request log and a ready-to-copy curl command for every action.
5 languages, dark mode
English, Русский, Español, Português and 简体中文. Light and dark themes, works on mobile.
How it works
- Paste the bot tokenCopy the token from @BotFather and press Connect.
- Check the statusSee the webhook, pending updates, errors and bot capabilities at a glance.
- Change settingsEdit and save — every action calls the official Bot API method directly.
Your token stays with you
- Static page hosted on GitHub Pages: there is no server that could store or log your token.
- Requests go from your browser straight to
api.telegram.org(or to the API server you choose). - The token is kept only in this browser tab unless you tick “Remember on this device”. “Disconnect” removes it.
- Strict Content Security Policy, no analytics, no third-party scripts. The source code is open — check it or host your own copy.
Guides
Set a webhookSet a Telegram bot webhook in a few clicks: HTTPS URL, secret token, allowed_updates, max_connections and self-signed certificate. With curl examples.
Check a webhook (getWebhookInfo)Check your Telegram bot webhook online: URL, pending updates, last error message and what it means. Fix SSL, DNS, timeout and 4xx/5xx webhook errors.
Delete a webhookDelete a Telegram bot webhook online (deleteWebhook), drop pending updates and fix “409 Conflict: can't use getUpdates method while webhook is active”.
Bot commands editorEdit Telegram bot commands online: setMyCommands per scope and language, deleteMyCommands, limits and format. Free, no code needed.
FAQ
Is it safe to enter my bot token here?
The page is fully static and has no backend. The token is used only in your browser to call the Telegram Bot API and is never sent anywhere else. You can audit the open-source code or run your own copy. If you think a token has leaked, revoke it in @BotFather → /revoke.
How do I check my Telegram bot's webhook?
Connect the bot and open the Webhook tab. It calls getWebhookInfo and shows the URL, the number of pending updates, the last delivery error with its time and a hint on how to fix it.
How do I delete a webhook and switch to getUpdates?
Open Webhook → Danger zone → Delete webhook. Optionally drop pending updates. After that the bot can receive updates with getUpdates (long polling) again — otherwise Telegram answers “409 Conflict: can't use getUpdates method while webhook is active”.
Why are there pending updates and the bot doesn't answer?
Telegram can't deliver updates to your webhook. Look at the last error: SSL problems, DNS errors, timeouts or HTTP 4xx/5xx from your server. Fix the server, then optionally drop the queued updates.
What is allowed_updates?
A list of update types the bot receives. By default you get everything except chat_member, message_reaction and message_reaction_count. To receive those, choose the types explicitly.
Can I set different commands for groups or other languages?
Yes. In the Commands tab choose a scope (all private chats, all groups, administrators, a specific chat or member) and a language. Telegram picks the most specific list for each user.
It says “Network error” when I connect. What now?
Your network, browser extension or country may block api.telegram.org. Open “Advanced: API server” and use your own proxy (a free Cloudflare Worker template is in the repository) or a local Bot API server.
Is it free? Can I host it myself?
Yes, it's free and MIT-licensed. Fork the repository and enable GitHub Pages, or run npm run build and upload the dist folder to any static hosting.