# LinkedIn Company Search - Find Companies, No Cookies (`andrew_babo/linkedin-company-search`) Actor

Find LinkedIn companies by keyword, industry and location without a login, then pull their full public profile: website, phone, employee count, followers, HQ, specialties, industries and funding. HTTP-first engine. Export CSV, Excel, JSON.

- **URL**: https://apify.com/andrew\_babo/linkedin-company-search.md
- **Developed by:** [Andrew Babo](https://apify.com/andrew_babo) (community)
- **Categories:** Lead generation, Business, SEO tools
- **Stats:** 449 total users, 84 monthly users, 98.8% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## 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 Search — Find Companies, No Cookies

Discover LinkedIn company pages matching a keyword, location or industry, then enrich them into full company records. **No login, no account, no `li_at` cookie.**

### How discovery works without a login

LinkedIn's own company search requires an account, so this actor rebuilds the result set from public sources:

1. **Search engine results** for `site:linkedin.com/company` with your keyword, location and industry
2. **LinkedIn job postings** — every job card carries its hiring company's page
3. **LinkedIn's public company sitemap** (optional, `useSitemap`)

Candidates are de-duplicated by company slug before enrichment.

### Measured head-to-head (real runs, not estimates)

Query `fintech` in Singapore, full mode, 15 companies, cold cache:

| | This actor | harvestapi/linkedin-company-search |
|---|---|---|
| Time | 16.4 s | 5.4 s |
| Cost per 1,000 companies | **$0.35** | $4.07 |
| Field coverage | 100% on name, description, website, size, followers, type, industries, locations, HQ | same, minus HQ |
| Blocked requests | 0 | 0 |

About **11x cheaper**. Result relevance differs by design: this actor returns operating fintech companies (Airwallex, Stripe, Binance, Coinhako, StraitsX), while pure name matching tends to surface associations and events with "Fintech" in the title.

### Input

```json
{
  "search": "logistics",
  "locations": ["Singapore"],
  "industries": ["Transportation"],
  "mode": "full",
  "maxItems": 500
}
```

- **`short`** — returns the discovered company list (name, LinkedIn URL, snippet) with no extra requests. Cheapest way to build a target list.
- **`full`** — scrapes each company page for the complete record.

### Full record fields

`name`, `universalName`, `linkedinUrl`, `logo`, `tagline`, `description`, `website`, `phone`, `industries`, `specialities`, `companyType`, `employeeCount`, `employeeCountRange`, `followerCount`, `foundedOn`, `headquarter`, `locations`, `fundingData`, `similarOrganizations`, `jobSearchUrl`.

Every enriched company is cached for 30 days, so repeated or overlapping searches cost far less on the second run.

### Honest limits without a cookie

Discovery is a reconstruction of LinkedIn's index, not a copy of it: recall depends on what search engines, job postings and the sitemap expose. Filters are applied to the query, so results are broad rather than exactly matching LinkedIn's internal filter semantics. Employee lists and contact emails are not available to logged-out visitors.

### Proxy

Use Apify **residential** proxies. Sessions are paced and warmed up, and any IP returning a `999` is rotated out.

### Output

CSV, Excel, JSON, JSONL or API. Run statistics — candidates discovered, companies scraped, blocked requests, per-field coverage — are in the key-value store under `STATS`.

### Full pagination and LinkedIn filters (new)

The search now walks every source page by page until your `maxItems` is met or the sources
are drained — asking for 50 returns 50. When it cannot, `STATS.stopReason` says why:
`reachedMaxItems`, `exhausted`, `blocked` or `timeout`.

New filters for pipelines that split work by country × industry × size:

- `industryIds` — LinkedIn industry codes (e.g. `96` IT Services, `133` Transportation & Logistics,
  `42` Financial Services). They widen discovery and are applied to the scraped profile.
- `companySize` — LinkedIn size codes (`A` 1, `B` 2-10, `C` 11-50, `D` 51-200, `E` 201-500,
  `F` 501-1000, `G` 1001-5000, `H` 5001-10000, `I` 10001+) **or** plain ranges
  (`11-50`, `1001-5000`, `10001+`). Both spellings behave identically.
  Companies whose headcount LinkedIn does not publish are kept; set
  `strictCompanySize: true` to drop them. Unrecognised buckets are logged and ignored
  instead of emptying the result.

When filters remove every candidate the run still ends **SUCCEEDED** with
`stopReason: filteredOut`, plus `candidates`, `rejectedBySize` and `rejectedByIndustry`
in `STATS` so a pipeline can tell "nothing found" from "everything filtered out".

Measured filter runs (Singapore software, 20 requested, build 0.1.10):
`companySize: ["C","D"]` → 16 companies, every headcount inside 11-200, 47s, $1.31/1,000;
`industryIds: ["4"]` → 10 companies, all `Software Development`;
both together → 1 company; impossible combination → SUCCEEDED, 0 rows, `filteredOut`.
Unfiltered 50-company run is unchanged: 50/50, `website` 100%, `employeeCount` 100%, $0.29/1,000.

Measured run (Singapore logistics, 50 requested): 50 returned, `website` 98%,
`employeeCount` 100%, 0 blocked, ≈ $0.49 per 1,000 companies.

`foundedOn` is `{ year, month, day }` and `employeeCountRange` is `{ start, end }`,
matching harvestapi. `includeRunSummary` is off by default.

**Phone:** logged-out LinkedIn company pages carry no phone number (verified, including the
`/about` tab), so this field stays empty unless you supply `liAtCookie`.

### For AI agents (MCP-ready)

This actor is built to be called by AI agents. It works out of the box with the
[Apify MCP Server](https://mcp.apify.com) — add it to Claude Desktop, Cursor or any MCP
client: the agent can build company lists on its own.

```json
{
  "mcpServers": {
    "linkedin-company-search": {
      "url": "https://mcp.apify.com/?actors=andrew_babo/linkedin-company-search",
      "headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }
    }
  }
}
```

#### Agent skill (paste into your agent's instructions)

```text
Use the "linkedin-company-search" tool to DISCOVER companies matching a
keyword, industry, location or headcount band and return their public
LinkedIn profile data — for market maps, ICP lists and account research.
If you already have the company URLs, use "linkedin-company" instead.

HOW TO CALL
- { "search": "fintech", "locations": ["Singapore"], "maxItems": 50 }
- Narrow with "industries" / "industryIds" and "companySize"
  ("strictCompanySize": true to drop companies with unknown headcount).
- "maxItems" is the cost driver — request only what the user needs.
- "mode": "full" returns full profiles; use the lighter mode when only
  names and URLs are needed.

OUTPUT CONTRACT
- One row per company: name, LinkedIn URL, industry, size, location,
  website, description.
- Empty results are a valid answer — say no companies matched the filters
  and suggest loosening them; never fabricate company names.
```

# Actor input Schema

## `search` (type: `string`):

What the company does, e.g. "logistics" or "fintech".

## `locations` (type: `array`):

Countries or cities, e.g. \["Singapore", "Vietnam"]. Each one runs as its own query, which is also how you go past LinkedIn's 1,000-result ceiling.

## `industries` (type: `array`):

Extra industry words to narrow the search.

## `mode` (type: `string`):

Short = candidate list only, cheapest. Full = open each company page for the complete profile.

## `maxItems` (type: `integer`):

Max companies.

## `useSitemap` (type: `boolean`):

When the search returns fewer companies than requested, enumerate extra ones from LinkedIn's public sitemap. Broad, unfiltered — off by default.

## `bingApiKey` (type: `string`):

Optional. Supplying a key swaps the free search source for Bing, which gives deeper and more stable pagination on large runs.

## `scrapeAboutFallback` (type: `boolean`):

Use the About page fallback.

## `cacheTtlDays` (type: `integer`):

Reuse previously scraped profiles for this many days. 0 disables the cache.

## `speedMode` (type: `string`):

Speed mode.

## `maxConcurrency` (type: `integer`):

Max concurrency.

## `liAtCookie` (type: `string`):

Leave empty. Only needed for fields LinkedIn hides from logged-out visitors. Using your own account carries a restriction risk.

## `failOnZeroResults` (type: `boolean`):

Fail run when nothing is extracted.

## `includeRunSummary` (type: `boolean`):

Append one final summary item to the dataset. Off by default; the summary (including stopReason: reachedMaxItems / exhausted / blocked / timeout) is always in the key-value store under STATS.

## `maxRunTimeSecs` (type: `integer`):

Max run time (seconds).

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

Residential proxies are strongly recommended; datacenter IPs get blocked by LinkedIn within minutes.

## `industryIds` (type: `array`):

Filter by LinkedIn industry codes (e.g. 96 = IT Services, 133 = Transportation & Logistics, 42 = Financial Services). Applied to the scraped profile and also used to widen discovery.

## `companySize` (type: `array`):

Headcount filter. Accepts LinkedIn size codes (A=1, B=2-10, C=11-50, D=51-200, E=201-500, F=501-1000, G=1001-5000, H=5001-10000, I=10001+) or plain ranges like 51-200, 1001-5000, 10001+. Companies whose headcount LinkedIn does not publish are kept unless strictCompanySize is on.

## `strictCompanySize` (type: `boolean`):

Drop companies whose headcount LinkedIn does not publish instead of keeping them.

## Actor input object example

```json
{
  "search": "fintech",
  "locations": [],
  "industries": [],
  "mode": "full",
  "maxItems": 100,
  "useSitemap": false,
  "scrapeAboutFallback": true,
  "cacheTtlDays": 30,
  "speedMode": "turbo",
  "failOnZeroResults": true,
  "includeRunSummary": false,
  "maxRunTimeSecs": 3600,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  },
  "industryIds": [],
  "companySize": [],
  "strictCompanySize": false
}
```

# Actor output Schema

## `STATS` (type: `string`):

No description

# 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 = {
    "search": "fintech",
    "companySize": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("andrew_babo/linkedin-company-search").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 = {
    "search": "fintech",
    "companySize": [],
}

# Run the Actor and wait for it to finish
run = client.actor("andrew_babo/linkedin-company-search").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 '{
  "search": "fintech",
  "companySize": []
}' |
apify call andrew_babo/linkedin-company-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,andrew_babo/linkedin-company-search"
        }
    }
}
```

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/suxcA6cG3AEEyqqbl/builds/tPO9tvbBrpU3pJ6qg/openapi.json