Whether a channel's subscribers and its post views moved together: GET /insights/telegram/{username}/audience-quality

What this endpoint answers

The Telegram rollup records a channel's subscriber count and its average post views on the same row of the same day, and this is the only endpoint that reads the pair. Separately they are already served: activity is the views axis and growth-quality is the subscriber axis. Neither can say whether the two moved together, which is the actual question. Subscribers climbing while views sit still means people were added who do not open the channel. Subscribers falling while views climb means dormant accounts are being shed. Both shapes are here and nowhere else.

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

Only days carrying BOTH columns take part. A day the crawler could not read the channel's public preview has no avg_views, and it is dropped rather than read as zero: pairing across it would attribute one series' movement to the other's absence. Read window.days_observed as the denominator for everything else.
shape is two signs and a sentence, never a verdict. A channel whose subscribers rose while views fell has the same shape whether it bought a subscriber list or had a viral week that has since passed, and this endpoint will not pretend to tell those apart. change_pct sits beside each direction so the caller can judge the size.
projection is the one derived number here. It takes the views-per-subscriber ratio measured on the FIRST observed day, applies it to the subscriber count on the LAST, and reports the difference against what the channel actually pulls. A large negative gap means the audience added since the first day is not watching at the rate the earlier audience did.
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. For the ratio ranked against channels of the same size, use GET /insights/telegram/{username}/reach.
measurable is false with reason not_a_channel for groups, because Telegram publishes no per-post view count for them, and with reason insufficient_paired_history under four paired days. Neither is an error and neither is scored as zero.
Coverage measured on production 2026-08-31: 480 of the 500 largest channels (96%) hold at least seven paired days inside a 30 day window, at a mean of 22.0 paired days each. Across the whole daily table 84.4% of the rows written in the last seven days carry avg_views.

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	`toncoin`	Public @username or a t.me link.
`days`	query	optional	`30`	Calendar days of history to read back from today, 1 to 90. The rollup begins 2026-06-09, so no channel can answer for more than that.

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/toncoin/audience-quality" \
  -H "Authorization: Bearer psk_live_..."

JavaScript

const res = await fetch("https://crmsolid.com/data-api/v2/insights/telegram/toncoin/audience-quality", {
  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/toncoin/audience-quality",
    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: toncoin
Chat id: -1001233043722
Title: Gram of TON
Type: channel
Status: active
Subscribers: 6,863,255
Avg views: 383,000
Posts per day: 0.17
Window requested days: 30
Window from: 2026-08-01
Window to: 2026-08-31
Window days observed: 23
Window days spanned: 31
Window coverage pct: 74.2
Window longest gap days: 7
Measurable: yes
Audience first day: 2026-08-01
Audience first value: 7,142,642
Audience latest day: 2026-08-31
Audience latest value: 6,863,735
Audience change: -278,907
Audience change pct: -3.9
Audience direction: down
Reach first day: 2026-08-01
Reach first value: 340,776
Reach latest day: 2026-08-31
Reach latest value: 382,882
Reach change: 42,106

200 GET /insights/telegram/{username}/audience-quality

{
  "data": {
    "username": "toncoin",
    "chat_id": "-1001233043722",
    "title": "Gram of TON",
    "type": "channel",
    "status": "active",
    "subscribers": 6863255,
    "avg_views": 383000,
    "posts_per_day": 0.17,
    "window": {
      "requested_days": 30,
      "from": "2026-08-01",
      "to": "2026-08-31",
      "days_observed": 23,
      "days_spanned": 31,
      "coverage_pct": 74.2,
      "longest_gap_days": 7
    },
    "measurable": true,
    "reason": null,
    "audience": {
      "first": {
        "day": "2026-08-01",
        "value": 7142642
      },
      "latest": {
        "day": "2026-08-31",
        "value": 6863735
      },
      "change": -278907,
      "change_pct": -3.9,
      "direction": "down"
    },
    "reach": {
      "first": {
        "day": "2026-08-01",
        "value": 340776
      },
      "latest": {
        "day": "2026-08-31",
        "value": 382882
      },
      "change": 42106,
      "change_pct": 12.36,
      "direction": "up"
    },
    "reach_ratio": {
      "first": {
        "day": "2026-08-01",
        "value": 0.04771
      },
      "latest": {
        "day": "2026-08-31",
        "value": 0.05578
      },
      "change": 0.00807,
      "change_pct": 16.92,
      "direction": "up",
      "median": 0.05277,
      "min": 0.04771,
      "max": 0.05578
    },
    "shape": {
      "audience": "down",
      "reach": "up",
      "key": "audience_down_reach_up",
      "statement": "Subscribers fell while post views rose. The list is shrinking and what remains is more attentive, which is what shedding dormant accounts looks like."
    },
    "projection": {
      "basis_day": "2026-08-01",
      "basis_ratio": 0.04771,
      "expected_reach": 327469,
      "actual_reach": 382882,
      "gap": 55413,
      "gap_pct": 16.92
    },
    "freshness": {
      "last_observed_day": "2026-08-31",
      "data_age_days": 0,
      "channel_last_seen": "2026-08-31T12:09:24.441Z"
    },
    "series": [
      {
        "day": "2026-08-30",
        "subscribers": 6878417,
        "avg_views": 381352,
        "reach_ratio": 0.05544
      },
      {
        "day": "2026-08-31",
        "subscribers": 6863735,
        "avg_views": 382882,
        "reach_ratio": 0.05578
      }
    ]
  },
  "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}/audience-quality 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-audience-quality