Telegram Channel posts API

Request parameters

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": { … },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the source does not provide are never made up.

Errors and billing

401

Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.

422

Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.

402

Insufficient balance. Top up first.

429

Per-minute request limit reached. Wait for Retry-After and try again.

503

Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.

200 empty

The request completed without data and is not charged (billing.reason = empty_result_refunded).

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