Accounts

Check up to 50 accounts at once

POST/data-api/v2/accounts/check

Get a key All 127 endpoints OpenAPI spec

Scope: directory:read
Freshness: catalog read
Group: Accounts
Platforms: any

What this endpoint answers

The bulk form of the catalog check: an array of { platform, handle } pairs, each answered independently in the same shape. Built for enriching a list - a CRM export, an influencer roster, a due-diligence sheet - in one round trip instead of fifty.

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.

Good to know

One request is one request against your rate limit however many targets it carries. The database work is real per target, so batch to be efficient rather than to evade the limit.
The cap is 50 because each target is a probe on a different table and the read pool is shared with every directory page on the site.
The envelope stays 200 whenever the request was well formed, even if every target failed. Branch on results[].ok and on check.catalog.state, not on the status code.
`found` counts the targets whose catalog state is present. A target that is merely not indexed is not an error.
This is the catalog check only. There is no bulk live check, and that is deliberate: fifty upstream reads in one call would spend more of a source's per-minute budget than any single caller is allowed to hold.

Parameters

This endpoint takes no path or query parameters.

Request body

targetsobject[]required
Array of { platform, handle } objects, at most 50. Duplicate pairs are collapsed.

Example request body

{
  "targets": [
    {
      "platform": "x",
      "handle": "nasa"
    },
    {
      "platform": "instagram",
      "handle": "nasa"
    }
  ]
}

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/accounts/check" \
  -H "Authorization: Bearer psk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"targets":[{"platform":"x","handle":"nasa"},{"platform":"instagram","handle":"nasa"}]}'

JavaScript

const res = await fetch("https://crmsolid.com/data-api/v2/accounts/check", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.CRM_SOLID_DATA_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "targets": [
      {
        "platform": "x",
        "handle": "nasa"
      },
      {
        "platform": "instagram",
        "handle": "nasa"
      }
    ]
  }),
});

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("""
{
  "targets": [
    {
      "platform": "x",
      "handle": "nasa"
    },
    {
      "platform": "instagram",
      "handle": "nasa"
    }
  ]
}
""")

res = requests.post(
    "https://crmsolid.com/data-api/v2/accounts/check",
    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.

Requested: 2
Found: 2
Results: 2 items

200 POST /accounts/check

{
  "data": {
    "requested": 2,
    "found": 2,
    "results": [
      {
        "platform": "x",
        "handle": "nasa",
        "ok": true,
        "check": {
          "platform": "x",
          "handle": "nasa",
          "checked_at": "2026-08-30T09:14:02.113Z",
          "exists": true,
          "evidence": "catalog",
          "identity": {
            "id": "528817151",
            "handle": "nasa",
            "name": "NASA",
            "avatar_url": "https://scontent.cdninstagram.com/v/t51.2885-19/...",
            "url": "https://www.instagram.com/nasa/",
            "object": "account"
          },
          "audience": {
            "count": 104443318,
            "metric": "followers",
            "precision": "exact"
          },
          "flags": {
            "verified": true,
            "private": false,
            "nsfw": false
          },
          "created_at": null,
          "catalog": {
            "state": "present",
            "status": "active",
            "tier": "a",
            "category": "science",
            "language": "en",
            "country": null,
            "last_seen": "2026-08-30T04:02:11.000Z",
            "data_age_s": 18711,
            "directory_url": "/best-instagram-accounts/nasa",
            "metrics": {
              "engagement_rate": 0.4213,
              "avg_likes": 402118,
              "avg_comments": 2904,
              "posts_analyzed": 12,
              "citation_score": 91
            }
          }
        }
      },
      {
        "platform": "instagram",
        "handle": "nasa",
        "ok": true,
        "check": {
          "platform": "instagram",
          "handle": "nasa",
          "checked_at": "2026-08-30T09:14:02.113Z",
          "exists": true,
          "evidence": "catalog",
          "identity": {
            "id": "528817151",
            "handle": "nasa",
            "name": "NASA",
            "avatar_url": "https://scontent.cdninstagram.com/v/t51.2885-19/...",
            "url": "https://www.instagram.com/nasa/",
            "object": "account"
          },
          "audience": {
            "count": 104443318,
            "metric": "followers",
            "precision": "exact"
          },
          "flags": {
            "verified": true,
            "private": false,
            "nsfw": false
          },
          "created_at": null,
          "catalog": {
            "state": "present",
            "status": "active",
            "tier": "a",
            "category": "science",
            "language": "en",
            "country": null,
            "last_seen": "2026-08-30T04:02:11.000Z",
            "data_age_s": 18711,
            "directory_url": "/best-instagram-accounts/nasa",
            "metrics": {
              "engagement_rate": 0.4213,
              "avg_likes": 402118,
              "avg_comments": 2904,
              "posts_analyzed": 12,
              "citation_score": 91
            }
          }
        }
      }
    ]
  },
  "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

POST /accounts/check 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.

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/accounts-bulk