LinkedIn Company Employees — Staff List + Full Profiles ✅

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

{
  "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
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):

{
  "_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):

{
  "_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:

{
  "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	profile URL → full career profile
Reverse Email Lookup	email → person, profile URL and employer
Name to Profile	name + company domain → profile
Social Handle Lookup	GitHub, X/Twitter or Facebook handle → profile
Bulk People Enrichment	CSV of emails, URLs, handles or names → profiles
LinkedIn Email Finder	profile URL → email addresses on record
Work Email Finder	name + company domain → work email candidates
Company Employees (this one)	company domain → current staff
People Database Search	filters → people
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.