Skip to content
HookWatch beta
FeaturesUse casesPricingQuickstartSecurityCompare
Sign in Start beta
Troubleshooting

Telegram webhook not receiving updates

When a Telegram bot stops getting updates, check getWebhookInfo first — it reports the URL, pending count, and the last error Telegram saw from your endpoint.

Works with Telegram bot webhook updates. When your bot stops receiving updates, ask Telegram what it sees before touching your code: call getWebhookInfo.

Start with getWebhookInfo

https://api.telegram.org/bot<token>/getWebhookInfo returns the truth from Telegram’s side:

  • url — empty means setWebhook was never set, or was cleared.
  • pending_update_count — a growing number means Telegram is queuing updates it cannot deliver.
  • last_error_message — the actual reason delivery failed: bad HTTPS certificate, connection refused, or a non-2xx response.

Common causes

  • setWebhook not set — register the URL with the Bot API’s setWebhook call.
  • Non-HTTPS or invalid cert — Telegram requires HTTPS on a valid public URL.
  • Endpoint returns non-2xx or times out — a cold start or a bad deploy returns 502, and updates are dropped after retries.
Related

Keep reading

Get started

Start debugging your webhooks.

Point one endpoint at HookWatch, capture a failure, and replay it once it’s fixed. Free during beta.

Start debugging webhooks Read quickstart