Telegram API

Telegram Channel API

Get a public Telegram channel by username: name, bio, photo, verified badge, exact subscriber count, and how many photos, videos, files and links it has posted.

POST/v1/run/telegram.channel
Uptime
100.00%
30d · 2 calls
Requests
2
30d
Response
1.1s
median · 30d

Pricing and providers

Telegram Channel API pricing: one API, 3 interchangeable providers

The cheapest provider serves first. If it fails, the next one takes over in the same call.

Provider
1LemurServes first$1.10/1k reqflat2GiraffeBackup 1$1.20/1k reqflat3FoxBackup 2$3.60/1k reqflat
You pay
$11.00
$1.10/1k req, only for what you use. No monthly plan.
Your first 90 requests are free with the $0.10 starting balance.

Try it

Get Telegram channel in one request

requireFieldsarray
Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `photoCount`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a channel that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.
Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.
{
  "data": {
    "avatarUrl": "https://example.com/image.jpg",
    "description": "A short example description of this item.",
    "fileCount": 12500,
    "handle": "alex_rivera",
    "linkCount": 12500,
    "photoCount": 12500,
    "subscribers": 12500,
    "title": "Example title",
    "url": "https://example.com/page",
    "verified": true,
    "videoCount": 12500
  },
  "found": true,
  "reason": "not_found"
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

One request, one response shape.

Every field you send and every field you get back, each with a real example.

Last verified 2026-10-19 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • handlestring

    telegram

    Public Telegram channel username, with or without the @ (e.g. "telegram"), or its t.me link.

  • requireFieldsarray

    Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `photoCount`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a channel that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.

You send. A small JSON body. The values shown are examples to replace with your own.

Response

JSON, one example value per field.

datadata

The channel record, or null when nothing was found.

  • avatarUrlstring

    Channel photo URL. Temporary: Telegram's CDN link expires.

  • descriptionstring

    Channel bio as plain text; null when the channel has none.

  • fileCountintegercan require

    Files the channel has posted, rounded by Telegram. Null when not shown or when this source does not report it.

  • handlestring

    Channel username, without the @. Populated whenever the provider has data for the entity.

  • linkCountintegercan require

    Links the channel has posted, rounded by Telegram. Null when not shown or when this source does not report it.

  • photoCountintegercan require

    Photos the channel has posted. Telegram rounds this count ("1.2K" becomes 1200). Null when not shown or when this source does not report it.

  • subscribersinteger

    Exact subscriber count, read from the channel's public t.me page. Null when Telegram does not show it. Populated whenever the provider has data for the entity.

  • titlestring

    Channel name. Populated whenever the provider has data for the entity.

  • urlstring

    The channel's t.me link.

  • verifiedboolean

    True when the channel carries Telegram's verified badge. Null when this source does not report it.

  • videoCountintegercan require

    Videos the channel has posted, rounded by Telegram. Null when not shown or when this source does not report it.

top level
  • foundboolean

    True when the channel was found; false when no public channel has this username.

  • reason"not_found"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

You get back. Named, typed fields in the same shape whichever source answers.

FAQ

About the Telegram Channel API

The AnyAPI Telegram Channel API returns Telegram channel data as normalized JSON from one POST call to /v1/run/telegram.channel. Get a public Telegram channel by username: name, bio, photo, verified badge, exact subscriber count, and how many photos, videos, files and links it has posted. AnyAPI routes each request across 3 sources and falls back automatically when one fails. It costs from $1.10 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Telegram channel calls through AnyAPI succeeded, with a median response time of 1.1 seconds across 2 measured calls.

It costs from $1.10 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

Get a public Telegram channel by username: name, bio, photo, verified badge, exact subscriber count, and how many photos, videos, files and links it has posted. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of Telegram channel calls through AnyAPI succeeded, with a median response time of 1.1 seconds across 2 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

Yes. A new AnyAPI account starts with $0.10 of free balance and no card required, which covers 90 Telegram Channel calls at $0.0011 each.

AnyAPI asks the next of its 3 sources in the same request, cheapest first, so one source going down does not fail your call.

Send a POST request to https://api.getanyapi.com/v1/run/telegram.channel with your AnyAPI key in an "Authorization: Bearer" header and the input as a JSON body. The same key and the same wallet work on every AnyAPI endpoint.

No. You add US dollars to one prepaid AnyAPI balance and each request draws it down. There is no monthly plan and no minimum, and the same balance pays for every AnyAPI endpoint.

Yes. Install @getanyapi/sdk from npm for TypeScript or getanyapi from pip for Python. Both call every AnyAPI endpoint with the same key, and any HTTP client works too.

Yes. An agent can connect to the AnyAPI MCP server at https://api.getanyapi.com/mcp, or create its own free-trial key with one unauthenticated POST to https://api.getanyapi.com/agent/signup and call this endpoint over HTTP.