Telegram Channel posts API
API health
- 24h health
- Normal
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Read the messages posted in a public Telegram channel. Each post has text, views, media, reactions and its forwarding source. Private invite links are not supported. The batch may not reach the full channel history.
Send POST https://api.everyinfra.com/api/v1/social with platform set to telegram and action set to channel_posts. Price $0.56 per 1,000 requests ($0.000556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
#Please help me write a data collection script with the EveryInfra Telegram Channel posts endpoint (telegram/channel_posts).
How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to telegram and action to channel_posts, and put the parameters inside params.
- Required parameters:
- username: Specifies the target public channel or group using formats such as name, @name, t.me/name, or t.me/s/name.
- Optional parameters:
- limit: The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, url, channel_username, channel_title, text, view_count, posted_at, media_type, media_url, author, is_forwarded, forwarded_from; 15 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=telegram.
- Example request body:
{
"platform": "telegram",
"action": "channel_posts",
"params": {
"username": "<PUBLIC_CHANNEL_USERNAME>"
}
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
#| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | telegram | Platform identifier, fixed value. |
action | body | string | Yes | channel_posts | Capability identifier, fixed value. |
username | body.params | string | Yes | - | Specifies the target public channel or group using formats such as name, @name, t.me/name, or t.me/s/name. Used by channel_posts and profile for public channels, group for public entity metadata, and members to retrieve visible group members; private invite links are not supported, and complete member lists are not guaranteed. |
limit | body.params | integer (1–200) | No | 20 | The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |
Code samples
#curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "telegram",
"action": "channel_posts",
"params": {
"username": "<PUBLIC_CHANNEL_USERNAME>"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
#{ "id": "req_…", "platform": "telegram", "action": "channel_posts", "results": [ { "id": …, "url": …, "channel_username": …, "channel_title": …, "text": …, "view_count": …, "posted_at": …, "media_type": …, "media_url": …, "author": …, "is_forwarded": …, "forwarded_from": …, "reply_to_url": …, "platform": …, "link_preview_url": …, "reactions": … } ], "count": …, "billing": { "charged": …, "charged_usd": …, "balance_after_usd": …, … }, "quota": { … }}
Response fields
#Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
url | Link to the record on the platform. |
channel_username | Keeps the platform's own meaning |
channel_title | Keeps the platform's own meaning |
text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
view_count | Views or plays. null means not disclosed, not 0. |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
media_type | Keeps the platform's own meaning |
media_url | Keeps the platform's own meaning |
author | Keeps the platform's own meaning |
is_forwarded | Keeps the platform's own meaning |
forwarded_from | Keeps the platform's own meaning |
reply_to_url | Keeps the platform's own meaning |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
link_preview_url | Keeps the platform's own meaning |
reactions | Keeps the platform's own meaning |
Errors and billing
#- 401
- Missing or invalid key.
- 402
- Insufficient balance. Top up first.
- 422
- Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
- 429
- Per-minute request limit reached. Wait for Retry-After, then try again.
- 503
- Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
- 200 empty
- No data. No charge.
Official references
#Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.
- Telegram Official: Channels, Public Usernames, and View Counts ↗
Official Telegram documentation distinguishes public channels from invite-only private channels, noting that channels function as broadcast tools and view counts include forwarded copies as approximate figures; this explains the channel object and view_count parameter, but does not prove this endpoint can read complete channel history or private content.
Checked 2026-09-04
- Telegram Official: Content Access Remains Subject to Licensing Terms ↗
Limited official exceptions for third-party clients, bots, and Mini Apps cover only data strictly necessary for operational functionality and remain bound by terms, copyright, and privacy rules; the mere existence of an API endpoint does not constitute authorization for scraping, reselling, or arbitrary re-use of platform data.
Checked 2026-09-04