Measured engagement rates by follower band: GET /insights/instagram/benchmarks

What this endpoint answers

Engagement-rate percentiles for each follower band, computed over our own Instagram catalog rather than quoted from the industry rules of thumb every competitor ships. Every band publishes the number of accounts behind it and whether that number is enough to trust.

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

Measured medians on 2026-08-31: 14.28 percent under 10K, 5.09 at 10K-100K, 3.42 at 100K-1M, 1.67 at 1M-10M, 0.92 above 10M. The decline is monotonic across every band, which is the shape the field expects and the cheapest evidence that the pipeline behind it is sound.
The population is 2,535 accounts, not the full 10,947 catalog. Only 2,538 rows carry a follower count: Instagram's profile endpoint stopped answering anonymous callers, so the rest reached us through the feed fallback and have posts but no profile. catalog.coverage_pct states this on every response.
reliable is false for any band holding fewer than 100 accounts. The under-10K band holds 59 and is returned anyway, flagged, rather than dropped: a caller who asked for it deserves the number and the reason not to lean on it.
Upper percentiles are wide and genuinely so. An account whose posts reach far beyond its own followers can exceed 100 percent, which is a real measurement of an account whose reach outruns its follower count, not an error. Lead with p50.
oldest_measurement and newest_measurement bound the whole measured population. Every follower count in the benchmark was read within that window, so the bands are a snapshot of that window rather than a long-run average.
This path shadows the handle route: an Instagram account literally named 'benchmarks' would not be reachable at /insights/instagram/benchmarks. Use GET /accounts/instagram/{handle} for that one account.

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
`followers`	query	optional	`250000`	Optional. A follower count to locate in the bands; the response then names which band it falls in.

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/instagram/benchmarks" \
  -H "Authorization: Bearer psk_live_..."

JavaScript

const res = await fetch("https://crmsolid.com/data-api/v2/insights/instagram/benchmarks", {
  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/instagram/benchmarks",
    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.

Metric: engagement_rate_pct
Definition: (mean likes + mean comments) per post, divided by followers, times 100. Computed from the posts the crawl retains for e…
Catalog accounts total: 10,975
Catalog accounts measured: 2,536
Catalog coverage pct: 23.1
Catalog oldest measurement: 8/29/2026, 1:01:34 PM
Catalog newest measurement: 8/31/2026, 12:37:54 PM
Min sample for reliable: 100
Bands: 2 items

200 GET /insights/instagram/benchmarks

{
  "data": {
    "metric": "engagement_rate_pct",
    "definition": "(mean likes + mean comments) per post, divided by followers, times 100. Computed from the posts the crawl retains for each account, not from a sampled subset chosen at query time.",
    "catalog": {
      "accounts_total": 10975,
      "accounts_measured": 2536,
      "coverage_pct": 23.1,
      "oldest_measurement": "2026-08-29T13:01:34.350Z",
      "newest_measurement": "2026-08-31T12:37:54.495Z"
    },
    "min_sample_for_reliable": 100,
    "bands": [
      {
        "band": "100k_1m",
        "followers_from": 100000,
        "followers_to": 1000000,
        "sample_size": 754,
        "reliable": true,
        "observed_followers_min": 100199,
        "observed_followers_max": 998021,
        "p25": 0.95,
        "p50": 3.425,
        "p75": 9.483,
        "p90": 22.62,
        "avg_posts_analysed": 11.8
      },
      {
        "band": "under_10k",
        "followers_from": 0,
        "followers_to": 10000,
        "sample_size": 59,
        "reliable": false,
        "observed_followers_min": 212,
        "observed_followers_max": 9844,
        "p25": 2.866,
        "p50": 14.28,
        "p75": 74.963,
        "p90": 360.726,
        "avg_posts_analysed": 11.6
      }
    ],
    "your_band": null
  },
  "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/instagram/benchmarks documents 7 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.
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 Instagram. Rate limits come from the tier on your key.

Instagram

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-instagram-benchmarks