LinkedIn Company Details Scraper

LinkedIn Company Details Scraper is an Apify Actor for turning LinkedIn company URLs or slugs into one record per company. It accepts a list of company pages, and each returned dataset item represents one LinkedIn company with firmographic fields such as company name, LinkedIn URL, company ID, handle, slogan, description, industry, company size, employee count, followers, founded year, headquarters, location, website, type, specialties, logo, cover image, funding, similar pages, sample employees, recent posts, source, and scrapedAt.

This Actor is usable through Apify MCP and is designed for cookieless company enrichment from public LinkedIn company pages.

Best fit and connected workflows

Use this Actor when you already have a company URL or slug and want structured LinkedIn firmographics for enrichment, research, or downstream automation.

It fits well in workflows such as:

• company discovery first, then firmographic enrichment
• CRM or lead list cleanup from known LinkedIn company links
• market research pipelines that compare company size, industry, and funding
• AI agent flows that need a single normalized record per company page

If you need to discover LinkedIn companies before enrichment, start with LinkedIn Company Search Scraper and pass the verified public URL or slug into this Actor.

Practical scenario

Maya is building a sales research sheet for a list of LinkedIn company pages. She starts with a company slug like stripe, runs the Actor, and receives fields such as companyName, industry, companySize, employeeCount, headquarters, website, funding, and recentPosts.

She uses the employeeCount and funding fields to decide which accounts need a deeper review, then sends the company URL and summary into her next enrichment step for outreach preparation.

Input

The Actor accepts LinkedIn company URLs or bare slugs. One record in the output dataset corresponds to one LinkedIn company page requested in companyUrls, after de-duplication and maxCompanies capping.

Input fields

Field	Type	Required	Description
companyUrls	string[]	Yes	List of LinkedIn company pages to scrape. Each item can be a full company URL such as https://www.linkedin.com/company/shopify or a bare company slug such as shopify.
includePosts	boolean	No	When true, each company record includes a recentPosts array with post URL, date, and text from the company page.
maxCompanies	integer	No	Hard ceiling for this run after de-duplication. Accepts 1 to 1000. Default is 100.
preferredProvider	string	No	Backend order: auto, scrapecreators, or sociavault. Default is auto.

Focused input example

{
  "companyUrls": [
    "https://www.linkedin.com/company/microsoft",
    "stripe"
  ],
  "includePosts": false,
  "maxCompanies": 25,
  "preferredProvider": "auto"
}

Output

The Actor writes one dataset record per scraped company. The live dataset contract includes these fields.

Output fields

Field	Type	Description
companyName	string	Company display name
linkedinUrl	string	Canonical LinkedIn company URL
companyId	string	LinkedIn numeric company ID
handle	string	LinkedIn slug
slogan	string	Tagline shown on the page
description	string	Company "About" text
industry	string	Industry category
companySize	string	Size band shown by LinkedIn
employeeCount	integer	Employee count listed on LinkedIn
followers	integer	LinkedIn follower count
founded	integer	Founded year
headquarters	string	HQ string
location	object	Structured location object
website	string	Company website
type	string	Company type
specialties	array	Specialty tags
logo	string	Logo URL
coverImage	string	Cover image URL
funding	object	Funding information object
similarPages	array	Related company pages
sampleEmployees	array	Example employee entries
recentPosts	array	Recent company posts when requested
source	string	Provider source used for the record
scrapedAt	string	ISO timestamp when the record was scraped

Illustrative output record

{
  "companyName": "Shopify",
  "linkedinUrl": "https://www.linkedin.com/company/shopify",
  "companyId": "7890",
  "handle": "shopify",
  "industry": "Software Development",
  "companySize": "10,001+ employees",
  "employeeCount": 29084,
  "followers": 1092578,
  "founded": 2006,
  "headquarters": "Ottawa, ON",
  "website": "https://www.shopify.com",
  "type": "Public Company",
  "specialties": ["ecommerce", "API", "POS", "Payments"],
  "source": "scrapecreators",
  "scrapedAt": "2026-06-27T00:00:00.000Z"
}

How it works

This Actor uses two backend providers and returns the same normalized fields regardless of provider order:

• auto tries ScrapeCreators first, then falls back to SociaVault
• scrapecreators tries ScrapeCreators first
• sociavault tries SociaVault first, then ScrapeCreators

