How many subscribers actually see a Telegram post: GET /insights/telegram/{username}/reach

What this endpoint answers

Telegram publishes per-post view counts, which makes it the one platform where the gap between an audience and its attention is directly observable. This scores a channel's average views against its own subscriber count and ranks that ratio inside the percentile ladder for channels of the same size. It is the strongest signal we have anywhere that a subscriber list was bought rather than earned.

This is a catalog read: it is served from the CRM Solid database in milliseconds, costs one budget unit, and reports how old the reading is in meta.cache_age_s. It needs the insights:read scope (Insights): Engagement rates, top posts, viral patterns, cohort benchmarks.

Good to know

score.scored is false whenever the ratio cannot be ranked, and `reason` says which of four things happened: no_view_sample (the crawler has never seen a post view count), not_a_channel (Telegram publishes no per-post views for groups), below_floor (under 1,000 subscribers the ratio is too noisy to rank) and no_benchmark (the ladder for that size has not been built). None of those is an error and none of them is scored as zero.
ratio is average views divided by subscribers. It is computed from the two stored inputs rather than read from the engine's own engagement column, which is still being backfilled and would make the score appear for some channels and not others for no visible reason.
A ratio above 1.0 is common and is not proof of a real audience: forwards, cross-posts and paid promotion all deliver views from outside the subscriber list. That is what the `amplified` verdict says out loud.
The percentile is against tracked channels in the same size band, not against Telegram. GET /insights/telegram/reach-bands publishes those ladders with their sample sizes and rebuild timestamps.
This lookup deliberately does not apply the directory's active/channel scope: someone checking a handle wants to hear 'this is a group' or 'this channel is no longer public' rather than a blank miss.

Parameters

Every value the call accepts, with the example the spec ships so the request runs as written.

Name	In	Required	Example	What it does
`username`	path	required	`durov`	Public @username or a t.me link.

Call it

Authenticate with a bearer token or the x-api-key header. Keys are server-to-server credentials. Never embed one in front-end code - call the API from your own backend and forward the result.

curl

curl "https://crmsolid.com/data-api/v2/insights/telegram/durov/reach" \
  -H "Authorization: Bearer psk_live_..."

JavaScript

const res = await fetch("https://crmsolid.com/data-api/v2/insights/telegram/durov/reach", {
  headers: {
    Authorization: `Bearer ${process.env.CRM_SOLID_DATA_API_KEY}`,
  },
});

if (!res.ok) {
  const { error } = await res.json();
  throw new Error(`${error.code}: ${error.message} (${error.request_id})`);
}

const { data, meta } = await res.json();

Python

import os

import requests

res = requests.get(
    "https://crmsolid.com/data-api/v2/insights/telegram/durov/reach",
    headers={"Authorization": f"Bearer {os.environ['CRM_SOLID_DATA_API_KEY']}"},
    timeout=30,
)
res.raise_for_status()

payload = res.json()
data, meta = payload["data"], payload["meta"]

Keys look like psk_live_... for production keys, psk_test_... for test keys and are minted in the panel.

What comes back

Success is { data, meta }. Failure is { error: { code, message, request_id } }. The body below is the spec's own example: the values in it are illustrative readings, not live numbers.

Username: durov
Title: Du rove
Type: channel
Subscribers: 1,402,882
Avg views: 402,118
Posts per day: 1.4
Last seen: 8/30/2026, 2:14:00 AM
Score scored: yes
Score ratio: 0.287
Score percentile: 94
Score verdict: amplified
Score verdict label: Pushed from outside
Score verdict summary: Each post is seen far more times than this channel has subscribers, so most of the reach is arriving from outside the s…
Score avg views: 402,118
Score subscribers: 1,402,882
Score band band: 500k+
Score band min subs: 500,000
Score band sample size: 1,193
Score band exact: yes
Score band median: 0.038
Score band computed at: 8/29/2026, 3:00:00 AM

200 GET /insights/telegram/{username}/reach

