Find accounts matching audience and engagement criteria

Cross-platform discovery: audience band, measured engagement, language, category, verified status and full-text terms, applied to every catalog at once and returned as one ranked group per platform. This is the 'find me creators like this' query, without running it six times.

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 directory:read scope (Directory): Read the account and channel catalog across all seven platforms.

curl "https://crmsolid.com/data-api/v2/people/search" \
  -H "Authorization: Bearer psk_live_..."

const res = await fetch("https://crmsolid.com/data-api/v2/people/search", {
  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();

import os

import requests

res = requests.get(
    "https://crmsolid.com/data-api/v2/people/search",
    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.

Filters min Audience

10,000

Filters max Audience

100,000

Filters min Engagement

3

Filters language

en

Filters verified Only

no

Groups

2 items

{
  "data": {
    "filters": {
      "minAudience": 10000,
      "maxAudience": 100000,
      "minEngagement": 3,
      "language": "en",
      "category": null,
      "verifiedOnly": false,
      "q": null
    },
    "groups": [
      {
        "platform": "instagram",
        "count": 10,
        "scan": "bounded",
        "ignored": [],
        "people": [
          {
            "platform": "instagram",
            "handle": "example",
            "name": "Example Creator",
            "audience": 48120,
            "audience_metric": "followers",
            "verified": false,
            "engagement_rate": 5.8102,
            "language": "en",
            "category": "fitness",
            "url": "https://instagram.com/example"
          }
        ]
      },
      {
        "platform": "x",
        "count": 10,
        "scan": "ranked",
        "ignored": [
          {
            "filter": "min_engagement",
            "reason": "Engagement is only measured where the crawl returns per-post counts, which today is Instagram."
          }
        ],
        "people": []
      }
    ],
    "unavailable": []
  },
  "meta": {
    "request_id": "req_9f2c41a8b3d5",
    "generated_at": "2026-08-23T09:14:02.317Z",
    "took_ms": 42
  }
}

• 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.

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.

• GET/people/lookupFind one handle across every catalog

Reference path: /data-api/reference/people-search