# Telegram Bot API > The Telegram Bot API is Telegram's HTTP interface for bot accounts. A bot sends and edits messages, media and polls, manages chats and takes payments, and receives user messages by long polling or webhook, with a token issued by @BotFather. - Canonical: https://www.anchorterminal.com/tools/telegram-bot - Markdown: https://www.anchorterminal.com/tools/telegram-bot.md (~7,650 tokens) - Slim: https://www.anchorterminal.com/tools/telegram-bot.min.md (~1,830 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/telegram-bot.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-10 ## Overview **Grade E · 43/100 · rank #885 of 950 · #14 in Messaging APIs · not agent-ready · confidence medium** ## Assessment Telegram's first-party bot interface is free, needs no card and documents 185 methods on one page with a dated changelog and numeric send limits. No OpenAPI document, status page, SLA or idempotency key was found, one token controls the whole bot and travels in the URL, and a person must create the bot in a chat with @BotFather. ## Facts | Field | Value | | --- | --- | | Vendor | Telegram Messenger Inc. (https://telegram.org) | | Kind | HTTP API | | Category | Messaging APIs (https://www.anchorterminal.com/categories/messaging) | | Transport | HTTP | | Endpoint | `https://api.telegram.org` | | Auth | API key · Self-serve. A person with a Telegram account sends `/newbot` to @BotFather and receives one token per bot. The token goes in the URL path of every request, as `https://api.telegram.org/bot/METHOD_NAME`. It has no scopes or expiry and gives full control of the bot. `/token` in @BotFather generates a new one. No OAuth, app review or sales approval applies. | | Pricing | Free (Free) · Free, with no card or contract. The one fee found is for paid broadcasts, 0.1 Telegram Stars per message sent above 30 a second, open to bots with at least 100,000 Stars and 100,000 monthly active users. A separate test environment exists for bots (checked 2026-10-09). | | x402 | No · No x402, MPP or L402 in the Bot API reference, the FAQ, the developer terms or the server source (checked 2026-10-09). | | Licence | Proprietary hosted service under the Telegram Bot Platform Developer Terms of Service. The Bot API server source in tdlib/telegram-bot-api is BSL-1.0 | | Source | https://github.com/tdlib/telegram-bot-api | | Docs | https://core.telegram.org/bots/api | | llms.txt | not found | | Last release | 2026-08-24 | | GitHub stars | 4,478 (as of 2026-10-09) | | API | HTTPS at https://api.telegram.org/bot/METHOD_NAME, version 10.3 of 24 August 2026. 185 methods and about 400 types. GET or POST, with parameters as query string, form, JSON or multipart. Method names are case-insensitive | | Access | Self-serve. A person sends `/newbot` to @BotFather in Telegram and receives the token. A user must start the bot or add it to a group before it can message them | | Credentials | One token per bot in the URL path, with no scopes or expiry. `/token` in @BotFather generates a new one. Managed bots have `getManagedBotToken` and `replaceManagedBotToken` | | Inbound | `getUpdates` long polling (1 to 100 updates a call, `offset`, `timeout`, `allowed_updates`) or a webhook set with `setWebhook`. The two are mutually exclusive, and updates are kept at most 24 hours | | Webhooks | HTTPS with TLS 1.2 or later on ports 443, 80, 88 or 8443, from 149.154.160.0/20 and 91.108.4.0/22. Optional `secret_token` returned in `X-Telegram-Bot-Api-Secret-Token`. Self-signed certificates can be uploaded | | Rate limits | About one message a second per chat with short bursts, 20 messages a minute in a group, about 30 messages a second in bulk. Paid broadcasts raise bulk sends to 1,000 a second | | Errors | JSON with `ok`, `error_code` and `description`, plus optional `parameters` holding `retry_after` or `migrate_to_chat_id`. The reference says `error_code` contents are subject to change. No error list is published | | Files | Downloads up to 20 MB with `getFile` and uploads up to 50 MB on the hosted API. A local server lifts uploads to 2,000 MB and removes the download limit | | Group privacy | Privacy mode is on by default, so a bot in a group receives only commands, replies to it and service messages unless it is an admin or the mode is disabled in @BotFather | | Fees | Free. Paid broadcasts cost 0.1 Stars per message above 30 a second and need 100,000 Stars and 100,000 monthly active users. Digital goods must be sold in Telegram Stars, and Stars sales carry a 15 per cent fee while topics in private chats are enabled | | Test environment | A separate environment with its own accounts and bots, called at https://api.telegram.org/bot/test/METHOD_NAME | | Self-hosting | tdlib/telegram-bot-api, C++, BSL-1.0, version 10.3, last commit 25 August 2026. Needs an `api_id` and `api_hash` from Telegram, and the bot must call `logOut` on the hosted server first | | Support | @BotSupport in Telegram, announcements on @BotNews and discussion in @BotTalk. @BotFather sends status alerts to popular bots whose reply rate drops | | Data handling | Privacy policy section 6 lists what bots receive. Data for UK and EEA sign-ups is stored in the Netherlands. Group companies in the British Virgin Islands and Dubai are named. No DPA or sub-processor list was found | | Status | No public status page, incident history or SLA was found | | Capabilities | messaging.inbound | | Tags | hosted, free, api-key, webhooks, long-polling, telegram, chat, open-source-server, bug-bounty, self-serve | | JSON | https://www.anchorterminal.com/api/v1/tools/telegram-bot.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 40 | 8.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 44 | 7.2 | | Agent ergonomics | 13% | 16.2 | 48 | 7.8 | | Security & auth | 14% | 17.5 | 35 | 6.1 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 38 | 3.3 | | Transparency & trust (editorial 53, provenance 74) | 7% | 8.8 | 64 | 5.6 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **43 → E** | ### Why each score - Reliability 40: Graded on the hosted API at api.telegram.org, with the hosted lines. No status page was found on core.telegram.org or telegram.org (0). With no readable incident history the record line takes the floor (5). Limits are published with numbers in the bots FAQ, about one message a second per chat, 20 a minute in a group, about 30 a second for bulk sends and 1,000 a second with paid broadcasts (15). Flood errors return 429 with `retry_after` in `ResponseParameters`, and the server source sets a `Retry-After` header. No idempotency key exists for sends (10). No SLA was found, and section 12.3 of the developer terms disclaims uptime and availability (0). The API is generally available at version 10.3 (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 44: No OpenAPI document or other machine-readable contract is published by Telegram (0). core.telegram.org/llms.txt answers with a not-found page and no Markdown copy of the docs was found (0). Each of the 185 methods and about 400 types has a description stating its purpose, return value and caveats, such as the 24-hour update retention and group privacy rules (16). Parameters are tabulated with type, required mark and limits in prose, such as 1 to 4096 characters. Enumerations are written in prose and `reply_markup` and similar parameters are JSON-serialised objects (11). Few request examples, and no error catalogue. The reference says `error_code` contents are subject to change (5). Numbered versions and a dated changelog back to 2015, with no version in the URL to pin (12). - Agent ergonomics 48: Responses are whole `Message` or `Update` objects with no field selection. `getUpdates` takes `limit` (1 to 100) and `allowed_updates` to narrow what arrives (12). `getUpdates` pages by `offset`, with `limit`, `timeout` and `allowed_updates`. A bot cannot list or search past messages in a chat (12). Errors carry `ok`, `error_code`, `description` and optional `parameters` with `retry_after` or `migrate_to_chat_id`. Descriptions are free text with no published list (10). No idempotency key for sends. `update_id` lets a receiver discard repeated inbound updates (5). `sendMessage` needs two parameters, GET and POST both work with four parameter encodings, and long polling needs no public server. No official SDK was found (9). - Security & auth 35: One token per bot gives full control, issued and regenerated in @BotFather with `/token`. It has no scopes or expiry. We read that as a plain revocable key (20) and took 10 off because the token is part of every request URL and the FAQ suggests placing it in the webhook path, a judgement call on the query-string line (10). Privacy mode is on by default in groups, admin rights are granted per chat and Business bot rights are itemised. There is no read-only token or approval step before a send (10). Inbound user messages are untrusted content, and no prompt-injection guidance was found in the reference or features page (3). No audit log of API calls was found. `getWebhookInfo` reports the last delivery error (2). A bug bounty with a safe-harbour statement and security@telegram.org, a webhook secret header and published source IP ranges. No security.txt, SOC 2 or ISO 27001 statement was found (10). - Payments & pricing 40: No x402, MPP or L402 in the reference, the FAQ, the developer terms or the server source (0). The API is free, stated without a login, and the one fee found is 0.1 Stars per broadcast message above 30 a second, for bots with 100,000 Stars and 100,000 monthly users (20). No card or payment method is needed to create a bot and send (20). A person with a Telegram account, which needs a phone number, must create the bot in a chat with @BotFather. Managed bots also need a user to confirm in a Telegram client (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 38: Closed service with an open-source server. The newest dated API change is Bot API 10.3 on 24 August 2026, 46 days before the check (20). Two dated changelog entries fall in the 90 days to 9 October 2026, 10.2 on 14 July and 10.3 on 24 August, so the three-entry line isn't met (0). A changelog, the @BotNews and @BotTalk channels and @BotSupport exist. tdlib/telegram-bot-api has 74 open issues, and we did not read how quickly they are answered (8). No official SDK was found. The official server source is current at 10.3 (5). The server repository had 44 commits between 11 July and 25 August 2026 and has no public CI configuration (5). - Transparency & trust 64: Editorial half only. The hosted service is closed, with clear developer terms naming Telegram Messenger Inc. The Bot API server source is public under BSL-1.0, an OSI-approved licence (22). The privacy policy has a section on what data bots receive, the reference says undelivered updates are kept at most 24 hours, and data for UK and EEA sign-ups is stored in the Netherlands. No DPA and no retention period for bot messages were found (15). No deprecation policy. Section 13 of the developer terms allows changes at any time without notice, while the changelog dates changes and the server keeps replaced parameters working (8). Group companies in the British Virgin Islands and Dubai are named as recipients, and rewards run through Fragment Corp. No sub-processor list was found (8). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (21 items): https://www.anchorterminal.com/fixes/telegram-bot.md (JSON https://www.anchorterminal.com/fixes/telegram-bot.json) ### What we couldn't check - unchecked: whether Telegram runs a public status page on a host not linked from the docs. None was found on core.telegram.org or telegram.org, and it was scored as absent - unchecked: how quickly issues on tdlib/telegram-bot-api are answered, and the content of bugs.telegram.org, which were not opened - unchecked: community libraries on core.telegram.org/bots/samples, which was not opened. No official SDK is named in the pages read - unchecked: the US dollar value of a Telegram Star, so the paid broadcast fee has no unit price - The developer terms carry no date. Section 4.3 prohibits data collection aimed at large datasets, machine learning models and AI products, and section 5.2(f) prohibits circumventing rate limits. Read both before any probe is run - The Security score takes 10 off for the token in the URL path. The checklist names the query string, so this is a judgement call - The changelog says 10.3 replaced `receiver_user_id` and `callback_query_id` 41 days after 10.2 added them. The server source at 10.3 still reads `receiver_user_id`, so no deduction was taken - telegram.org/privacy redirected to a /gb edition from our network. Other regional editions were not read - Not tested with a live bot, as we had no token - The lead held up. The category has no Telegram capability key, so only `messaging.inbound` is recorded ### Sources - Bot API reference, version 10.3: (seen 2026-10-09) - Bot API changelog: (seen 2026-10-09) - bots FAQ, limits and paid broadcasts: (seen 2026-10-09) - introduction to bots: (seen 2026-10-09) - bot functions, BotFather, privacy mode, test environment: (seen 2026-10-09) - webhook guide: (seen 2026-10-09) - Bot Platform Developer Terms of Service: (seen 2026-10-09) - Terms of Service for Bots (user-facing): (seen 2026-10-09) - privacy policy: (seen 2026-10-09) - bug bounty programme: (seen 2026-10-09) - Bot API server source, shallow clone: (seen 2026-10-09) - repository statistics: (seen 2026-10-09) - llms.txt check, not-found page: (seen 2026-10-09) - security.txt check, 404: (seen 2026-10-09) - robots.txt check, 404 on both hosts: (seen 2026-10-09) - RDAP for telegram.org: (seen 2026-10-09) ## Who's behind it (provenance 74/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Telegram Messenger Inc. | 20/20 | | Domain age | telegram.org, registered 2003-12-15 (22 years) | 15/15 | | Endpoint on the vendor's domain | api.telegram.org | 15/15 | | Terms of service | read, states 5 of the 7 things a reader expects, and has 1 clause that costs points | 6.3/10 | | Privacy policy | read, states 5 of the 8 things a reader expects | 7.8/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The Bot Platform Developer Terms of Service name Telegram Messenger Inc. as the contracting party and incorporate the Telegram Terms of Service and Privacy Policy. The page carries no date. The privacy policy names Telegram Messenger Inc. as controller, Telegram Group Inc and Telegraph Inc. in the British Virgin Islands and Telegram FZ-LLC in Dubai as group recipients, and EDPO as EEA representative. Its last listed change is 29 September 2024. The API answers at api.telegram.org and the docs at core.telegram.org, both telegram.org subdomains. telegram.org/.well-known/security.txt returns 404, and core.telegram.org/.well-known/security.txt and telegram.org/security.txt return ordinary web pages. The bug bounty page at core.telegram.org/bug-bounty takes reports at security@telegram.org. Neither core.telegram.org nor telegram.org serves a robots.txt (404 on both). No status page was found. RDAP for telegram.org gives a registration date of 2003-12-15. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://telegram.org/tos/bot-developers), read 2026-10-09, gives no date, states 5 of the 7 things a reader expects. - To know. Says the terms or the service can change without notice (costs points). "We may, at our sole and absolute discretion and without liability, at any time and without notice, modify Bot Platform in any way we deem necessary." - To know. Says access can be ended without notice or for any reason. "the availability of Bot Platform, and, by extension, access to the creation, operation and usage of TPA or some of their features for both you and your TPA users may change at any time, and we are not obligated to provide advance notice, compensation or explanations for any such changes." - Not found in the text. Gives the date it was last updated. - Not found in the text. Names the governing law or courts. - States a limit on its liability. Rules out indirect and consequential losses, with no cap named in this sentence. - Says how changes to the terms are announced. Changes are posted, with no other notice named. - Also in the text (2026-10-08). Bots may not collect data to build large datasets, machine learning models or AI products, and scraping public group or channel contents is named as a banned use. "Always prohibited uses include any form of data collection aimed at creating large datasets, machine learning models and AI products, such as scraping public group or channel contents." - Also in the text (2026-10-08). Developers grant Telegram a perpetual, transferable, sub-licensable, royalty-free licence to use their bot or mini app to improve the Telegram platform. "By accessing and utilizing Bot Platform, you consent to grant us a non-exclusive, perpetual, transferable, sub-licensable, royalty-free, and worldwide license to utilize (not reproduce) your TPA for the betterment of the Telegram ecosystem." - Also in the text (2026-10-08). Telegram may delete or make inaccessible chats, messages, media and files sent to and from a bot at any time. "Furthermore, you understand that Telegram may delete or make inaccessible whole chats, messages, media and files sent to and from your TPA at any time." **Privacy policy** (https://telegram.org/privacy), read 2026-10-09, dated 2024-06-01, states 5 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2024-06-01. - Says how long data is kept. Names a period of 12 months. - Not found in the text. Says whether personal data is sold or shared for advertising. - Not found in the text. Gives a privacy contact. - Not found in the text. Says where data is transferred or stored. - Also in the text (2026-10-08). An account not used for 18 months is deleted by default, with all its messages, media and contacts. "By default, if you stop using Telegram and do not come online for at least 18 months, your account will be deleted along with all messages, media, contacts and every other piece of data you store in the Telegram cloud." - Also in the text (2026-10-08). A third-party bot connected through Telegram Business can read all messages, media and files in the private chats the account holder lets it manage. "Additionally, the bot will have access to all messages, media and files contained in the private chats you allow it to manage." ## Live (updated 2026-10-10 02:07 UTC) - Right now: up, HTTP 200, 123 ms, checked 2026-10-10 02:07 UTC (get on `https://api.telegram.org`) - Uptime 24h 100.0% (107 probes) · 30 days 100.0% (107 probes) · p50 116 ms · p95 503 ms - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/telegram-bot.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - Free to use with no card. Limits are published as numbers, about one message a second per chat, 20 a minute in a group and about 30 a second in bulk - Flood errors return HTTP 429 with `retry_after` in the response `parameters`, and the open-source server sets a `Retry-After` header - Inbound messages arrive by `getUpdates` long polling with no public server, or by webhook with a `secret_token` echoed in `X-Telegram-Bot-Api-Secret-Token` - The Bot API server is open source under BSL-1.0 in tdlib/telegram-bot-api, at version 10.3, and can be self-hosted for larger files - A dated changelog covers every version, and the server source still accepts `receiver_user_id` and `correct_option_id` after the changelog said they were replaced ## Weaknesses - No OpenAPI document, llms.txt or official SDK was found. The contract is one HTML reference page of about 860 KB - One token gives full control of the bot, sits in the URL path of every request, and has no scopes or read-only form - No status page, SLA or incident history was found, and the developer terms disclaim uptime and allow changes without notice - No idempotency key exists for sends, and `error_code` contents are described as subject to change with no published error catalogue - A person with a Telegram account must create the bot in a chat with @BotFather, and a bot cannot message a user who has not started it - Developer terms section 4.3 prohibits collecting data for large datasets, machine learning models and AI products. Recorded as a fact, and it matters before any probe is run ## Before you call it (notes for agents) 1. Send `POST https://api.telegram.org/bot/sendMessage` with `chat_id` and `text`. Keep the token out of logs, because it is part of the URL. 2. On HTTP 429 wait the `parameters.retry_after` seconds before retrying. Stay under one message a second per chat and 20 a minute per group. 3. Call `getUpdates` with `offset` set to the last `update_id` plus one, or the same updates return. Updates are kept for at most 24 hours. 4. A retried send can post twice, as there is no idempotency key. Record the returned `message_id` before retrying after a timeout. 5. In groups the bot sees only commands and replies unless privacy mode is disabled in @BotFather or the bot is an admin. ## Connect First request: ```bash curl https://api.telegram.org/bot/getMe ``` Through letme (picks today, calling later): https://letme.dev/telegram-bot. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Twilio API + MCP | A | 80.4 | 8 | messaging.inbound | no | https://www.anchorterminal.com/tools/twilio.md | | Bird API + MCP | BB | 76.5 | 29 | messaging.inbound | no | https://www.anchorterminal.com/tools/bird.md | | AWS End User Messaging | BB | 74.3 | 73 | messaging.inbound | no | https://www.anchorterminal.com/tools/aws-end-user-messaging.md | | Telnyx API + MCP | BB | 73.6 | 87 | messaging.inbound | no | https://www.anchorterminal.com/tools/telnyx.md | | MailSlurp | B | 68.4 | 215 | messaging.inbound | no | https://www.anchorterminal.com/tools/mailslurp.md | | WhatsApp Business Platform (Cloud API) | B | 67.1 | 264 | messaging.inbound | no | https://www.anchorterminal.com/tools/whatsapp-cloud-api.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Bot API 10.3 is dated 24 August 2026, after 10.2 on 14 July, 10.1 on 11 June and 10.0 on 8 May (source: ) - The reference lists 185 methods and about 400 types on one page, and accepts GET or POST with query string, form, JSON or multipart parameters (source: ) - Bots can send about one message a second per chat, 20 a minute in a group and about 30 a second in bulk, or 1,000 a second with paid broadcasts at 0.1 Stars a message (source: ) - Undelivered updates are stored for at most 24 hours, and `getUpdates` and webhooks cannot be used together (source: ) - The Bot API server is open source and can be run locally, which lifts uploads to 2,000 MB and allows HTTP webhooks (source: ) - Section 4.3 of the developer terms prohibits data collection aimed at large datasets, machine learning models and AI products, such as scraping public groups or channels (source: ) - Section 13 of the developer terms lets Telegram modify the Bot Platform at any time without notice, and section 12.3 disclaims uptime (source: ) - The bug bounty covers telegram.org domains and takes reports at security@telegram.org, with a statement that no legal action follows responsible disclosure (source: ) - #14 of 14 in Best SMS, WhatsApp and messaging APIs for AI agents: https://www.anchorterminal.com/best/messaging/index.md - All 91 messaging comparisons: https://www.anchorterminal.com/compare/messaging/index.md ## Compare - [360dialog WhatsApp API + MCP vs Telegram Bot API](https://www.anchorterminal.com/compare/360dialog-vs-telegram-bot.md): D 52 vs E 43 - [AWS End User Messaging vs Telegram Bot API](https://www.anchorterminal.com/compare/aws-end-user-messaging-vs-telegram-bot.md): BB 74.3 vs E 43 - [Bandwidth Messaging API + MCP vs Telegram Bot API](https://www.anchorterminal.com/compare/bandwidth-vs-telegram-bot.md): B 64.3 vs E 43 - [Bird API + MCP vs Telegram Bot API](https://www.anchorterminal.com/compare/bird-vs-telegram-bot.md): BB 76.5 vs E 43 - [ClickSend SMS API + MCP vs Telegram Bot API](https://www.anchorterminal.com/compare/clicksend-vs-telegram-bot.md): D 47.7 vs E 43 - [Infobip API + MCP vs Telegram Bot API](https://www.anchorterminal.com/compare/infobip-vs-telegram-bot.md): C 59.1 vs E 43 - [Plivo API vs Telegram Bot API](https://www.anchorterminal.com/compare/plivo-vs-telegram-bot.md): C 60.3 vs E 43 - [Sendblue vs Telegram Bot API](https://www.anchorterminal.com/compare/sendblue-vs-telegram-bot.md): C 61.7 vs E 43 - [Sinch Messaging APIs + MCP vs Telegram Bot API](https://www.anchorterminal.com/compare/sinch-vs-telegram-bot.md): B 63.2 vs E 43 - [Telegram Bot API vs Telnyx API + MCP](https://www.anchorterminal.com/compare/telegram-bot-vs-telnyx.md): E 43 vs BB 73.6 - [Telegram Bot API vs Twilio API + MCP](https://www.anchorterminal.com/compare/telegram-bot-vs-twilio.md): E 43 vs A 80.4 - [Telegram Bot API vs Vonage Messages API + MCP](https://www.anchorterminal.com/compare/telegram-bot-vs-vonage.md): E 43 vs B 66.8 - [Telegram Bot API vs WhatsApp Business Platform (Cloud API)](https://www.anchorterminal.com/compare/telegram-bot-vs-whatsapp-cloud-api.md): E 43 vs B 67.1 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on telegram.org or one of its subdomains, or the README of github.com/tdlib/telegram-bot-api. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "telegram-bot", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Telegram Bot API on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Telegram Bot API on Anchor Terminal](https://www.anchorterminal.com/badges/telegram-bot.svg)](https://www.anchorterminal.com/tools/telegram-bot) ``` Plain link: ```html Telegram Bot API on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Telegram Bot API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/telegram-bot-dark.png - Light: https://www.anchorterminal.com/assets/share/telegram-bot-light.png