# LinkedIn Company Pages with Funding & Affiliates (`nimbryxo-studio/linkedin-company-pages-with-funding-and-affiliates`) Actor

Pull full LinkedIn company pages, including industry, headcount, headquarters, specialties, and Crunchbase-sourced funding, with optional affiliated-company and showcase-page records for each input company.

- **URL**: https://apify.com/nimbryxo-studio/linkedin-company-pages-with-funding-and-affiliates.md
- **Developed by:** [Nimbryxo-studio](https://apify.com/nimbryxo-studio) (community)
- **Categories:** Lead generation, Social media, Automation
- **Security:** Limited permissions
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## LinkedIn Company Pages with Funding & Affiliates

Give this actor a list of LinkedIn company pages and get back the full "About" page for each one — industry, headcount, headquarters, specialties, logo, and (when LinkedIn surfaces it) Crunchbase-sourced funding history — plus the option to also pull every affiliated company and showcase page linked from that company's profile.

### What this actor does

- Resolves full LinkedIn company URLs, `/about` pages, or bare slugs into one structured record per company
- Adds Crunchbase-style funding data (total raised, round count, last round) when `includeFundingDetails` is on
- Can walk out from each input company to also emit its affiliated companies and/or showcase pages as separate records
- Returns both the exact employee count and LinkedIn's bucketed employee-count range when either is available
- Only includes a field when LinkedIn actually published that data — no null or placeholder values ever appear

### Output per company

- `companyId`, `name`, `companyUrl`, `slug`, `companyPageUrl` — identifiers and canonical links
- `websiteUrl`, `industry`, `industries`, `companyType`, `stockTicker` — classification fields
- `foundedYear`, `headquarters`, `headquartersAddress`, `locations`, `parentCompany` — location and corporate structure
- `description`, `tagline`, `specialties` — the company's own "About" copy
- `employeeCount`, `employeeCountRange`, `followersCount`, `jobsCount` — size and reach signals
- `logoUrl`, `coverImageUrl` — page imagery
- `phone` — published contact phone number, when listed
- `verifiedStatus` — whether LinkedIn shows the company as verified
- `awards`, `acquiredBy` — recognitions and acquisition history, when disclosed
- `affiliatedCompanies`, `showcasePages` — structured lists of related company/showcase pages referenced on this company's profile
- `crunchbaseUrl`, `crunchbaseFundingUrl`, `fundingTotalUsd`, `fundingRoundsCount`, `lastFundingRound` — funding details (only when `includeFundingDetails` is enabled and LinkedIn has Crunchbase data for the company)
- `inputUrl` — the URL or slug you originally supplied
- `relation`, `parentSlug` — present only on affiliate/showcase records, marking the record as `affiliate` or `showcase` and naming the company it came from
- `scrapedAt` — ISO 8601 UTC timestamp of when the record was scraped

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `companyUrls` | array | – | **Required.** LinkedIn company URLs or bare slugs, e.g. `https://www.linkedin.com/company/apple/` or `apple` |
| `cookie` | string | – | **Required.** LinkedIn session cookie — either the `li_at` value or a full exported cookies JSON array |
| `includeAffiliates` | boolean | `false` | Also emit one record per affiliated company referenced by each input company |
| `includeShowcases` | boolean | `false` | Also emit one record per showcase page referenced by each input company |
| `includeFundingDetails` | boolean | `true` | Add Crunchbase-sourced funding fields when LinkedIn has them for the company |
| `language` | string | `en` | Language used for the request locale |
| `proxyConfiguration` | object | – | Optional Apify proxy configuration |

#### Example: basic company lookup

```json
{
    "companyUrls": ["https://www.linkedin.com/company/microsoft/", "openai"],
    "cookie": "AQEDATVc5uM..."
}
```

#### Example: company plus its affiliates and showcase pages

```json
{
    "companyUrls": ["https://www.linkedin.com/company/microsoft/"],
    "cookie": "AQEDATVc5uM...",
    "includeAffiliates": true,
    "includeShowcases": true
}
```

#### Example: skip funding lookups for a faster run

```json
{
    "companyUrls": ["apple", "google", "amazon"],
    "cookie": "AQEDATVc5uM...",
    "includeFundingDetails": false
}
```

### Use cases

- **Sales intelligence** — enrich a target-account list with headcount, HQ, industry, and funding stage before outreach
- **Investor and M\&A research** — pull funding totals and last-round details across a portfolio or watchlist of companies
- **Corporate structure mapping** — use `includeAffiliates` and `includeShowcases` to surface a parent company's full family of LinkedIn pages
- **Competitive benchmarking** — compare headcount, follower growth, and specialties across a set of competitors
- **Recruiting and market research** — gather company-level context (industry, size, locations) for a list of employers

### FAQ

**Why is a LinkedIn cookie required?** Full company-page data, including funding and affiliate links, is only exposed to a signed-in LinkedIn session, so a valid session cookie is mandatory for every run.

**Does this work for private as well as public companies?** Yes — any company with a LinkedIn page returns the same data a logged-in user would see when visiting that page.

**Why do some companies have no funding fields?** Funding fields only appear when `includeFundingDetails` is on and LinkedIn has linked Crunchbase funding data to that company; many companies, especially non-startups, have none to show.

**What's the difference between `employeeCount` and `employeeCountRange`?** `employeeCount` is LinkedIn's exact reported staff figure; `employeeCountRange` is the bucketed range (e.g. `10001-50000`) LinkedIn uses in search filters. Some companies only expose the range.

**What do `affiliatedCompanies` and `showcasePages` return when the toggles are off?** With `includeAffiliates`/`includeShowcases` off, the company's own record still lists its affiliated companies and showcase pages as structured data — turning the toggles on additionally fetches a full separate record for each of those pages.

**Why might a field like `phone` or `stockTicker` be missing?** Those fields only exist for companies that have published that information on their LinkedIn page; most companies don't list a phone number or a ticker, so the field is simply omitted.

**How long does my cookie stay valid?** A LinkedIn `li_at` session cookie typically lasts several weeks to months; once it expires, log back into LinkedIn and copy the new value.

**Is this affiliated with LinkedIn?** No. This is an independent actor that reads data through an authenticated LinkedIn session you provide; it is not endorsed by or affiliated with LinkedIn Corporation.

# Actor input Schema

## `companyUrls` (type: `array`):

LinkedIn company page URLs or slugs. Accepts: https://www.linkedin.com/company/apple/, https://www.linkedin.com/company/apple/about/, or just the slug: apple

## `cookie` (type: `string`):

Your LinkedIn session cookie. Accepts either: (1) the li_at value from browser DevTools Application Cookies, or (2) full cookies JSON array exported from an extension like EditThisCookie.

## `includeAffiliates` (type: `boolean`):

Also emit one record per affiliated company referenced by each input company.

## `includeShowcases` (type: `boolean`):

Also emit one record per LinkedIn showcase page referenced by each input company.

## `includeFundingDetails` (type: `boolean`):

Extract Crunchbase funding info (total raised, last round, lead investors) from the LinkedIn page when available. Adds small fetch time.

## `language` (type: `string`):

Language code used for Accept-Language and the LinkedIn lang cookie.

## `proxyConfiguration` (type: `object`):

Optional Apify proxy configuration. Residential proxy recommended for best results.

## Actor input object example

```json
{
  "companyUrls": [
    "https://www.linkedin.com/company/hubspot/"
  ],
  "includeAffiliates": false,
  "includeShowcases": false,
  "includeFundingDetails": true,
  "language": "en"
}
```

# Actor output Schema

## `companies` (type: `string`):

Dataset containing detailed information for each scraped LinkedIn company.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "companyUrls": [
        "https://www.linkedin.com/company/hubspot/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("nimbryxo-studio/linkedin-company-pages-with-funding-and-affiliates").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "companyUrls": ["https://www.linkedin.com/company/hubspot/"] }

# Run the Actor and wait for it to finish
run = client.actor("nimbryxo-studio/linkedin-company-pages-with-funding-and-affiliates").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "companyUrls": [
    "https://www.linkedin.com/company/hubspot/"
  ]
}' |
apify call nimbryxo-studio/linkedin-company-pages-with-funding-and-affiliates --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/linkedin-company-pages-with-funding-and-affiliates"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/KqeIxDtYhtcuiYlB2/builds/L4G7ZYl7jJxEwCnmN/openapi.json