Measured Instagram engagement, placed against its cohort: GET /insights/instagram/{handle}

What this endpoint answers

Instagram is the one catalog whose crawl returns per-post like and comment counts, so this rate is measured rather than modelled. The response pairs the account's own numbers with the distribution of accounts its own size, because 'is 4.2% good' is only answerable next to the population it is being compared with - and that population is published alongside the answer rather than assumed.

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

engagement.measured is false when the crawl has not been able to read this account's posts. Every number in the block is then null: not measured is not the same claim as zero engagement, and this API never collapses the two.
rate is interactions per follower per post, in percent, over the twelve most recent posts the crawl read. It is not a lifetime average.
cohort is a bounded sample, not a census: up to 5,000 accounts in the 0.4x-2.5x follower band around this one, read in follower order. `scanned` is how many rows were read and `measured` is how many of those carry a rate - the percentiles' real n. Quote `measured`, not `scanned`.
The mean is carried beside the median deliberately. On a distribution this skewed the mean sits well above it, and that gap is the reason to quote the median.
An account the catalog has never reached answers 404. Use GET /accounts/instagram/{handle}/live to read one directly.
There is no equivalent endpoint for Bluesky, YouTube or TikTok. Those engines store profile counters and daily snapshots but nothing post-level, so any engagement rate we published for them would be a follower ratio wearing a measurement's clothes.

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	`nasa`	Instagram handle, with or 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

curl "https://crmsolid.com/data-api/v2/insights/instagram/nasa" \
  -H "Authorization: Bearer psk_live_..."

JavaScript

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

Handle: nasa
Account user id: 528817151
Account handle: nasa
Account full name: NASA
Account url: https://www.instagram.com/nasa/
Account avatar url: https://scontent.cdninstagram.com/v/t51.2885-19/...
Account followers: 104,443,318
Account following: 78
Account posts: 4,318
Account verified: yes
Account private: no
Account business: yes
Account ig category: Government Organization
Account category: science
Account language: en
Account tier: a
Account status: active
Account last post at: 8/29/2026, 6:02:44 PM
Account last seen: 8/30/2026, 4:02:11 AM
Account data age s: 18,711
Engagement measured: yes
Engagement rate: 0.421
Engagement avg likes: 402,118
Engagement avg comments: 2,904
Engagement avg interactions: 405,022
Engagement posts analyzed: 12
Cohort band min followers: 41,777,327
Cohort band max followers: 261,108,295

200 GET /insights/instagram/{handle}

{
  "data": {
    "handle": "nasa",
    "account": {
      "user_id": "528817151",
      "handle": "nasa",
      "full_name": "NASA",
      "url": "https://www.instagram.com/nasa/",
      "avatar_url": "https://scontent.cdninstagram.com/v/t51.2885-19/...",
      "followers": 104443318,
      "following": 78,
      "posts": 4318,
      "verified": true,
      "private": false,
      "business": true,
      "ig_category": "Government Organization",
      "category": "science",
      "language": "en",
      "tier": "a",
      "status": "active",
      "last_post_at": "2026-08-29T18:02:44.000Z",
      "last_seen": "2026-08-30T04:02:11.000Z",
      "data_age_s": 18711
    },
    "engagement": {
      "measured": true,
      "rate": 0.4213,
      "avg_likes": 402118,
      "avg_comments": 2904,
      "avg_interactions": 405022,
      "posts_analyzed": 12
    },
    "cohort": {
      "band": {
        "min_followers": 41777327,
        "max_followers": 261108295
      },
      "scanned": 812,
      "measured": 774,
      "percentile": 63,
      "percentiles": {
        "p10": 0.0611,
        "p25": 0.1402,
        "p50": 0.3118,
        "p75": 0.7204,
        "p90": 1.4402
      },
      "mean": 0.6119
    }
  },
  "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/{handle} 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 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-engagement