Measure a TikTok account's engagement: POST /tools/tiktok/engagement

What this endpoint answers

Computes engagement from lifetime hearts divided by video count against the follower base, the standard follower-based TikTok rate, and grades it against benchmarks for the account's size band.

This is a live read: it goes to the platform at request time, returns cache_age_s = 0, and is metered against a separate live-per-minute bucket on top of your tier. It needs the tools:use scope (Tools): Run the analysis tools: valuation, follower audit, scoring, and more.

Good to know

Costs money: exactly one ScrapeCreators credit per call. Metered as a live call.
Returns 503 not_configured when SCRAPECREATORS_API_KEY is unset, 404 not_found for an unknown or unreachable account, and 502 upstream_error when the upstream fails.
Ignores NEXT_PUBLIC_USE_MOCK_DATA: there is no mock path for this data.
TikTok's profile endpoint returns lifetime aggregates, not per-video data, so this is a lifetime average rather than a recent-content rate. It reacts slowly to a change in performance.
Profiles are cached in-process for 5 minutes, so a repeat call on the same handle inside that window does not spend a second credit.

Parameters

This endpoint takes no path or query parameters.

Request body

handlestringrequired
TikTok username. Accepts @name or a profile URL. Also accepted as `username`.

Example request body

{
  "handle": "khaby.lame"
}

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 -X POST "https://crmsolid.com/data-api/v2/tools/tiktok/engagement" \
  -H "Authorization: Bearer psk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"handle":"khaby.lame"}'

JavaScript

const res = await fetch("https://crmsolid.com/data-api/v2/tools/tiktok/engagement", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.CRM_SOLID_DATA_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "handle": "khaby.lame"
  }),
});

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 json
import os

import requests

body = json.loads("""
{
  "handle": "khaby.lame"
}
""")

res = requests.post(
    "https://crmsolid.com/data-api/v2/tools/tiktok/engagement",
    headers={"Authorization": f"Bearer {os.environ['CRM_SOLID_DATA_API_KEY']}"},
    json=body,
    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.

Profile handle: khaby.lame
Profile name: Khabane lame
Profile avatar url: https://p16-sign-va.tiktokcdn.com/khaby.jpeg
Profile verified: yes
Profile private: no
Profile bio: If you want to laugh you're in the right place
Profile followers: 162,400,000
Profile following: 82
Profile friends: 61
Profile total likes: 2,510,000,000
Profile video count: 1,284
Profile created at: 3/14/2020, 12:00:00 AM
Profile account age days: 2,354
Profile follower following ratio: 1,980,487.8
Engagement engagement rate: 1.2
Engagement avg likes per video: 1,954,828
Engagement likes per follower: 15.46
Rating: good
Rating score: 71
Benchmarks below: 0.4
Benchmarks average: 1
Benchmarks good: 2
Benchmarks excellent: 3.5
Summary size category: 10M+ followers · Mega Influencer

200 POST /tools/tiktok/engagement

{
  "data": {
    "profile": {
      "handle": "khaby.lame",
      "name": "Khabane lame",
      "avatar_url": "https://p16-sign-va.tiktokcdn.com/khaby.jpeg",
      "verified": true,
      "private": false,
      "bio": "If you want to laugh you're in the right place",
      "bio_link": null,
      "followers": 162400000,
      "following": 82,
      "friends": 61,
      "total_likes": 2510000000,
      "video_count": 1284,
      "created_at": "2020-03-14T00:00:00.000Z",
      "account_age_days": 2354,
      "follower_following_ratio": 1980487.8
    },
    "engagement": {
      "engagement_rate": 1.2,
      "avg_likes_per_video": 1954828,
      "likes_per_follower": 15.46
    },
    "rating": "good",
    "rating_score": 71,
    "benchmarks": {
      "below": 0.4,
      "average": 1,
      "good": 2,
      "excellent": 3.5
    },
    "summary": {
      "size_category": "10M+ followers · Mega Influencer"
    }
  },
  "meta": {
    "request_id": "req_9f2c41a8b3d5",
    "generated_at": "2026-08-23T09:14:02.317Z",
    "took_ms": 42,
    "cache_age_s": 0
  }
}

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

POST /tools/tiktok/engagement 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

Live reads count against the live column as well as the ordinary one, so a burst of them runs out of the live bucket first. 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 Tools group

The analysis tools behind the public free-tool pages, callable directly: valuation, follower audit, scoring and the rest. Metered like a live call, because each run costs compute or an upstream fetch.

Other groups

Accounts Directory X People Live scrape Insights Trends Identity Graph Watch Research 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/tools-tiktok-engagement