LinkedIn
Instagram
WhatsApp
Telegramm
Google Mail
Ausblick
Google Kalender
Slack-Gemeinschaft beitreten Table of Contents
The Direct Answer
The Real Cost
Telegram API Pricing
Is the Telegram API Free? The Real Cost Isn't the Price
Yes, the Telegram Bot API and the Telegram API (MTProto) are both free to use, with no per-message fee and no pricing tier. But free access isn't the same as free to run. This guide covers the real Telegram API cost: infrastructure, ban risk, and MTProto implementation time.
Quick Answer
Is the Telegram API free? Yes, with one distinction
Both API surfaces you would use to build on Telegram, the Bot API and the Telegram API (MTProto), are free to use. There is no message quota, no per-message fee and no pricing tier tied to volume. That settles the Telegram API price question. It does not settle the cost question, which is a different thing and the actual subject of this article.
The Telegram API is free. No message-based pricing, no tier, no quota.
Telegram states both the Bot API and the Telegram API are usable free of charge. The Bot API is currently at version 10.2, published July 14, 2026. Free access is not the full story: the infrastructure, the ban risk, and the implementation time behind that access are where the real cost sits, and they're covered in the sections below.
Source: core.telegram.org, consulted August 10, 2026.
Telegram and WhatsApp are not priced the same way. Meta has billed the WhatsApp Business Platform per message since July 1, 2025. Telegram has no equivalent fee on either of its APIs. See is the WhatsApp API free for that model.
Pricing Breakdown
What's actually free, and what isn't
Telegram exposes three distinct API surfaces plus one consumer subscription. Only two of the four are free for developers. Confusing them is where most "is the Telegram API free" questions actually come from.
Bot APIFree
HTTP interface for bot accounts, created through
BotFather. Telegram states it is usable free of charge. Currently at version 10.2, published July 14, 2026. No message quota, no billing tier.Telegram API (MTProto)Free
The protocol behind full Telegram clients, also free to use. Requires an
api_id and api_hash obtained on my.telegram.org, one api_id per phone number.Gateway APIPaid
Sends one-time verification codes for account authentication. A separate product from the Bot API and the Telegram API, billed per verification. Out of scope for this article: it isn't a messaging API.
Telegram PremiumPaid
A consumer subscription for end users (larger uploads, reactions, badges). It sits on the user side of the app, not on the developer side, and has no bearing on whether an API integration is billed.
The Real Cost, Part 1
Infrastructure you still pay for
The Telegram API itself carries no fee, but nothing runs on its own. Whether you build on the Bot API or on MTProto directly, you're still responsible for the infrastructure that keeps a Telegram integration alive.
Server and uptime
A bot webhook or an MTProto client both need a server that stays up. Downtime means missed messages and updates, not a queued retry from Telegram's side.
Session and credential storage
MTProto sessions and your
api_id / api_hash pair need secure, durable storage. There is only one api_id per phone number, so losing or leaking it is expensive to fix.Webhook or persistent connection
Bots receive updates via webhook or long polling. Full MTProto clients hold a persistent connection open. Both need to be maintained, not just deployed once.
Reconnection and monitoring
Networks drop, sessions expire, devices get removed from Telegram's session list. Someone has to detect a disconnected state and recover it before messages start silently failing.
The Real Cost, Part 2
The real cost, part two: the risk of a ban
A free API doesn't mean a risk-free one. Telegram is explicit that certain behaviors get accounts and clients permanently banned, and unofficial clients are already watched more closely than the official app.
Flooding, spam and inflated counters
Telegram states that flooding, spam and inflated counters result in a permanent ban. This applies to both Bot API bots and MTProto-based clients acting on behalf of a user account.
Unofficial clients are already flagged
Clients built outside the official app are placed under automatic observation. A custom MTProto client starts under closer scrutiny than the app most users already have installed.
Shared credentials trigger real errors
The
api_id shipped inside open-source example code is a known case: reusing it triggers API_ID_PUBLISHED_FLOOD errors for end users, because Telegram sees a public credential shared across too many clients.What lowers the risk in practice
Avoid sending from brand-new accounts
Ramp up sending volume progressively
Never send faster than every 10 to 20 seconds
This is Unipile's own operating guidance for accounts using the Devices connection method, and it holds for anyone building on Telegram, bot or account. A permanent ban costs more than any subscription would: the account, the session and the integration all need to be rebuilt.
The Real Cost, Part 3
The real cost, part three: the time to implement MTProto
MTProto is a binary protocol, not a REST API. Building a client on it, even with a library like TDLib, Pyrogram, GramJS or Telethon, means handling the encryption handshake, session serialization, update gaps, media upload chunking, flood-wait backoff and multi-device sync yourself. That's engineering time no pricing page will ever show.
Bot APIHTTP, bot account
MTProto directBinary protocol, full account
Linked account (Unipile)REST over the account connection
Unipile connects a Telegram user account, through Telegram's own Devices function (QR code login) or through Hosted Auth with
Build the linked account route instead providers: "TELEGRAM", and exposes it as a REST API. This is not the Bot API: it's the same full account access MTProto gives you, without writing an MTProto client. If the linked device is removed from the account's Telegram sessions, the account simply goes disconnected, the same way any session drop would.Three Ways In
Bot API vs MTProto direct vs a linked account
All three routes reach a free Telegram API. What separates them is who owns the session, who owns the ban risk, and how many weeks it takes to ship.
| Bot API | MTProto direct (DIY) | Linked account (Unipile) | |
|---|---|---|---|
| API cost | Free | Free | Free API access, platform cost applies, see pricing |
| Account type | Bot account | Full user account | Full user account |
| Protocol | HTTP / REST | Binary MTProto | REST, MTProto abstracted away |
| Setup | Token from BotFather | api_id / api_hash from my.telegram.org, custom client build | QR login or Hosted Auth, a few endpoints |
| Session management | Handled by Telegram | Your responsibility | Handled by Unipile |
| Ban risk handling | Platform-managed for bots | Entirely your responsibility | Unipile applies Telegram's own pacing guidance; final volume and cadence stay a customer-side decision |
| Groups | Limited to bot permissions | Full, if you build it | Supported (add / remove / list participants); channels, communities and broadcasts not supported |
| Best for | Automated triggers, simple bots | Teams with dedicated MTProto engineering time | Product teams shipping account-level messaging without building MTProto |
Bot API
API costFree
Account typeBot account
ProtocolHTTP / REST
SetupToken from BotFather
Session managementHandled by Telegram
Ban risk handlingPlatform-managed for bots
GroupsLimited to bot permissions
Best forAutomated triggers, simple bots
MTProto direct (DIY)
API costFree
Account typeFull user account
ProtocolBinary MTProto
Setup
api_id / api_hash from my.telegram.org, custom client buildSession managementYour responsibility
Ban risk handlingEntirely your responsibility
GroupsFull, if you build it
Best forTeams with dedicated MTProto engineering time
Linked account (Unipile)Best
API costFree API access, platform cost applies, see pricing
Account typeFull user account
ProtocolREST, MTProto abstracted away
SetupQR login or Hosted Auth, a few endpoints
Session managementHandled by Unipile
Ban risk handlingApplies Telegram's own pacing guidance; volume and cadence stay a customer-side decision
GroupsSupported (add / remove / list participants); channels, communities and broadcasts not supported
Best forProduct teams shipping account-level messaging without building MTProto
Telegram API-Preise – FAQ
Klare Antworten zu Telegram-API-Preisen, der Bot-API, MTProto und wie Unipile ein Telegram-Konto verbindet.
Ja. Telegram gibt an, dass die Bot-API kostenlos nutzbar ist, ohne Gebühren pro Nachricht und ohne Volumenstaffelung. Die aktuelle Version ist 10.2, veröffentlicht am 14. Juli 2026. Die Kosten für den Betrieb eines Bots entstehen durch den Server und die Infrastruktur, auf der Sie ihn hosten, und nicht durch Telegram selbst.
Die Telegram-API (MTProto), das Protokoll hinter vollständigen Telegram-Clients, ist ebenfalls kostenlos. Sie erhalten einen
api_id und API-Hash from my.telegram.org, beschränkt auf eins api_id über eine Telefonnummer, und ihre Nutzung ist nicht mit Rechnungen verbunden. Die Kosten fallen später an, in Form der Infrastruktur und der Entwicklungszeit, die erforderlich sind, um einen funktionierenden MTProto-Client zu bauen.Nein, und es handelt sich um ein anderes Produkt. Die Gateway-API sendet einmalige Bestätigungscodes zur Kontoauthentifizierung und wird pro Bestätigung abgerechnet. Sie ist von der Bot-API und der Telegram-API getrennt und keine Messaging-API, weshalb sie außerhalb des Rahmens einer Telegram-Messaging-Integration liegt.
Nein. Unipile verknüpft ein echtes Telegram Benutzerkonto, unter Verwendung von Telegrams eigener Funktion „Geräte“ (QR-Code-Anmeldung) oder Hosted Auth mit
Anbieter: "TELEGRAM". Dieses Konto wird dann als REST-API bereitgestellt. Es handelt sich dabei nicht um ein Bot-Konto, und es läuft nicht über die Bot-API.Telegram gibt an, dass Flood, Spam und manipulierte Zähler zu einer permanenten Sperrung führen und dass inoffizielle Clients unter automatische Beobachtung gestellt werden. In der Praxis: Vermeiden Sie brandneue Accounts, steigern Sie das Versandvolumen schrittweise und senden Sie niemals schneller als alle 10 bis 20 Sekunden. Eine Sperrung bedeutet, dass der Account und die Integration neu aufgebaut werden müssen, was mehr kostet als jedes Abonnement.
Die beiden Plattformen werden nicht auf dieselbe Weise bepreist. Meta stellt die WhatsApp Business Platform seit dem 1. Juli 2025 pro Nachricht in Rechnung. Telegram hat weder für die Bot-API noch für die Telegram-API eine vergleichbare Gebühr pro Nachricht. Siehe Ist die WhatsApp API kostenlos? dafür, wie dieses Modell funktioniert.
Sie wägen noch zwischen Bot-API, MTProto oder einem verknüpften Konto ab? Unser Team berät Sie gerne.
DE 
EN 
FR 
ES 
IT 
BR 
NL 
PL 
TR