Telegram Bot API

Telegram Bot Webhook Checker

Check your Telegram bot's webhook in one click: the tool calls getWebhookInfo, shows the URL, pending updates and the last delivery error with a hint how to fix it, and lets you set or delete the webhook.

The token stays in your browser (localStorage) and is sent only to api.telegram.org.

Set or change the webhook

How to check a Telegram bot webhook

  1. Paste the bot token. Tick Test server if the bot is in the test environment.
  2. Press Check webhook. You get one of three results: no webhook (the bot uses getUpdates), a webhook without errors in the last 24 hours, or a delivery problem with the time and text of the last error plus a hint.
  3. Check the pending updates counter. More than 100 is highlighted: updates are piling up because your server does not accept them.
  4. Below you see the full getWebhookInfo response: url, has_custom_certificate, pending_update_count, last_error_date, last_error_message, max_connections and other fields.
  5. To change it, open Set or change the webhook: enter an HTTPS URL, an optional secret_token, choose whether to drop pending updates and press setWebhook or deleteWebhook. The check runs again automatically.

Common webhook errors

The hint is picked from the text of last_error_message:

Error looks likeWhat to check
SSL / certificateA valid certificate for the domain (or a self-signed one uploaded via the certificate parameter of setWebhook), TLS 1.2+.
Wrong response from the webhook: 4xx/5xxThe path, your secret_token check and server errors — Telegram expects 2xx.
Timeout / connection resetThe server must be reachable from the internet on port 443, 80, 88 or 8443 and answer quickly.
Connection refusedNothing listens on the port, or a firewall blocks Telegram.
Host can't be resolvedDNS records of the webhook domain.

The form sends only url, secret_token and drop_pending_updates. The secret (1–256 characters A-Z a-z 0-9 _ -) arrives in the X-Telegram-Bot-Api-Secret-Token header of every request. For allowed_updates, max_connections or a certificate use /telegram-bot-api-tester.html#setWebhook.

Privacy

The token stays in your browser's localStorage, and getWebhookInfo, setWebhook and deleteWebhook are sent directly to api.telegram.org — nothing passes through our server. The same call is available in /telegram-bot-api-tester.html#getWebhookInfo. A complete setup walkthrough is in /guides/telegram-bot-webhook.html, and 409 Conflict and other errors are covered in /guides/telegram-bot-api-errors.html.

Frequently asked questions

How do I check if my Telegram bot has a webhook?

Call getWebhookInfo. If url is empty, no webhook is set and the bot works with getUpdates. The checker above calls it for you and explains the result.

How do I delete a Telegram bot webhook?

Call deleteWebhook — in the tool open Set or change the webhook and press deleteWebhook. Tick Drop pending updates only if you want to discard queued updates. After that getUpdates works again.

Why is pending_update_count growing?

Telegram can't deliver updates: your server is unreachable, slow or answers with a non-2xx status. Look at last_error_message; Telegram keeps retrying, and updates are stored for up to 24 hours.

What does "Wrong response from the webhook" mean?

Your server answered with an HTTP status other than 2xx, for example 404 for a wrong path or 500 for a crash. Telegram expects a quick 2xx response and retries otherwise.

Other utilities

Chat ID finderMarkdownV2 & HTML escaperMini App initData validatorBot API Tester