What each platform measures, how precise it is, and how deep: GET /insights/activity/platforms

What this endpoint answers

Coverage for the activity and growth-quality endpoints: which column each platform's second series reads, whether that platform's audience count is exact or rounded at the source and why, whether growth quality can be described at all, the freshest finished day, and the measured history depth. Reading precision at runtime is what stops a client from silently trusting a rounded number after a source changes.

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

latest_day is read live. null means freshness could not be read, which is unknown rather than stale.
The history counts are a measurement taken on the date they carry, not a live count: counting accounts by series length is a full scan of the daily table and took 56 seconds on Telegram, four times the pool's statement timeout. They move slowly and are re-measured by hand.
precision is about the SOURCE, not about our storage. A rounded count is what the platform published; nothing is rounded on the way in.
Instagram and X are absent because they are served elsewhere: X has a post layer behind /insights/x, and the Instagram daily rollup held 2,262 rows on 2026-08-30, which is not yet a series. LinkedIn has no account catalog with an audience over time at all.

Parameters

This endpoint takes no path or query parameters.

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

JavaScript

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

Platforms: 1 items

200 GET /insights/activity/platforms

{
  "data": {
    "platforms": [
      {
        "platform": "youtube",
        "metric": {
          "key": "views",
          "label": "Lifetime channel views",
          "kind": "cumulative_total",
          "measures": "Views added across the channel's whole back catalogue on that day, not views on new uploads alone."
        },
        "audience": {
          "metric": "subscribers",
          "precision": "rounded",
          "precision_note": "YouTube publishes subscriber counts rounded to three significant figures and we store what it publishes. Across 72,264 daily rows in the ten days to 2026-08-30 not one value was a non-multiple of ten. Subscriber deltas are therefore either zero or a whole rounding step, never a real day's gain."
        },
        "growth_quality": {
          "supported": false,
          "reason": "Every YouTube subscriber count we hold is rounded, so the shape of the series would be the shape of the rounding. GET /insights/youtube/{handle}/activity reads views instead, which are exact."
        },
        "latest_day": "2026-08-30",
        "history": {
          "measured_on": "2026-08-30",
          "accounts_with_series": 23068,
          "with_7_days": 9201,
          "with_30_days": 5010
        }
      }
    ]
  },
  "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/activity/platforms 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 is not platform-specific. 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-activity-platforms