Inbound graph edges

The accounts we know point AT this one. Paginated by peer id so the whole known set can be walked. The response states what the edges mean on that platform, and reports both the audience the platform reports and how many edges we actually hold - they are different numbers and must not be confused.

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/directory/x/elonmusk/followers" \
  -H "Authorization: Bearer psk_live_..."

const res = await fetch("https://crmsolid.com/data-api/v2/directory/x/elonmusk/followers", {
  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/directory/x/elonmusk/followers",
    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.

Target id

44196397

Target handle

elonmusk

Target name

Elon Musk

Target reported metric

221,384,902

Target known edges

37,812

Target known edges capped

no

Graph direction

followers

Graph kind

follows

Graph note

Real follow edges, but only among accounts already in the catalog.

Edges

1 items

{
  "data": {
    "target": {
      "id": "44196397",
      "handle": "elonmusk",
      "name": "Elon Musk",
      "reported_metric": 221384902,
      "known_edges": 37812,
      "known_edges_capped": false
    },
    "graph": {
      "direction": "followers",
      "kind": "follows",
      "note": "Real follow edges, but only among accounts already in the catalog."
    },
    "edges": [
      {
        "peer_id": "813286",
        "edge_type": "follows",
        "weight": 1,
        "edge_seen": "2026-08-19T04:31:52+00:00",
        "username": "BarackObama",
        "name": "Barack Obama",
        "followers_count": 131402119,
        "language": "en",
        "country": "US"
      }
    ]
  },
  "meta": {
    "request_id": "req_9f2c41a8b3d5",
    "generated_at": "2026-08-23T09:14:02.317Z",
    "took_ms": 42,
    "page": {
      "limit": 50,
      "next_cursor": "eyJrIjoiMTczNDU2IiwiZCI6ImEifQ",
      "count": 50
    }
  }
}

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

• 404NotFoundnot_found

  The addressed resource does not exist.

• 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/directoryCatalog capability map
• GET/directory/{platform}List and filter a catalog
• GET/directory/{platform}/{id}One account or channel
• GET/directory/{platform}/{id}/growthDaily audience history
• GET/directory/{platform}/{id}/followingOutbound graph edges
• POST/directory/{platform}/bulkResolve up to 100 records at once
• GET/directory/{platform}/facetsDistribution of the catalog
• GET/directory/searchSearch every platform at once

Reference path: /data-api/reference/directory-followers