# LinkedIn Company Employees — Staff List + Full Profiles ✅ (`b2bsearch/company-employees`) Actor

LinkedIn company employees by website domain: list the current employees of any company, then pick how much to return — the roster row at $1.50 per 1,000, the full profile at $3.20, or the profile plus emails and phones at $8 per 1,000 employees with a live contact. No cookies, no 2,500-row cap.

- **URL**: https://apify.com/b2bsearch/company-employees.md
- **Developed by:** [B2B Enrich Search](https://apify.com/b2bsearch) (community)
- **Categories:** Lead generation, Social media, AI
- **Stats:** 4 total users, 4 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 employee rows

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

> **Roster row $1.50 per 1,000, full profile $3.20, profile with emails and
> phones that work $8.** Each employee is delivered once: the store keeps
> historical snapshots of the same person and you are not charged for the
> copies.

List the current employees of any company by its site domain: names,
titles, seniority buckets, headlines, email flags and profile links, with
freshness stamps telling you when the profile and the position were last
re-confirmed.

This is a database lookup, not a live scrape: rosters return in seconds
from a database of 800M+ professional profiles. No cookies, no 2,500-row cap.

### Input

```json
{
  "companies": ["stripe.com", "figma.com"],
  "roles": ["cxo", "vp"],
  "profileDetail": "profile",
  "mustHave": [],
  "maxRows": 500
}
```

- `companies`: site domains, or numeric company ids from a previous run.
- `roles`: optional seniority filter (`cxo`, `founder`, `vp`, `director`,
  `manager`, `other`). Empty means the whole roster.
- `titleContains` / `titleExcludes`: filter on the raw job title before
  rows are counted or charged.
- `excludeLowSignal`: drop self-declared profiles (under 10 connections,
  no start date) before they are counted or charged.
- `profileDetail`, how much to return per employee:

  - `roster` (default, $1.50 per 1,000): the staff list;
  - `profile` ($3.20 per 1,000): plus the whole career card;
  - `contacts` ($8 per 1,000 employees with a working contact): plus
    email addresses and phone numbers.

  The richer tiers pull the profiles in the same run and cap a run at
  10,000 employees. An employee the profile store cannot answer for still
  ships, as a roster row at the roster price; the `_detail` column says
  which tier each row carries. If the profile store is unreachable for the
  whole run, one free `detail_unavailable` row says so.

With contacts, the $8 price applies only to a person with a contact that
reaches them today (a personal mailbox, an address on their current
employer's domain, or a phone the service labels direct). Everyone else
ships at the $3.20 profile price, old work addresses included. Phone labels
arrive with the next data rebuild; until then numbers ship unlabelled and
never earn the contacts price by themselves.

How often that is, measured on 30 September 2026 over 200 employed
professionals per country: the contacts price applied to 53% of people in
the US, 42% in India, 40% in France, 33% in the UK and 32% in Germany.
Everyone else shipped at the lower price.

### Only people who have what you need: `mustHave`

List what a person must have to be delivered: `email`, `personalEmail`,
`workEmail`, `currentWorkEmail`, `phone`, `github`, `twitter`, `facebook`.
People who do not qualify are skipped for free, and one `skipped_must_have`
row at the end says how many.

- `email`, `personalEmail`, `workEmail` work on every tier: the rows carry
  those flags already.
- `github`, `twitter`, `facebook` need the profile tier.
- `phone` and `currentWorkEmail` need the contacts tier.

A requirement the chosen tier cannot check is refused before the run
starts. Skipped people are free, so the walk reads ahead of what it
delivers, up to a ceiling; if it stops there, a `skipped_scan_limit` row
says so. Narrow the filters to reach further.

### What you get

| Group | Fields |
|---|---|
| Identity | full name, headline, `profileUrl`, slug |
| Role | current title, seniority bucket, in-role-since year |
| Location | city, `countryCode` |
| Email flags | `hasPersonalEmail`, `hasWorkEmail` |
| Signal | `lowSignal`: the self-declared "CEO at <famous brand>" pattern; such rows are never hydrated and ship at the roster price with a `_note` |
| Contacts (contacts tier) | `email`, `emailType`, `employerMatch`, `workEmails`, `personalEmails`, `emailCount`, `phone`, `phones` |
| Freshness | `personUpdatedAt`, `positionUpdatedAt`, `_freshness` |
| Status rows | free `unresolved_domain`, `skipped_row_budget`, `skipped_must_have`, `skipped_scan_limit`, `detail_unavailable` rows that say what happened |

A roster row (anonymized sample):

```json
{
  "_status": "found",
  "_input": { "company": 456123 },
  "_freshness": "fresh_90d",
  "_detail": "roster",
  "fullName": "Jane Doe",
  "title": "VP Engineering",
  "seniority": "vp",
  "headline": "VP Engineering at Acme",
  "locality": "Amsterdam",
  "countryCode": "nl",
  "hasPersonalEmail": true,
  "hasWorkEmail": true,
  "lowSignal": false,
  "positionStartYear": 2021,
  "personUpdatedAt": "2026-08-14T09:12:44Z",
  "positionUpdatedAt": "2026-08-14T09:12:44Z",
  "profileUrl": "https://www.linkedin.com/in/jane-doe-example"
}
```

With `profileDetail: "contacts"` the row also carries the career card and
the contact columns (values made up):

```json
{
  "_detail": "contacts",
  "email": "jane.doe@acme.example",
  "emailType": "work",
  "employerMatch": true,
  "workEmails": ["jane.doe@acme.example"],
  "personalEmails": ["jane.doe@example.com"],
  "emailCount": 2,
  "phone": "+15550100123",
  "phones": [{ "number": "+15550100123", "sharedBy": 1, "companyLine": false }]
}
```

The **Output tab** has two views: *Overview* and *Reachability & freshness*.

### Pricing

| Event | Price | When |
|---|---|---|
| Employee row | $0.0015 | roster row, or a richer tier the store could not answer |
| Employee row (full profile) | $0.0032 | `profile`, or `contacts` without a working contact |
| Employee row (profile + contacts) | $0.008 | `contacts` and a contact that reaches the person today |
| Repeat of an employee already delivered | **$0** | never reaches your dataset |
| Skipped by `mustHave`, unresolved domain, invalid entry | **$0** | always free |

The store keeps historical snapshots of a person under separate ids (13.5
to 21.7% of rows on full rosters we measured); this Actor delivers each
person once, so the price per 1,000 rows is the price per 1,000 people. Up
to 50,000 rows per run; set `maxRows` to cap the spend.

### FAQ

**A domain came back `unresolved_domain`. Do I pay?** No. It is a free row
saying no company record vouches for that domain.

**Why was an employee charged as a profile on the contacts tier?** They had
no personal mailbox, no address on this employer's domain and no labelled
direct phone. Their older addresses are still in the row.

### Use LinkedIn Company Employees with AI agents and MCP

This Actor works as a tool for AI agents. Add it to Claude, ChatGPT, Cursor or any other MCP client through the Apify MCP server:

```
https://mcp.apify.com?tools=b2bsearch/company-employees
```

- **Fast enough for a tool call.** A small request finishes in seconds, so the agent gets its answer inside one call.
- **The agent pays only for results.** Prices are per result (see the pricing section above) and every miss is a free row. Cap what one call may spend with `maxTotalChargeUsd`.
- **Rows explain themselves.** Each row has a `_status`; a row that is not a result says why in `_error`, so the agent can decide what to do next without guessing.
- **Compact rows for a context window.** `"compact": true` returns a short row — about 2 KB for a full profile instead of 10+ KB: identity, current role, the 5 latest positions, education, top skills and any contacts. Same price; leave it off to get the complete record.
- **Bounded cost.** `maxRows` limits how many rows one call can deliver and bill.

Input an agent can send as is:

```json
{
  "companies": [
    "stripe.com"
  ],
  "roles": [
    "cxo"
  ],
  "profileDetail": "roster",
  "titleContains": [],
  "titleExcludes": [],
  "excludeLowSignal": false,
  "maxRows": 100,
  "compact": true
}
```

The same Actor is available as a tool in LangChain, CrewAI and the OpenAI Agents SDK, and as a step in n8n, Make and Zapier through the Apify integrations.

### Which actor in this family?

One database, ten doors. Misses are free on every one of them.

| Actor | Input → output |
|---|---|
| [Profile Lookup](https://apify.com/b2bsearch/profile-lookup) | profile URL → full career profile |
| [Reverse Email Lookup](https://apify.com/b2bsearch/reverse-email-lookup) | email → person, profile URL and employer |
| [Name to Profile](https://apify.com/b2bsearch/name-to-profile) | name + company domain → profile |
| [Social Handle Lookup](https://apify.com/b2bsearch/social-handle-lookup) | GitHub, X/Twitter or Facebook handle → profile |
| [Bulk People Enrichment](https://apify.com/b2bsearch/bulk-people-enrichment) | CSV of emails, URLs, handles or names → profiles |
| [LinkedIn Email Finder](https://apify.com/b2bsearch/linkedin-email-finder) | profile URL → email addresses on record |
| [Work Email Finder](https://apify.com/b2bsearch/work-email-finder) | name + company domain → work email candidates |
| **Company Employees** (this one) | company domain → current staff |
| [People Database Search](https://apify.com/b2bsearch/people-database-search) | filters → people |
| [Company Database Search](https://apify.com/b2bsearch/company-database-search) | filters → companies |

### Disclaimer

This Actor is an independent product. It is not affiliated with, endorsed by
or sponsored by LinkedIn. It does not access, crawl or scrape any of them at
run time: answers come from our own database of publicly available
professional data, and the network names only describe the kind of data it
covers. To have a person's data removed, open an issue on this Actor with only
the profile link — nothing else is needed, and it is removed from every listing.

# Actor input Schema

## `companies` (type: `array`):

One company per line: a site domain (acme.com) or a numeric company id from a previous run. Domains that match no company come back as free "unresolved\_domain" rows.

## `roles` (type: `array`):

Keep only these seniority buckets. Leave empty for the whole roster.

## `profileDetail` (type: `string`):

roster = the staff list row, $1.50 per 1,000; profile = each employee’s full career profile, $3.20 per 1,000; contacts = the profile plus emails and phones, $8 per 1,000 employees with a contact that reaches them today (the rest ship at the profile price). The profile tiers run in the same run and cap it at 10,000 employees.

## `mustHave` (type: `array`):

Deliver and charge only employees who have all of these; the rest are skipped for free and counted in one note row. Personal and work email work on every tier; social profiles need the profile tier; phone and "work email at the current employer" need emails & phones.

## `compact` (type: `boolean`):

Returns a short row instead of the full record: identity, current role, location, the 5 latest positions, education, top skills and any contacts — about 2 KB per person instead of 10+ KB. Made for AI agents and LLM pipelines with a context limit. Same price. Off by default: a run returns the complete record.

## `titleContains` (type: `array`):

Keep only employees whose job title contains any of these words (case-insensitive, 3–64 characters each, up to 10; an entry outside these rules stops the run before anything is charged). Reaches titles the seniority buckets misfile: "President" is filed under Other.

## `titleExcludes` (type: `array`):

Drop employees whose job title contains any of these words. The C-level bucket also holds "Executive Operations, Office of the CEO" and "Executive Assistant to CRO"; assistant, office of, executive operations, chief of staff removes them before they are counted or charged.

## `excludeLowSignal` (type: `boolean`):

Drop rows the data flags as low-signal: under 10 connections and no start date on the position — the self-declared "CEO at <famous brand>" pattern. Off by default because among rank-and-file staff many such rows are real people with a hidden network; they only sort last. Every row carries the lowSignal column either way.

## `maxRows` (type: `integer`):

Stop after this many employee rows across all companies (default 1000; maximum 50000 on roster rows, 10000 on the profile tiers). Companies left unqueried when the cap hits are reported as free skipped\_row\_budget rows.

## Actor input object example

```json
{
  "companies": [
    "stripe.com"
  ],
  "roles": [
    "cxo"
  ],
  "profileDetail": "roster",
  "compact": false,
  "titleContains": [],
  "titleExcludes": [],
  "excludeLowSignal": false,
  "maxRows": 100
}
```

# Actor output Schema

## `results` (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 = {
    "companies": [
        "stripe.com"
    ],
    "roles": [
        "cxo"
    ],
    "profileDetail": "roster",
    "titleContains": [],
    "titleExcludes": [],
    "excludeLowSignal": false,
    "maxRows": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("b2bsearch/company-employees").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 = {
    "companies": ["stripe.com"],
    "roles": ["cxo"],
    "profileDetail": "roster",
    "titleContains": [],
    "titleExcludes": [],
    "excludeLowSignal": False,
    "maxRows": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("b2bsearch/company-employees").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 '{
  "companies": [
    "stripe.com"
  ],
  "roles": [
    "cxo"
  ],
  "profileDetail": "roster",
  "titleContains": [],
  "titleExcludes": [],
  "excludeLowSignal": false,
  "maxRows": 100
}' |
apify call b2bsearch/company-employees --silent --output-dataset

```

## MCP server setup

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

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/ZqqWQVioHjdURtVEb/builds/4lATL4WDdsNdLcLUf/openapi.json