Best Telegram API in 2026: Pricing Compared
Best Telegram API in 2026 by listed price: 7 SandBase channel endpoints, six at $0.001 and batch at $0.008. Official Bot API and TDLib are free, and a different product.

The official Bot API is free. That fact does not price a public-channel research call. On the 21 Nov 2026 catalog check (Asia/Shanghai), Telegram on SandBase listed 7 endpoints for channel info, posts, comments, similar channels, and keyword search. Six cards were a flat $0.001 per call. Batch Channel Info was $0.008 per call. Telegram APIs says you are welcome to use both the Bot API and the Telegram API with TDLib free of charge. Those are bots and custom clients. The Gateway API on the same page is a verification-code product. None of those pages is a rate card for the channel-research endpoints below. Accuracy and latency against other vendors stay Unknown.
Key takeaway
- On 21 Nov 2026 the SandBase Telegram hub listed 7 endpoints. Six were $0.001 per call. Batch Channel Info was $0.008. These are flat prices, not “From” floors.
- Channel Search and Channel Posts showed the row “100 free calls / day — First 100 calls per day free (shared per organization) · Resets at 00:00 UTC. Pay per call after that.” Channel Info and Batch Channel Info did not. The hub itself is not a free-quota badge.
- Official Bot API and TDLib are free of charge for bots and custom clients. Official per-call prices for public-channel research were not published. One thousand calls at the $0.001 price are $1.00 as list-price floor math.
- Call
POST https://api.sandbase.ai/v1/api/telegram/web/{endpoint}with a Bearer key. These representative cards were not flagged asynchronous. Do not start the call withPOST /v1/run.
What a Telegram API means in 2026
Three products share the name. Mixing them up is how a free bot gets quoted as the price of a channel archive.
The first is Telegram’s own platform. On 21 Nov 2026, Telegram APIs returned the title “Telegram APIs” and described three kinds: the Bot API, the Telegram API with TDLib (“You are welcome to use both APIs free of charge.”), and the Gateway API for verification codes. Bots: An introduction for developers says the Bot Platform is free for both users and developers. That is a real price: zero, for building a bot or a custom client. It is not a public price list for keyword search across channel posts.
The second product is a separate unofficial vendor account. This article does not name those vendors or borrow accuracy scores.
The third is the SandBase hub. The HTML title was “Telegram Data APIs: Research Channels and Public Post Activity | SandBase.” The Markdown twin counted 7 endpoints: channel info, batch channel info, channel post lists, post details and comment threads, similar-channel discovery, and keyword channel search. SandBase is not Telegram. Official Telegram terms still apply.
The useful stop: if you are shipping a bot, stay on core.telegram.org. If you are pricing a research read of public channel posts, read the card. The Gateway API is not that price either.
Telegram endpoints you can call on SandBase today
Do not flatten the hub to $0.001. Batch Channel Info is eight times that list price. The wider data API index listed 2,247 endpoints from 182 providers on the same check. The Social Media category footer counted 1,235 APIs. Those figures can change.
| Card | List price, 21 Nov 2026 | Call | What the card describes | Async | Free allowance |
|---|---|---|---|---|---|
| Channel Info | $0.001 per call | POST /v1/api/telegram/web/channel-info | Public metadata and usernames | Not flagged | No visible row |
| Channel Search | $0.001 per call | POST /v1/api/telegram/web/channel-search | Messages by keyword | Not flagged | Visible 100/day row |
| Channel Posts | $0.001 per call | POST /v1/api/telegram/web/channel-posts | Media, reactions, and views | Not flagged | Visible 100/day row |
| Post Detail | $0.001 per call | POST /v1/api/telegram/web/post-detail | A public post | Not flagged | Not confirmed on a captured card |
| Batch Channel Info | $0.008 per call | POST /v1/api/telegram/web/batch-channel-info | Public profiles in a batch | Not flagged | No visible row |
Also on the hub at $0.001: post comments and similar channels. Those two were not opened as screenshot cards here, so this article does not mark them eligible. Channel Search and Channel Posts are the cards that showed the shared daily row. That row is one pool of 100 calls per organization per UTC day, shared across eligible data APIs, not 100 free calls of each card. Channel Info and Batch Channel Info must not be described as eligible, even if a README sentence mentions a daily quota.

