Measured likes per video by follower band: GET /insights/tiktok/benchmarks

What this endpoint answers

What a TikTok account of a given size normally earns per video, as percentiles over our own catalog. Every one of the 16,190 accounts carries the three counters this is built from, so every band is backed by hundreds of accounts rather than a rule of thumb.

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

Sample sizes measured 2026-08-31: 7,851 accounts under 10K, 3,784 at 10K-100K, 2,346 at 100K-1M, 1,224 at 1M-10M and 426 above 10M. Every band clears the 100-account floor, the smallest by more than four times.
Coverage is the TikTok catalog's advantage over the Instagram one: all 16,190 accounts carry a follower count, a like total and a video count. The measured population is smaller only because accounts with no videos yet are excluded, since dividing by zero videos is not a benchmark.
Median likes per video as a percent of followers falls monotonically with size - 21.8 percent under 10K, 5.46, 3.38, 2.22, 2.13 above 10M - which is the shape the field expects and the cheapest evidence the pipeline is sound.
This is a lifetime ratio and describes an account's whole history rather than its current form. An account that was large three years ago and is quiet now still reports well. Pair it with GET /insights/tiktok/{handle}/growth to see which way the account is moving.
The pre-2026-08-24 counter rounding does not reach these numbers: they read the current account row, which has been refreshed from statsV2 since the cutover.
This path shadows the handle route: a TikTok account named 'benchmarks' would not be reachable at /insights/tiktok/benchmarks. Use GET /accounts/tiktok/{handle} for that one account.

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

JavaScript

const res = await fetch("https://crmsolid.com/data-api/v2/insights/tiktok/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/tiktok/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: likes_per_video
Definition: Lifetime like total divided by lifetime video count, reported both absolutely and as a percent of followers. TikTok pub…
Catalog accounts total: 16,190
Catalog accounts measured: 15,631
Catalog coverage pct: 96.5
Catalog oldest measurement: 6/24/2026, 10:40:12 PM
Catalog newest measurement: 8/31/2026, 12:44:41 PM
Min sample for reliable: 100
Bands: 2 items

200 GET /insights/tiktok/benchmarks

{
  "data": {
    "metric": "likes_per_video",
    "definition": "Lifetime like total divided by lifetime video count, reported both absolutely and as a percent of followers. TikTok publishes no per-post data and no view counts to a logged-out reader, so this is the only engagement signal available at account level.",
    "catalog": {
      "accounts_total": 16190,
      "accounts_measured": 15631,
      "coverage_pct": 96.5,
      "oldest_measurement": "2026-06-24T22:40:12.204Z",
      "newest_measurement": "2026-08-31T12:44:41.432Z"
    },
    "min_sample_for_reliable": 100,
    "bands": [
      {
        "band": "100k_1m",
        "followers_from": 100000,
        "followers_to": 1000000,
        "sample_size": 2346,
        "reliable": true,
        "median_followers": 261201,
        "median_videos": 653,
        "likes_per_video": {
          "p25": 3884,
          "p50": 9667,
          "p75": 26183,
          "p90": 67410
        },
        "likes_per_video_pct_of_followers": {
          "p25": 1.497,
          "p50": 3.381,
          "p75": 8.713,
          "p90": 21.221
        }
      },
      {
        "band": "over_10m",
        "followers_from": 10000000,
        "followers_to": null,
        "sample_size": 426,
        "reliable": true,
        "median_followers": 17272708,
        "median_videos": 1371,
        "likes_per_video": {
          "p25": 219493,
          "p50": 392601,
          "p75": 798479,
          "p90": 1775785
        },
        "likes_per_video_pct_of_followers": {
          "p25": 1.228,
          "p50": 2.131,
          "p75": 3.598,
          "p90": 7.029
        }
      }
    ],
    "caveats": []
  },
  "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/tiktok/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 TikTok. Rate limits come from the tier on your key.

TikTok

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