Démarrer

L'API Telegram est-elle gratuite ? Le coût réel expliqué

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.
Build with Unipile
See the Telegram API product page
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.
Build a Telegram integration with Unipile
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.
Build without managing that infrastructure yourself
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.
Build on infrastructure that already respects these limits
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
Low effort
MTProto directBinary protocol, full account
Weeks of build
Linked account (Unipile)REST over the account connection
Days, not weeks
Unipile connects a Telegram user account, through Telegram's own Devices function (QR code login) or through Hosted Auth with 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.
Build the linked account route instead
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 APIMTProto direct (DIY)Linked account (Unipile)
API costFreeFreeFree API access, platform cost applies, see pricing
Account typeBot accountFull user accountFull user account
ProtocolHTTP / RESTBinary MTProtoREST, MTProto abstracted away
SetupToken from BotFatherapi_id / api_hash from my.telegram.org, custom client buildQR login or Hosted Auth, a few endpoints
Session managementHandled by TelegramYour responsibilityHandled by Unipile
Ban risk handlingPlatform-managed for botsEntirely your responsibilityUnipile applies Telegram's own pacing guidance; final volume and cadence stay a customer-side decision
GroupsLimited to bot permissionsFull, if you build itSupported (add / remove / list participants); channels, communities and broadcasts not supported
Best forAutomated triggers, simple botsTeams with dedicated MTProto engineering timeProduct 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
Setupapi_id / api_hash from my.telegram.org, custom client build
Session 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
Read the Telegram API setup guide
See the Telegram API product page
Get Started

Connect Telegram accounts without building MTProto

Unipile links a real Telegram user account, through the app's own Devices login, and exposes it as a single REST API alongside WhatsApp, LinkedIn, Instagram, Gmail, Outlook and IMAP. No MTProto client to maintain, no session store to build.
Start building
Read the setup guide See the Telegram API page

Tarification de l'API Telegram - FAQ

Des réponses claires sur la tarification de l'API Telegram, l'API Bot, MTProto et la façon dont Unipile connecte un compte Telegram.
Oui. Telegram indique que l'API Bot est utilisable gratuitement, sans frais par message et sans palier de volume. La version actuelle est la 10.2, publiée le 14 juillet 2026. Le coût d'exécution d'un bot provient du serveur et de l'infrastructure sur lesquels vous l'hébergez, et non de Telegram lui-même.
L'API Telegram (MTProto), le protocol à l'origine des clients Telegram complets, est également gratuite. Vous obtenez un id_api et clé d'API from my.telegram.org, limité à un id_api par numéro de téléphone, et aucune facturation n'est liée à leur utilisation. Le coût apparaît plus tard, dans l'infrastructure et le temps d'ingénierie nécessaires pour construire un client MTProto fonctionnel.
Non, et c'est un produit différent. L'API Gateway envoie des codes de vérification à usage unique pour l'authentification des comptes et est facturée par vérification. Elle est distincte de l'API Bot et de l'API Telegram, et ce n'est pas une API de messagerie, elle est donc hors du champ d'application d'une intégration de messagerie Telegram.
Non. Unipile lie un véritable Telegram espace client, en utilisant la propre fonction Appareils de Telegram (connexion par code QR) ou l'authentification hébergée avec fournisseurs : "TELEGRAM". Ce compte est ensuite exposé sous forme d'API REST. Il ne s'agit pas d'un compte de bot et il ne passe pas par l'API des bots.
Telegram déclare que les inondations, le spam et les compteurs artificiellement gonflés entraînent un bannissement permanent, et que les clients non officiels sont placés sous observation automatique. En pratique : évitez les comptes flambant neufs, augmentez progressivement le volume d'envoi et n'envoyez jamais plus d'un message toutes les 10 à 20 secondes. Un bannissement implique de reconstruire le compte et l'intégration, ce qui coûte plus cher que n'importe quel abonnement.
Les deux plateformes ne sont pas tarifées de la même manière. Meta facture la plateforme WhatsApp Business par message depuis le 1er juillet 2025. Telegram n'a pas de frais équivalents par message, ni sur l'API Bot ni sur l'API Telegram. Voir L'API WhatsApp est-elle gratuite ? pour comprendre le fonctionnement de ce modèle.
Vous hésitez encore entre l'API Bot, MTProto ou un compte lié ? Notre équipe peut vous guider.
Parler à un expert

fr_FRFR
en_USEN es_ESES de_DEDE it_ITIT pt_BRBR nl_NLNL pl_PLPL tr_TRTR fr_FRFR