One company with socials, contacts and decision makers

The full record for a single company, including the people we can name there with their titles, seniority and how we know about them. Same shape as a list row plus the people array, so a detail view can never disagree with the list it came from.

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/companies/modash" \
  -H "Authorization: Bearer psk_live_..."

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

Company id

modash

Company name

Modash

Company industry

Software Development

Company size band

51-200 employees

Company followers

31,146

Company hq location

Tallinn, Estonia

Company hq country code

EE

Company contact best email

hello@modash.io

Company contact best email is role

yes

Company contact email count

3

Company socials

1 items

Company people

1 items

Company decision makers

2

Company readiness

95

{
  "data": {
    "company": {
      "id": "modash",
      "name": "Modash",
      "industry": "Software Development",
      "size_band": "51-200 employees",
      "followers": 31146,
      "hq": {
        "location": "Tallinn, Estonia",
        "country_code": "EE"
      },
      "contact": {
        "best_email": "hello@modash.io",
        "best_email_is_role": true,
        "email_count": 3
      },
      "socials": [
        {
          "platform": "x",
          "handle": "modash_io",
          "matched": true,
          "followers": 4820
        }
      ],
      "people": [
        {
          "name": "Avery Lindqvist",
          "title": "Co-Founder & CEO",
          "seniority": "founder",
          "seniority_label": "Founder",
          "relation": "employee",
          "source": "website",
          "li_slug": "averylindqvist",
          "decision_maker": true
        }
      ],
      "decision_makers": 2,
      "readiness": 95,
      "flags": []
    }
  },
  "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/domains/{domain}Enrich a company from its website domain
• GET/leads/linkedin/segmentsFirmographic market sizing with real counts
• GET/leads/linkedin/companiesLinkedIn company records, filterable
• 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-companies-get