SandBase Telegram hub, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “Telegram Data APIs: Research Channels and Public Post Activity | SandBase.” The page is the 7-endpoint catalog. It is not a free-quota badge for every card.

SandBase Telegram Channel Info card, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “Telegram Channel Info API: Public Metadata and Usernames | SandBase.” The Markdown price was $0.001 per call. The card did not show a 100-free-calls row.

SandBase Telegram Channel Search card, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “Telegram Channel Search API: Find Messages by Keyword | SandBase.” The Markdown price was $0.001 per call. The card showed the shared 100-free-calls row.

SandBase Telegram Channel Posts card, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “Telegram Channel Posts API: Retrieve Media, Reactions and Views | SandBase.” The Markdown price was $0.001 per call. The card showed the same shared 100-free-calls row.

SandBase Telegram Batch Channel Info card, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “Telegram Batch Channel API: Retrieve Public Profiles and Badges | SandBase.” The Markdown price was $0.008 per call. The card did not show a 100-free-calls row.
Official Telegram API pricing versus the SandBase catalog
The rows are different products. Latency and accuracy are Unknown in every row.
| Path | What you can call, as checked 21 Nov 2026 | Billing | Free trial or allowance | Docs |
|---|---|---|---|---|
| Official Bot API and TDLib | Bots and custom clients. Gateway API is verification codes, a separate product. | Official pages say both APIs are free of charge. No public per-call card for channel-research reads. | The bot platform is free for users and developers. That is not a substitute allowance for SandBase channel cards. | Telegram APIs and bots |
| SandBase Telegram hub | 7 research endpoints. Six at $0.001. Batch Channel Info at $0.008. | Pay per call, no subscription. Start ($0), Build (Metered), Scale (Custom). | Channel Search and Channel Posts showed the shared 100-calls row. Channel Info and Batch Channel Info did not. | Live cards plus API passthrough |
| A separate unofficial vendor account | Whatever that vendor lists. Not measured here. | That vendor’s contract. Unknown here. | Unknown here. | That vendor’s own docs |
A dollar comparison against the official Bot API is the wrong comparison. Zero for a bot does not equal $0.001 for a channel-post read. Same-catalog context, not a bake-off: GitHub is the developer-research hub in this batch, and the Chinese social hubs (Weibo, Douyin, Xiaohongshu) are a different reader job. Pricing posts: Best Weibo API in 2026 and Best Social Media Data APIs for AI Agents (2026).
Best Telegram API for each need
- Lowest listed price: the six cards at $0.001, including Channel Info, Channel Search, and Channel Posts. Channel Info is cheap and still not free-quota eligible.
- Batch lookups: Batch Channel Info at $0.008. Budget it separately.
- Confirmed free-quota cards in this check: Channel Search and Channel Posts only. They share the organization pool. They do not each grant 100 calls.
- A bot, a custom client, or Gateway verification codes: official Telegram, not this hub.
How to call the Telegram API on SandBase
Data APIs use POST https://api.sandbase.ai/v1/api/{vendor}/{endpoint} with Authorization: Bearer $SANDBASE_API_KEY and a JSON body. Language models use POST /v1/chat/completions. Media models use POST /v1/run. Do not start a data API with POST /v1/run. The passthrough reference is the data-API page. The first API call walkthrough is chat completions only.
Channel Info and Channel Search were not flagged asynchronous on 21 Nov 2026. If a live card later says the endpoint runs asynchronously, poll GET https://api.sandbase.ai/v1/run/{id} until status is completed. That GET is the poll. Do not POST /v1/run to start. This comparison did not run a paid call. Replace the empty object with the fields on the live card. Read outputs[0].data. If that object is missing, fail loudly.
import os
import requests
payload = {} # replace with the fields on the live Channel Search card before sending
headers = {
"Authorization": f"Bearer {os.environ['SANDBASE_API_KEY']}",
"Content-Type": "application/json",
}
response = requests.post(
"https://api.sandbase.ai/v1/api/telegram/web/channel-search",
headers=headers,
json=payload,
timeout=90,
)
response.raise_for_status()
body = response.json()
# Channel Search was not flagged asynchronous on 21 Nov 2026.
# Do not POST /v1/run to start the data API.
outputs = body.get("outputs") or []
if body.get("status") not in (None, "completed") or not outputs or not isinstance(outputs[0], dict):
raise RuntimeError(f"SandBase call did not complete: {body.get('status')} {body.get('error')}")
data = outputs[0].get("data")Channel Info is /v1/api/telegram/web/channel-info. Channel Posts is /v1/api/telegram/web/channel-posts. The snippet is a client sketch, not a measured latency.

