LinkedIn Company Enrichment Scraper

Turn a LinkedIn company URL, company name, or website domain into a structured firmographic record with industry, size, followers, headquarters, locations, specialties, and website details.

What you get

Provide one or many companies and receive exactly one terminal record per accepted input query. terminal_status is one of resolved, no_match, fetch_failed, or duplicate_slug; resolved and duplicate rows also carry the company fields below. LinkedIn URLs and slugs are the most precise inputs; names and domains are useful when you are enriching an existing account list.

Output fields

Field	Description
query_id / query_index	Stable input identity and order
terminal_status	resolved, no_match, fetch_failed, or duplicate_slug
failure_kind	Retry reason on fetch_failed rows only
duplicate_of_query_id	Earlier input owning the same slug on duplicate_slug rows
name	Company name
slug / company_id	LinkedIn identifiers
linkedin_url	Canonical company-page URL
tagline / description	Public positioning and About text
industry	LinkedIn industry label
company_size	Published employee-size band
employee_count_min / employee_count_max	Parsed size-band bounds
employees_on_linkedin	Members who publicly list the company as employer
follower_count	Company-page followers
founded_year / company_type	Founding year and organization type
specialties	Self-declared specialties
website / website_domain	Company website details
headquarters	Formatted headquarters address
hq_street, hq_city, hq_region, hq_postal_code, hq_country	Headquarters components
locations / locations_count	Published office locations
logo_url / banner_image_url	Public brand images
recent_post_count / latest_post_at	Recent public activity signals
source_query / scraped_at	Input and collection timestamp

Example output

{
  "name": "HashiCorp",
  "slug": "hashicorp",
  "linkedin_url": "https://www.linkedin.com/company/hashicorp/",
  "industry": "Software Development",
  "company_size": "1001-5000 employees",
  "employee_count_min": 1001,
  "employee_count_max": 5000,
  "follower_count": 250000,
  "founded_year": 2012,
  "company_type": "Public Company",
  "website": "https://www.hashicorp.com",
  "headquarters": "San Francisco, California, United States",
  "source_query": "hashicorp.com"
}

Input parameters

Parameter	Required	Description
companies	Yes	LinkedIn company URLs, slugs, company names, or website domains.
queryRecords	API alternative	Bound objects with queryId, companyName, optional countryCode, and optional companyKeys. Do not combine with companies.
maxResults	No	Maximum input queries accepted. The run fails instead of truncating if this is smaller than the input. Default 10.
concurrency	No	Companies processed at the same time. Default 10.
proxyConfiguration	No	Connection settings. Keep the preconfigured default for most runs.

Use cases

• Sales operations: Fill missing firmographic fields in CRM account records.
• Market research: Compare industries, size bands, locations, and specialties across company cohorts.
• Recruiting intelligence: Segment target employers by size, industry, and geography.
• Data teams: Normalize mixed company names, domains, and LinkedIn URLs into one schema.

Limitations

• Website-domain resolution is correct for roughly three in four tested companies; use LinkedIn URLs or slugs when precision matters.
• Common company names can resolve to a larger organization with the same name.
• Optional fields such as specialties, founded year, and employee counts are absent when the company has not published them.
• Only public company-page data is supported. Private and member-only information is out of scope.

Compared to alternatives

• vs. harvestapi company enrichment: This actor accepts a mixed list of LinkedIn URLs, names, and domains and returns a compact firmographic record intended for account enrichment.
• vs. LinkedIn Company Employees actors: This actor returns company-level facts, not employee profiles. Pair the two when you need both account and people data.

FAQ

Which input is most reliable? A full LinkedIn company URL or exact slug. Names and domains are best-effort discovery inputs.

Does it require a LinkedIn login? No. It collects fields published on public company pages.

Can I process a mixed input list? Yes. URLs, slugs, names, and domains can appear in the same companies list.

Last verified: 2026-07

More company-data actors at thirdwatch.dev.