EN
Not connected

Parameters

Ctrl+Enter

Response

Bot API Tester lets you call the Telegram Bot API online, right from your browser: paste your bot token, pick any of the 185 methods of Bot API 10.3, fill in a typed parameter form and get the JSON response instantly. It is a free Telegram API playground and a lightweight Postman alternative to test a Telegram bot online, check a bot token or debug a request without writing code.

How to use the Telegram Bot API tester

  1. Get a token from @BotFather with /newbot (see how to get a bot token).
  2. Paste the token into the token field. It is saved in your browser's localStorage.
  3. Run getMe. A valid token returns your bot's User object; 401 Unauthorized means the token is wrong or revoked.
  4. Choose a method from the 19 categories or the search, or open it directly with a URL hash such as telegram-bot-api-tester.html#sendMessage.
  5. Fill in the parameters (required ones are marked) and click Execute or press Ctrl+Enter.
  6. Read the result in the collapsible JSON viewer and copy what you need.

Typical tasks

  • Check a Telegram bot token. getMe works as a token checker: one call shows whether the token is valid and which bot it belongs to.
  • Find a chat id. Start long polling, send your bot a message and read message.chat.id in the update history, which keeps the last 100 updates. Details in how to get a Telegram chat id.
  • Try messages and formatting. Test sendMessage with parse_mode, inline keyboards and link previews before you code them; see sending messages with the Bot API.
  • Manage webhooks. Call setWebhook, getWebhookInfo and deleteWebhook as described in the Telegram bot webhook guide.
  • Explore Bot API 10.x. Rich messages, ephemeral messages and join request queries are covered alongside the classic methods, ready to call with your token.

Because getUpdates doesn't work while a webhook is set, starting long polling calls deleteWebhook first (pending updates are kept). If your bot runs on a webhook in production, restore it with setWebhook when you're done.

Privacy: the token stays in your browser

The tester is a static page with no backend of its own. Your token is kept in your browser's localStorage, and every request goes directly from your browser to api.telegram.org, which supports CORS. Your token and API traffic never pass through our servers. For experiments, a separate test bot is still the safest choice.

More tools and references

Browse the OpenAPI 3.1 description of every method in Swagger, test the Telegram.WebApp JavaScript API in the Mini App Tester, or open the methods reference for parameters and curl, Python and JavaScript examples.

Frequently asked questions

How do I check if a Telegram bot token is valid?

Paste the token into the tester and run getMe. A valid token returns "ok": true with the bot's id and username; 401 Unauthorized means the token is wrong or has been revoked.

Is it safe to paste my bot token into this tester?

The token is stored only in your browser's localStorage, and requests go straight from your browser to api.telegram.org, never through our servers. On a shared computer, clear it after use; if a token leaks, revoke it with /revoke in @BotFather.

Can I use the Bot API Tester instead of Postman?

Yes, for the Telegram Bot API. Every method already has a typed form with parameter descriptions, there are no collections to import, and long polling, update history and a JSON viewer are built in.

Why does getUpdates return an empty result?

Usually there are simply no new updates: send your bot a message first. Updates are kept for only 24 hours, and getUpdates doesn't work while a webhook is set (409 Conflict), which is why the tester calls deleteWebhook before it starts polling.

Which Bot API version does the tester support?

Bot API 10.3 (August 24, 2026): all 185 methods in 19 categories, including rich messages, ephemeral messages and join request queries.

Updates 0

No updates.
Click "Start" to begin long polling.

Telegram Bot API v10.3Offset: —