Insights
This account against its follower cohort
/data-api/v2/insights/x/{handle}/benchmark- Scope
- insights:read
- Freshness
- catalog read
- Group
- Insights
- Platforms
- 1 of 7
What this endpoint answers
Where the account's engagement rate lands on the live percentile ladder of the tracked cohort, with the ladder itself, the population it is built from and the reach counterweight. The ladder is a distribution of per-account rates, so a placement is a rank among real accounts rather than a comparison against an average of averages.
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
- The reference population is NOT X as a whole. It is the accounts our crawl has scanned often enough to measure, and every one of them is large - the floor sits near 1.7M followers.
- Engagement rate falls as follower counts rise, so a smaller account will place higher on this ladder than the comparison really justifies. Use it to locate a large account among peers, not to grade a new one.
- The ladder is rebuilt from live percentiles on every cache refresh, never hardcoded, so a placement is against today's cohort.
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 |
|---|---|---|---|---|
handle | path | required | Cristiano | X handle without the @. |
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 "https://crmsolid.com/data-api/v2/insights/x/Cristiano/benchmark" \
-H "Authorization: Bearer psk_live_..."
const res = await fetch("https://crmsolid.com/data-api/v2/insights/x/Cristiano/benchmark", {
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();
import os
import requests
res = requests.get(
"https://crmsolid.com/data-api/v2/insights/x/Cristiano/benchmark",
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.
- Account username
- Cristiano
- Account followers
- 114,902,338
- Coverage tweets
- yes
- Coverage reliable
- yes
- Coverage originals sampled
- 27
- Benchmark engagement rate
- 0.048
- Benchmark percentile
- 75
- Benchmark band
- Top 25%
- Benchmark sentence
- At 0.048%, Cristiano sits above the 75th percentile of the 3,162 accounts in this comparison.
- Benchmark population accounts
- 3,162
- Benchmark population min followers
- 1,687,752
- Benchmark population median followers
- 2,840,444
- Benchmark population median view rate
- 0.743
- Benchmark population median reach pct
- 1.66
- Benchmark percentiles
- 6 items
{
"data": {
"account": {
"username": "Cristiano",
"followers": 114902338
},
"coverage": {
"tweets": true,
"reliable": true,
"originals_sampled": 27
},
"benchmark": {
"engagement_rate": 0.0476,
"percentile": 75,
"band": "Top 25%",
"sentence": "At 0.048%, Cristiano sits above the 75th percentile of the 3,162 accounts in this comparison.",
"population": {
"accounts": 3162,
"min_followers": 1687752,
"median_followers": 2840444,
"median_view_rate": 0.7425,
"median_reach_pct": 1.66
},
"percentiles": [
{
"p": 10,
"rate": 0.0003
},
{
"p": 25,
"rate": 0.0018
},
{
"p": 50,
"rate": 0.0117
},
{
"p": 75,
"rate": 0.0476
},
{
"p": 90,
"rate": 0.1458
},
{
"p": 99,
"rate": 0.7742
}
]
}
},
"meta": {
"request_id": "req_9f2c41a8b3d5",
"generated_at": "2026-08-23T09:14:02.317Z",
"took_ms": 42
}
}
The meta block
request_idstringrequiredUnique id for this request. Quote it in a support ticket.
generated_atstringrequiredServer time the response was produced.
took_msintegerrequiredMilliseconds spent server-side.
pagePageoptionalsourcestringoptionalWhich backend served the payload, for endpoints with more than one.
cache_age_sintegeroptionalAge of the underlying data in seconds. 0 for live reads.
When it fails
GET /insights/x/{handle}/benchmark documents 8 failure statuses. Branch on error.code, which is stable and enumerated; message is prose and may change.
- 401Unauthorized
unauthorized | invalid_keyNo key was presented, or the key is unknown, revoked or expired.
- 402PaymentRequired
payment_required | subscription_inactiveThe 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.
- 403Forbidden
forbidden_scope | forbidden_ipThe 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.
- 404NotFound
not_foundThe addressed resource does not exist.
- 422InvalidRequest
invalid_requestA parameter is malformed, out of range or mutually exclusive with another. `details` names the offending fields.
- 429RateLimited
rate_limited | quota_exceededEither 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.
- 500InternalError
internal_errorSomething failed on our side. Internals are never leaked; quote the request id.
- 503Unavailable
upstream_timeout | upstream_error | not_configuredThe 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 X. 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.
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.
Reference path: /data-api/reference/insights-x-benchmark