Telegram Members API

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Telegram Members endpoint (telegram/members).

Endpoint contract:
- 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 members, 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 5000. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 100)
- Returns a list of records. Main fields of each record: id, username, url, name, type, is_verified, is_premium, is_scam, is_fake, last_seen_at, phone.
- Example request body:
{
  "platform": "telegram",
  "action": "members",
  "params": {
    "username": "DatascienceChats"
  }
}
- 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

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": "members",
  "params": {
    "username": "DatascienceChats"
  }
}'

[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": "members",
  "results": [
    {
      "id": 7413168036,
      "username": "（已隐去）",
      "url": "https://t.me/（已隐去）",
      "name": "（已隐去）",
      "last_seen_at": "2026-09-26T09:50:28+00:00",
      "platform": "telegram"
    },
    {
      "id": 80807914,
      "username": "（已隐去）",
      "url": "https://t.me/（已隐去）",
      "name": "（已隐去）",
      "last_seen_at": "last_week",
      "platform": "telegram"
    }
  ],
  "count": 8,
  "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.

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

The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.

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: Groups, Usernames, and Last Seen Privacy Settings ↗

  Official Telegram documentation details public usernames and t.me links, noting that last-seen status can be hidden or configured to display only approximate timeframes; member last_seen_at fields cannot be used to reconstruct exact activity histories, nor does a public username imply access to a public phone number.

  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