API de Telegram: Canal
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.
Precios y proveedores
Precios del endpoint Canal de la API de Telegram: una API, 3 proveedores intercambiables
El proveedor más barato responde primero. Si falla, el siguiente toma el relevo en la misma llamada.
Pruébalo
Obtén Canal de Telegram en una sola solicitud
{
"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"
}Referencia completa de parámetros y respuesta: cada campo, tipo y ejemplo de este endpoint.
Referencia
Una solicitud, un formato de respuesta.
Cada campo que envías y cada campo que recibes, cada uno con un ejemplo real.
Verificado por última vez el 2026-10-19 · disponibilidad y latencia medidas en 30d
Cuerpo de la solicitud
JSON, enviado por POST a este 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.
Respuesta
JSON, un valor de ejemplo por campo.
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.
- fileCountintegerse puede exigir
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.
- linkCountintegerse puede exigir
Links the channel has posted, rounded by Telegram. Null when not shown or when this source does not report it.
- photoCountintegerse puede exigir
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.
- videoCountintegerse puede exigir
Videos the channel has posted, rounded by Telegram. Null when not shown or when this source does not report it.
- 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.
Preguntas frecuentes
Acerca del endpoint Canal de la API de Telegram
El endpoint Canal de AnyAPI para Telegram devuelve datos de Telegram como JSON normalizado con una sola llamada POST a /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 enruta cada solicitud entre 3 fuentes y recurre automáticamente a otra cuando una falla. Cuesta desde US$1.10 por cada 1,000 solicitudes, en dólares estadounidenses, sin suscripción y sin mínimo mensual. En los últimos 30 días, el 100.0% de las llamadas al endpoint Canal de la API de Telegram a través de AnyAPI tuvo éxito, con un tiempo de respuesta mediano de 1.1 segundos en 2 llamadas medidas.