Firmographic market sizing with real counts

How many companies exist in a slice of the catalog, and how reachable that slice is. Group by industry, country, size band or founding decade, filter on any of the others, and get true counts rather than a facet list with no numbers behind it. Every row is an aggregate over companies, so nothing here identifies a person and the surface is aggregate by construction rather than by a filter somebody has to remember.

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 leads:read scope (Leads): LinkedIn company and contact data, and X follower-graph exports.

curl "https://crmsolid.com/data-api/v2/leads/linkedin/segments" \
  -H "Authorization: Bearer psk_live_..."

const res = await fetch("https://crmsolid.com/data-api/v2/leads/linkedin/segments", {
  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/leads/linkedin/segments",
    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.

Dimension

country

Filters industry

Software Development

Buckets

3 items

Totals companies

7,776

Totals with domain

7,518

Totals crawl succeeded

4,088

Coverage measured at

2026-08-31

Coverage rows

93,677

{
  "data": {
    "dimension": "country",
    "filters": {
      "industry": "Software Development"
    },
    "buckets": [
      {
        "bucket": "US",
        "companies": 3094,
        "with_domain": 3041,
        "crawl_succeeded": 1580,
        "with_staff_count": 2975,
        "median_staff": 110,
        "active_last_90d": 2247
      },
      {
        "bucket": "(unknown)",
        "companies": 1422,
        "with_domain": 1315,
        "crawl_succeeded": 680,
        "with_staff_count": 1213,
        "median_staff": 42,
        "active_last_90d": 846
      },
      {
        "bucket": "IN",
        "companies": 512,
        "with_domain": 493,
        "crawl_succeeded": 294,
        "with_staff_count": 474,
        "median_staff": 58,
        "active_last_90d": 304
      }
    ],
    "totals": {
      "companies": 7776,
      "with_domain": 7518,
      "crawl_succeeded": 4088
    },
    "coverage": {
      "measured_at": "2026-08-31",
      "rows": 93677
    }
  },
  "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/leads/linkedin/domains/{domain}Enrich a company from its website domain
• GET/leads/linkedin/companiesLinkedIn company records, filterable
• GET/leads/linkedin/companies/{id}One company with socials, contacts and decision makers
• GET/leads/linkedin/peopleNamed people and decision makers
• GET/leads/x/followersFollower-graph export for one X account

Reference path: /data-api/reference/leads-linkedin-segments