Enrich a company from its website domain

The enrichment lookup keyed on the identifier a caller actually holds. Nobody arrives with a LinkedIn slug; everybody arrives with the domain off an email address or a signup form. Returns firmographics, page-activity signals, role contact addresses, decision-maker counts and whatever follower and headcount observations exist, with the measured coverage of every column alongside so a null is readable as absent rather than as zero.

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/domains/adcash.com" \
  -H "Authorization: Bearer psk_live_..."

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

Domain

adcash.com

Companies

1 items

Coverage company columns measured at

2026-08-31

Coverage company columns rows

93,677

Coverage companies returned

1

{
  "data": {
    "domain": "adcash.com",
    "companies": [
      {
        "id": "adcash",
        "name": "Adcash",
        "website_domain": "adcash.com",
        "linkedin_url": "https://www.linkedin.com/company/adcash",
        "firmographics": {
          "industry": "Advertising Services",
          "org_type": "Privately Held",
          "size_band": "51-200 employees",
          "staff_count": 122,
          "founded_year": 2007,
          "followers": 10095
        },
        "hq": {
          "location": "Tallinn, Harju County",
          "country_code": "EE",
          "country_text": "Harju County"
        },
        "activity": {
          "last_post_at": "2026-08-24T12:18:22.834Z",
          "posts_sampled": 10,
          "avg_reactions": 7,
          "avg_comments": 1,
          "posted_within_90d": true
        },
        "trend": {
          "observations": 2,
          "window_days": 4.7,
          "followers_first": 10070,
          "followers_last": 10095,
          "followers_delta": 25,
          "staff_first": 123,
          "staff_last": 122,
          "staff_delta": -1
        },
        "contacts": {
          "role_emails": [],
          "role_email_count": 0,
          "personal_email_count": 0,
          "phone_count": 0,
          "mx_ok": null
        },
        "people": {
          "named": 22,
          "decision_makers": 0,
          "with_title_or_seniority": 19
        },
        "enrichment": {
          "status": "no_contacts",
          "last_enriched": "2026-08-22T21:29:27.450Z",
          "last_seen": "2026-08-27T11:58:17.507Z"
        }
      }
    ],
    "coverage": {
      "company_columns": {
        "measured_at": "2026-08-31",
        "rows": 93677
      },
      "companies_returned": 1
    }
  },
  "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.

• 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/leads/linkedin/segmentsFirmographic market sizing with real counts
• 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-domain