The live contract shows two environment variables used by the build: SCRAPECREATORS_API_KEY and SOCIAVAULT_API_KEY.

The dataset schema is flat and agent-friendly, and the overview view surfaces company firmographics such as company name, industry, size, employee count, followers, founded year, headquarters, website, type, LinkedIn URL, and source.

The output contract also exposes a run summary record in key-value storage for counters such as scraped, not found, errors, and cost.

Pricing

This Actor uses Pay per event pricing plus Apify platform usage. The primary charged event is Company scraped, and the platform also charges an actor start event.

A simple example in words: if a execution successfully scrapes twenty companies, the execution includes twenty company-scraped events plus the actor start event, and Apify platform usage is charged separately according to the live Pricing tab.

For current pricing details, open the live Pricing tab on the Actor page. That view is the source of truth for the event price and any platform usage charges.

Use with AI agents (MCP)

This Actor is available through Apify MCP as a tool for company-page enrichment from LinkedIn company URLs or slugs.

Tool description: Given a LinkedIn company page URL or slug, return one normalized company record with firmographic fields and optional recent posts, suitable for agent workflows that need structured company data.

Exact Actor identity: khadinakbar/linkedin-company-details-scraper

Scrape these LinkedIn company pages and return one structured record per company. Use the company URL or slug as input. Include recent posts only if they are useful for this task. Summarize the output by company name, industry, size, headquarters, website, and source.

Output interpretation and provenance:
Each dataset item corresponds to one LinkedIn company page. The source field identifies which backend provided the normalized record, and scrapedAt records when the item was created. When includePosts is enabled, the recentPosts array adds public post data published by the company page.

Scope, pagination, and cost guidance:
The companyUrls array is the work queue. maxCompanies caps the number of companies processed after de-duplication. Because pricing is pay per event, the number of returned company records directly relates to the number of company-scraped events.

API example

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
  token: process.env.APIFY_TOKEN,
});

const input = {
  companyUrls: [
    'https://www.linkedin.com/company/microsoft',
    'stripe'
  ],
  includePosts: false,
  maxCompanies: 10,
  preferredProvider: 'auto',
};

const run = await client.actor('khadinakbar/linkedin-company-details-scraper').call(input);

const { items } = await client.dataset(run.defaultDatasetId).listItems();

console.log('Scraped companies:', items);

Best results and outcome guidance

Provide canonical LinkedIn company URLs or bare company slugs in companyUrls. Use includePosts only when recent company posts are part of your workflow, since it adds more fields to each record. Set maxCompanies to the smallest useful batch size for your task, and leave preferredProvider on auto unless you have a specific reason to try one backend first.

For agent workflows, the cleanest pattern is:

1. discover company pages with a search Actor,
2. pass the verified company URL or slug here,
3. read the dataset record,
4. branch into CRM, research, or reporting actions based on the returned firmographics.

Design note

I found that the live dataset contract is intentionally flat: the output view highlights a small set of firmographic fields, while the full schema keeps additional company details in a single record per company. That makes the Actor straightforward to use in both human review and agent pipelines.

FAQ

When should I use this Actor instead of a search Actor?

Use this Actor when you already have a LinkedIn company URL or slug. If you need to discover company pages first, use LinkedIn Company Search Scraper and then pass the verified result into this Actor.

Can I include recent company posts in the same run?

Yes. Set includePosts to true and the returned company record can include a recentPosts array with post URL, date, and text.

What is the meaning of one output record?

One output record represents one LinkedIn company page that was requested and scraped successfully. The record is the normalized company profile for that page.

How do I choose the provider order?

Use auto for the default provider order. Choose scrapecreators or sociavault only when you want to set which backend is tried first.

What fields are most useful for routing work downstream?

Common routing fields include industry, companySize, employeeCount, followers, founded, headquarters, website, type, source, and recentPosts when enabled.

Responsible use

Use this Actor only for public LinkedIn company pages and in line with applicable laws and LinkedIn's terms. Keep input scoped to company URLs or slugs, and use the returned firmographic data responsibly in your own workflows, systems, and access controls.

Related Actors

• LinkedIn Company Search Scraper: discover company pages first, then pass the verified public URL or slug into this Actor for company details enrichment.