A free, open-source web tool to manage a Telegram bot through the Bot API: set, check (getWebhookInfo) and delete webhooks, edit commands, name, description and avatar, the menu button and default admin rights. No code, no install, no backend: it runs entirely in your browser.
🇬🇧 English · 🇷🇺 Русский · the site itself is available in English, Русский, Español, Português and 简体中文.
- Webhook manager:
setWebhookwithsecret_token(built-in generator),allowed_updates,max_connections, fixedip_addressand self-signedcertificateupload. Delete the webhook or drop pending updates without losing your secret token. - getWebhookInfo checker: URL, pending updates, last delivery error and sync errors in your local time, with hints for SSL, DNS, timeout, 3xx/4xx/5xx errors.
- Commands editor:
setMyCommands/deleteMyCommandsas plain text with validation, for every scope (default,all_private_chats,all_group_chats,all_chat_administrators,chat,chat_administrators,chat_member), everylanguage_code, andis_ephemeral. - Profile:
setMyName,setMyDescription,setMyShortDescriptionper language. Only changed fields are sent, and rate limits (429 retry_after) are shown clearly. - Avatar:
setMyProfilePhoto(photo or video) andremoveMyProfilePhoto. - Menu button:
setChatMenuButtonfor commands, Web App (Mini App) or default, globally or per chat. - Admin rights:
setMyDefaultAdministratorRightsfor groups and channels, includingcan_manage_direct_messages,can_manage_tagsandcan_send_welcome_messages. - Bot info: every
getMecapability flag (guest mode, topics, business, Mini App…) and the Telegram Stars balance. - Developer tools: raw JSON responses, a request log and a ready-to-copy
curlcommand for every action. The token and secret are replaced with$BOT_TOKEN/$WEBHOOK_SECRET. - 5 languages, light and dark themes, works on mobile, accessible keyboard navigation.
| Profile | Commands | Admin rights | Mobile |
|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
- The site is static (GitHub Pages). There is no server that could store or log your token.
- Requests go from your browser directly to
https://api.telegram.org, or to an API server you choose. - By default the token is kept only in the current tab (
sessionStorage). “Remember on this device” useslocalStorage; Disconnect clears both. - The bot avatar is loaded straight from the Bot API server with
referrerpolicy="no-referrer"; through a CORS proxy it is downloaded as a blob instead. - Strict Content Security Policy, no analytics, no third-party scripts or fonts.
If a token leaks, revoke it with @BotFather → /revoke.
Some networks, countries or browser extensions block api.telegram.org. In that case deploy the bundled Cloudflare Worker (the free plan is enough):
- Cloudflare dashboard → Workers & Pages → Create → Worker → paste
proxy/cloudflare-worker.js→ Deploy. - Set the
ALLOWED_ORIGINvariable to your site origin (defaulthttps://f1devbin.github.io; comma-separated for several). Requests from other origins, and requests without anOriginheader, are rejected with 403. Use*only for a deliberately public proxy. - In Telegram Bot Manager open Advanced: API server and enter the worker URL.
A local Bot API server (http://localhost:8081) works the same way.
GitHub Pages: fork the repository → Settings → Pages → Source: GitHub Actions. Every push to main runs the tests and deploys the site. For a custom domain, set the repository variable SITE_URL (for example https://bots.example.com/) so canonical links and the sitemap use it.
Any static hosting:
npm run build # generates dist/
npm run serve # preview at http://localhost:8080Node.js 20+ is required. The project has no npm dependencies.
src/
templates/ layout.html, index.html (app + landing), guide.html
i18n/ en.json, ru.json, es.json, pt.json, zh.json
assets/js/ ES modules: api, validators, commands, curl, i18n, ui, tabs/*
assets/css/ app.css (light/dark design tokens)
static/ files copied to the site root as-is (e.g. a Google Search Console verification file)
scripts/
build.mjs static site generator: 5 languages × 5 pages, hreflang, sitemap, JSON-LD
serve.mjs local preview server
screenshots.mjs end-to-end test with a mocked Bot API + README screenshots (needs Playwright)
images.mjs icons and Open Graph images (needs Playwright)
proxy/ optional Cloudflare Worker CORS proxy
tests/ node:test unit tests
npm test # unit tests, locale consistency, build check
npm run build && node scripts/screenshots.mjs # e2e smoke test (Playwright + Chromium)Adding a language: copy src/i18n/en.json to <code>.json, translate it, and add the language to LANGS in scripts/build.mjs. The tests fail if any key is missing.
New Bot API version: update src/assets/js/data.js (update types, admin rights, getMe flags) and the translations; npm test lists every missing label. If a new parameter appears on a method the tool calls, add it to METHOD_PARAMS in scripts/check-bot-api.mjs and expose it in the UI when it matters.
- CI (
.github/workflows/ci.yml, on pull requests): unit tests, build, end-to-end test in Chromium against a mocked Bot API, and a Lighthouse audit (accessibility ≥ 95, best practices ≥ 90 and SEO ≥ 95 are errors; performance ≥ 85 is a warning; reports are attached to the run). - Bot API watch (
.github/workflows/bot-api-watch.yml, weekly): compares the latest Bot API spec withsrc/assets/js/data.jsviascripts/check-bot-api.mjs— update types, admin rights,getMeflags, scopes,BotCommand/MenuButton/InputProfilePhoto/WebhookInfofields and the parameters of every method the tool calls — and opens an issue labelledbot-api-updatewhen something is missing or the spec source looks stale. - Agent instructions for updating the project are in
CLAUDE.md.
How do I check my bot's webhook? Connect the bot and open the Webhook tab: it calls getWebhookInfo and explains the last error.
How do I fix “409 Conflict: can't use getUpdates method while webhook is active”? Delete the webhook (Webhook → Danger zone → Delete webhook), then use getUpdates.
Why don't I receive chat_member or reaction updates? They are excluded by default. Choose them explicitly in allowed_updates.
More in the guides: set a webhook · check a webhook · delete a webhook · bot commands.
Issues and pull requests are welcome. Please run npm test before submitting.
MIT © 2026 f1devbin.
Unofficial tool. Not affiliated with or endorsed by Telegram.