{
  "data": {
    "username": "durov",
    "title": "Du rove",
    "type": "channel",
    "subscribers": 1402882,
    "avg_views": 402118,
    "posts_per_day": 1.4,
    "last_seen": "2026-08-30T02:14:00.000Z",
    "score": {
      "scored": true,
      "ratio": 0.2866,
      "percentile": 94,
      "verdict": "amplified",
      "verdict_label": "Pushed from outside",
      "verdict_summary": "Each post is seen far more times than this channel has subscribers, so most of the reach is arriving from outside the subscriber list.",
      "avg_views": 402118,
      "subscribers": 1402882,
      "band": {
        "band": "500k+",
        "min_subs": 500000,
        "max_subs": null,
        "sample_size": 1193,
        "exact": true,
        "median": 0.0383,
        "computed_at": "2026-08-29T03:00:00.000Z"
      }
    }
  },
  "meta": {
    "request_id": "req_9f2c41a8b3d5",
    "generated_at": "2026-08-23T09:14:02.317Z",
    "took_ms": 42
  }
}

The meta block

request_idstringrequired
Unique id for this request. Quote it in a support ticket.
generated_atstringrequired
Server time the response was produced.
took_msintegerrequired
Milliseconds spent server-side.
pagePageoptional
sourcestringoptional
Which backend served the payload, for endpoints with more than one.
cache_age_sintegeroptional
Age of the underlying data in seconds. 0 for live reads.

When it fails

GET /insights/telegram/{username}/reach documents 8 failure statuses. Branch on error.code, which is stable and enumerated; message is prose and may change.

401Unauthorizedunauthorized | invalid_key
No key was presented, or the key is unknown, revoked or expired.
402PaymentRequiredpayment_required | subscription_inactive
The key is valid but the plan behind it cannot serve the call: the included requests are spent and overage is switched off, capped or unfunded (payment_required), or the billing period lapsed and was not renewed (subscription_inactive). Retrying does not help; paying does. The X-Plan-* headers on this response say how far past the line you are.
Carries X-Plan, X-Plan-Limit, X-Plan-Overage, X-Plan-Period-End, X-Plan-Remaining.
403Forbiddenforbidden_scope | forbidden_ip
The key is valid but not allowed to make this call: it lacks the scope, or the request came from an address outside the key's allowlist.
404NotFoundnot_found
The addressed resource does not exist.
422InvalidRequestinvalid_request
A parameter is malformed, out of range or mutually exclusive with another. `details` names the offending fields.
429RateLimitedrate_limited | quota_exceeded
Either the burst ceiling for the current minute or the daily quota is spent. Distinguish with the code: rate_limited clears within the minute, quota_exceeded does not clear until 00:00 UTC.
Carries Retry-After, X-Quota-Limit, X-Quota-Remaining, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-Request-Id.
500InternalErrorinternal_error
Something failed on our side. Internals are never leaked; quote the request id.
503Unavailableupstream_timeout | upstream_error | not_configured
The request could not be served right now. BRANCH ON error.code, not on the status: 'upstream_timeout' means a source was too slow (this is what a catalog query hitting its 15-second statement timeout returns, so it is reachable from any endpoint that reads the corpus, not only the live-scrape ones) and the same call is worth retrying with backoff - narrowing it with a smaller limit, a filtered scope or a less popular account makes it far less likely; 'upstream_error' means a source was unreachable, so back off further; 'not_configured' means the capability has no backing service in this deployment, and retrying will never help.

Every response carries X-Request-Id and meta.request_id. Quote it in support requests.

Coverage and limits

This endpoint covers Telegram. Rate limits come from the tier on your key.

Tier	Requests a minute	Requests a day	Live reads a minute
free	30	1,000	5
standard	120	25,000	20
pro	600	250,000	60
unlimited	6,000	10,000,000	600

This call only draws on the ordinary per-minute and per-day columns. Every response reports where you stand in X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset and the X-Plan headers.

The rest of the Insights group

Derived engagement intelligence: engagement rates, top and viral posts, posting patterns and cohort benchmarks computed over the post layer.

Other groups

Accounts Directory X People Live scrape Trends Identity Graph Watch Research Tools Leads

Start calling it

A key takes a minute to mint in the panel, no card. The reference covers authentication, the envelope, scopes, rate limits and every error code in one page.

Get a key All 127 endpoints Full reference What the Data API is

Reference path: /data-api/reference/insights-telegram-reach