How to enrich a lead from a LinkedIn company page

The endpoint

Make the call

Put your key in FASTFETCHZ_KEY. The target below is a real one — it works as written.

curl "https://api.fastfetchz.com/v1/linkedin/company?target=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fstripe" \
  -H "X-API-Key: $FASTFETCHZ_KEY"

What comes back

Trimmed to the fields that matter. The full payload carries more.

{
  "success": true,
  "service": { "platform": "LinkedIn", "name": "Company" },
  "credits_charged": 1,
  "data": {
    "company": {
      "name": "Stripe",
      "universal_name": "stripe",
      "linkedin_url": "https://www.linkedin.com/company/stripe",
      "website": "https://stripe.com",
      "industry": "Software Development",
      "description": "Stripe is a financial infrastructure platform for businesses.",
      "employee_count": 9241,
      "employee_count_range": "5001-10000",
      "follower_count": 1284310,
      "founded_year": 2010,
      "company_type": "Privately Held",
      "headquarters": {
        "city": "South San Francisco",
        "region": "California",
        "country": "US"
      },
      "specialties": ["payments", "billing", "fraud prevention"],
      "funding": {
        "last_round_type": "Series I",
        "last_round_date": "2023-03-14",
        "last_round_amount_usd": 6500000000,
        "rounds_count": 20
      },
      "logo_url": "https://media.example.com/company-logo/stripe.png"
    }
  }
}

What it costs

Wire it into the CRM, not into a spreadsheet

The useful shape is a hook: a lead is created with a LinkedIn URL, you call this endpoint, you write employee_count, industry, headquarters.country and funding.last_round_type onto the record, and your routing rules fire on real values instead of blanks. employee_count_range is the better field for segment rules because it is stable — the exact count moves every week.

Enrich once and store it. Company facts change on a quarterly timescale at most, so re-enriching an existing record daily is money spent to learn nothing. Re-run stale records on a schedule — quarterly is generous — rather than on every page view.

People need the other endpoint

For a named contact rather than the company, use the profile endpoint with the person's LinkedIn URL. It is also one call, and it returns headline, current role, location and work history — enough to tell a decision maker from an intern before anyone writes an email.

curl "https://api.fastfetchz.com/v1/linkedin/profile?target=https://www.linkedin.com/in/patrickcollison" \
  -H "X-API-Key: $FASTFETCHZ_KEY"

What you cannot get

No email addresses and no phone numbers. LinkedIn does not publish contact details on public pages, so nothing here can return them — an enrichment tool that does is guessing from a name-and-domain pattern, and you should treat those addresses as guesses.

Funding is present only for companies that have raised and where LinkedIn shows it; expect it to be absent for most private businesses. Headcount is LinkedIn's own figure, which counts people who list the company on their profile — it runs low for firms with a mostly offline workforce and high for firms whose alumni never updated their profile. Use it as a band, not a payroll number.

Company pages that do not exist, or that have been closed, return a 404. That is a failed call, and failed calls are never charged, so running this over a messy lead list only costs you the URLs that resolved.

Endpoints you will probably want next