SandBase API passthrough page, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “API Passthrough.” It documents POST /v1/api/{vendor}/{endpoint} for data APIs. It is not a Telegram price.
What the daily allowance does and does not cover
Pricing and Pricing and Usage, checked 21 Nov 2026, give every organization 100 free data API calls per UTC day for eligible tools. The pool is shared across eligible data APIs and all org keys, resets at 00:00 UTC, and does not carry over. The pricing-page sample includes telegram/web/channel-posts and telegram/web/channel-search at $0.001. That sample is not a complete roster. The visible card is what this article uses. Channel Search and Channel Posts showed the row. Channel Info and Batch Channel Info did not. After the 100th eligible call, requests still complete and are billed at the listed price. A zero balance can still spend remaining allowance. Failed calls are not charged. Catalog browsing is $0. Plans are Start ($0), Build (Metered), and Scale (Custom). Language models and media models are not in the pool. Some pricier data APIs are billed from the first call. This hub’s batch card is one of the cards without the row.

SandBase pricing page, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “SandBase Pricing: Models, APIs and Usage-Based Billing.” Plans are pay per call. The page is not a Telegram rate card.

SandBase Pricing and Usage guide, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “Pricing and Usage.” Eligible data APIs share 100 free calls per organization per UTC day. Only the Telegram cards that showed the row are described as eligible.
One thousand Channel Search calls at $0.001 are $1.00 if every call bills at the list price. One thousand Batch Channel Info calls at $0.008 are $8.00 on the same assumption. That is list-price math, not an invoice. Subtract the shared 100 only for calls that actually drew on a card showing the row, and only until the organization pool is gone. Do not subtract 100 from Batch Channel Info.
When the cards look right, open Console API keys, read pricing, and use signup, which currently redirects to sign-in. Agents can start from the SandBase skill file.
When not to use the SandBase Telegram hub
Stay on Telegram for a bot, a custom client, official Bot API or TDLib features, and Gateway verification codes. Official Telegram terms still apply. Stay put when the buying criterion is a measured accuracy or latency rank among unofficial providers. This check did not produce that rank.
FAQ
What does “Telegram API” mean in this article?
The 7 SandBase cards for public channel research, checked 21 Nov 2026. The official Bot API, TDLib, and Gateway API stay on core.telegram.org and are a different product.
When is the SandBase hub a better fit than the official Bot API?
For a public channel profile, post list, or keyword search, billed per call on one key. For a bot or a custom client, start with Telegram. The official platform is free for that job. It does not publish a channel-data rate card.
How much do the SandBase Telegram endpoints cost?
$0.001 per call on six cards, and $0.008 on Batch Channel Info, on the 21 Nov 2026 hub. One thousand calls at $0.001 are $1.00 as list-price floor math.
Are the first 100 Telegram calls free?
Channel Search and Channel Posts showed the shared row: 100 free calls per organization per UTC day, resetting at 00:00 UTC, then the listed price. Channel Info and Batch Channel Info did not show that row. The allowance is shared, not 100 per card.
How do official Telegram APIs compare with SandBase?
Official Bot API and TDLib are free for bots and clients. SandBase lists 7 channel-research endpoints with public per-call prices. Latency and accuracy were not measured. Do not treat the Gateway API as the channel-data price.
Do official Telegram terms still apply?
Yes. A catalog price does not replace Telegram’s terms.
How do I start a call?
POST https://api.sandbase.ai/v1/api/telegram/web/channel-search (or channel-info, channel-posts, batch-channel-info) with a Bearer key. Do not POST /v1/run to start. Poll GET https://api.sandbase.ai/v1/run/{id} only if that live card says the endpoint is asynchronous.
Related reading
Field-level walkthroughs, not rewritten here: Telegram Public Data API, Telegram Channel Monitoring API, and Telegram Channel Search API. Developer-repository pricing is Best GitHub API in 2026.
Open the Telegram hub, then Channel Search or Channel Info beside the passthrough reference. Create a key in the Console, read pricing, or start from the skill file.
Found this useful? Share it