👥 LinkedIn Employee List by Company: Names and Profile URLs, Bulk | No Login

Type a company name, or a whole list, and get back a target-people list: LinkedIn profile URLs of people who work there, with name, headline and photo. No LinkedIn account, no cookies, no ban risk. Search one company, or a whole list in bulk.

No login | 4 search patterns | Multi-country | Up to 100 results | Bulk company lists | JSON/CSV export

Not a scraper. We use X-ray search over publicly indexed data. We never touch LinkedIn's servers. Not affiliated with LinkedIn.

See all 10 actors by b2bdata

---

💳 Pricing and plans

Pay per result, see the Pricing tab. Free Apify plan: up to 100 results per run, as many runs as your Apify credit covers (the $5 monthly free credit buys about 2,500 employees). Paid plans have no per-run limit. Normal Apify platform usage applies.

Success-only billing

You pay for delivered rows only. A failed lookup, an empty search or a notice row is free: failed lookups are free. Each delivered employee is one employee event, charged right after the row is saved. Higher Apify plans pay less per result: Bronze 5% off, Silver 10% off, Gold and above 15% off. Exact numbers are on the Pricing tab.

Add-ons (charged extra)

Add-ons are opt-in inputs, off by default. Each is its own billed event and is charged only when it actually returns data for a row. The base run returns no emails; to get work emails, chain this actor to an email finder.

Delta mode

Set deltaMode to true for scheduled runs. We keep a hash of each row in a named key-value store in your own account (deltaStoreName, default linkedin-employee-search-delta). Only new or changed rows are pushed and charged. The OUTPUT summary reports newRows, changedRows and skippedUnchanged.

Compatible output

Set outputFormat to compatible to get common LinkedIn scraper field names instead of ours, so existing pipelines keep working. The default is default, unchanged. The mapping table is in AGENTS.md.

---

⚖️ This vs. the alternatives

	This actor	LinkedIn's own search	Cookie-based tools (PhantomBuster, Dux-Soup)
LinkedIn account needed	No	Yes	Yes (your cookies)
Account ban risk	None	n/a	Real
Results per search	Up to 100	Gated by plan	Varies
Several companies in one run	Yes, bulk mode	Manual	Varies
Multi-country in one run	Yes, comma-separated codes	Manual	Varies
Output	Clean JSON/CSV via API	HTML	Varies
Deduplication	Yes	No	Rarely
Incremental saving	Yes	No	Varies
Cost per profile	Pay per result, see Pricing tab	Subscription	Subscription or per-result

This actor returns no emails. For a lead list with work emails, take the company domain and pass it to executive-email-finder-by-domain, or use linkedin-leads-verified-work-emails to filter by title and get emails in one run. We do not claim to return more data per person than the others. We return less, on purpose: the profile URL, the name, the headline, the photo and the parsed first and last name. That is what you need to build a target list without risking an account.

---

⚡ Why this actor?

• No login, no cookies. Nothing of yours is exposed. Nothing to get banned.
• Two modes. Employee Search for one company, Bulk Employee Search for a list, one company per line.
• Four search patterns. From strict to broadest. You choose how many results you want to trade for precision.
• Countries as a list. Give us, uk, de and each country is searched on its own.
• Runs keep what they found. Every profile is saved the moment it is found. If a run stops, you keep what it collected.

---

🎯 Use cases

• Sales prospecting. Find the people at a target account, then filter by role on your side.
• Account-based marketing. Build a contact list per company, one company per line in bulk mode.
• Recruiting research. Map who works where before you reach out.
• Competitive intelligence. See the team around a competitor, by country.
• Conference prep. Research the people behind a list of exhibitor companies before the event.
• Lead list building. Start from linkedin-company-search, then pull employees for each company page you found.

---

🔗 Pipeline guide: from company to contact

This actor is step 2. Chain b2bdata actors and you go from a keyword to people, and from a company domain to a decision-maker's email:

keyword: "fintech", countries: "uk, de"
        |
        v
 [1] linkedin-company-search     -> company page URL, name, headline, logo
        |
        v
 [2] linkedin-employee-search    -> employee profile URL, name, headline, photo
        |
        v
 [3] executive-email-finder-by-domain -> work emails for decision-makers (needs the company domain)

To get the company domain for step 3, use company-firmographics-by-domain. All of them are on the publisher page: See all 10 actors by b2bdata. Each step reads the previous step's dataset, so a Make or n8n scenario chains them without code.

---

🚀 Quick start

Open the actor, fill the form, press Start. Or send JSON. Examples:

1. Employees at one company

{
  "service": "single_employee",
  "companyName": "Stripe"
}

2. Sales leaders in three countries, strict pattern

{
  "service": "single_employee",
  "companyName": "Salesforce",
  "employeePattern": "3",
  "employeeCountries": "us, uk, de",
  "employeeMaxResults": 50
}

3. Bulk: a list of companies, one per line

{
  "service": "bulk_employees",
  "bulkCompanies": "Marriott International\nHilton Worldwide, uk\nStripe\nAdyen",
  "bulkEmployeePattern": "2",
  "bulkMaxResultsPerCompany": 25,
  "loadAll": true
}

---

⚙️ Inputs

Pick a mode with service, then fill the fields of that mode.

Parameter	Type	Required	Default	Mode	Description
service	string	Yes	"single_employee"	both	"single_employee" (one company) or "bulk_employees" (a list of companies).
companyName	string	For single	none	single	Company name as it appears on LinkedIn, for example "National Bank of Canada". Returns employees whose profile mentions this company. You can also paste a LinkedIn company URL (linkedin.com/company/...): it is converted to the company name, anything else is searched as typed. Rows show what you typed in inputQuery and how it was read in inputRoute; a LinkedIn URL that is not a company URL ends the run with an explanation row, no charge.
excludeWords	string	No	empty	single	One keyword to drop from results, for example "Intern". Only one keyword.
employeePattern	string	No	"2"	single	"1" strict (often returns no results), "2" moderate (default), "3" broad (phrase match), "4" broadest.
employeeCountries	string	No	empty	single	Comma-separated country codes, for example uk, us, de. Empty means one global search.
employeeMaxResults	integer	No	100	single	Max profiles to return, 1 to 100.
bulkCompanies	string	For bulk	none	bulk	One company per line. Format: CompanyName, Country (country optional).
bulkEmployeePattern	string	No	"2"	bulk	Same four patterns as employeePattern.
bulkMaxResultsPerCompany	integer	No	100	bulk	Max profiles per company, 1 to 100.
bulkDelayMs	integer	No	1500	bulk	Milliseconds between searches, 500 to 10000. Does not affect pricing.
loadAll	boolean	No	false	both	Paginate up to your max.

Pattern tips: start with "2". Use "1" only when you want the strictest match and can live with empty results. Use "4" to get as many profiles as possible.

---

Advanced inputs (API users)

These fields are hidden in the Console form and meant for API and automation use.

Field	Type	Default	What it does
maxChargeUsd	number	0 (off)	Stops the run when this run's charges reach the amount. The run ends SUCCEEDED with the rows already delivered and one free explanation row (max_charge_reached). The check runs after each charge, so a run can exceed the amount by one result.
sourceTag	string, up to 100 characters	empty	Copied onto every result row as sourceTag and into the OUTPUT record, so a CRM or Clay table can match results to the request that produced them. Explanation rows never carry it.

📤 Output

Every row carries scrapedAt (ISO timestamp of the run) and inputQuery (the query that produced it).

One dataset row per profile.

{
  "url": "https://www.linkedin.com/in/satyanadella",
  "name": "Satya Nadella",
  "headline": "Chairman and CEO at Microsoft",
  "photoUrl": "https://media.licdn.com/dms/image/...",
  "firstName": "Satya",
  "lastName": "Nadella"
}

Export as JSON, CSV, Excel, XML or HTML from the Output tab, or read the dataset over the API.

Fields you might see when present

Alongside the six fields, a row can carry searchQuery (the parameters that produced it) and bulkIndex (the 0-based line number from your bulk input, so you can match results back to your list). Instead of a data row you can get a status row:

• noResults: true when nothing matched.
• error: true when a search failed.
• message: status or error details.

What is NOT returned

• ❌ Email addresses or phone numbers (see executive-email-finder-by-domain and email-phone-finder)
• ❌ Work history, education or skills
• ❌ Company size, revenue or domain (use company-firmographics-by-domain)
• ❌ Posts, connections or private profiles
• ❌ A job-title filter. Filter on headline after you get the rows.

A field with nothing to show is dropped, so rows never carry filler text.

---

🛡️ Reliable results

Our data promise. We work to keep every contact current, and we stand behind it. If a record is outdated, an email bounces or a person has moved on, open the Issues tab with your run link. We review every report and sort it out with you, case by case.

• Incremental saving. Every profile is saved the moment it is found. A run that stops keeps everything so far.
• Automatic deduplication. The same profile URL never appears twice.
• Retry with backoff. Transient failures are retried automatically (three attempts) before a search is given up on.
• Status rows instead of silent gaps. A search that finds nothing or fails leaves a row that says so.

---

🤖 For AI agents

This section is written for an LLM agent that calls this actor as a tool, through the Apify MCP server or the API. Humans: it doubles as a one-screen contract.

When to use this actor, and when to use a sister actor

• Use b2bdata/linkedin-employee-search when you know the company and need the people who work there.
• linkedin-company-search: you have a company name or industry keyword and need company page URLs.
• linkedin-person-search: you know a person's name and want their profile.
• linkedin-people-search: you want company search and employee search behind one actor, with one form.
• linkedin-leads-verified-work-emails: you want a lead list by job title, seniority, location and company size in one call.
• company-firmographics-by-domain: you have a company domain and want firmographics.
• executive-email-finder-by-domain and ceo-founder-email-finder-by-domain: you have a domain and need decision-makers or founder emails.
• email-phone-finder: you have work emails and want phone numbers and the person behind each email.

Input contract

Field	Type	Default	Notes
service	string, "single_employee" or "bulk_employees"	"single_employee"	Required. Picks the mode.
companyName	string	none	Single mode. Company name as on LinkedIn.
excludeWords	string	empty	Single mode. One keyword to exclude.
employeePattern	string, one of "1"-"4"	"2"	Single mode. Pass a string, not a number.
employeeCountries	string	""	Single mode. Comma-separated, for example "us, uk".
employeeMaxResults	integer 0-100 (0 = all)	100	Single mode.
bulkCompanies	string	none	Bulk mode. One company per line, Name, country with country optional.
bulkEmployeePattern	string, one of "1"-"4"	"2"	Bulk mode.
bulkMaxResultsPerCompany	integer 0-100 (0 = all)	100	Bulk mode.
bulkDelayMs	integer 500-10000	1500	Leave it alone.
loadAll	boolean	false	Paginate up to the max.

Required: service, plus companyName (single) or bulkCompanies (bulk). Send only the fields you need.

Output contract

Each item: url (string, LinkedIn profile), name (string), headline (string), photoUrl (string), firstName (string), lastName (string). Optional: searchQuery (object), bulkIndex (integer). Status rows carry noResults (boolean), error (boolean) and message (string) instead of profile data. Nothing else is ever returned. Always check error and noResults before treating a row as a person.

Cost per call

You pay per result returned, plus Apify platform usage. An empty search costs nothing. Keep your max-results fields low while testing. Free Apify plans get up to 100 results per run; paid plans have no per-run limit.

Idempotency and rate advice

Same input, same run. It writes a fresh dataset every time and results can change as the index changes, so do not assume two runs return identical rows. Deduplicate on url. Do not loop the same company. For several companies use bulk mode, not one run per company. Do not run more than a few runs at once.

Chaining

Take url, name and headline from each row. Filter by role on headline yourself, the actor has no title filter. To find one named person, pass the name plus the company to linkedin-person-search. For work emails, find the company domain with company-firmographics-by-domain and pass the domain to executive-email-finder-by-domain. Always filter rows by error and noResults first.

Error cases and what to do

Situation	What you see	What to do
Nothing matched	A row with noResults: true	Retry once with employeePattern: "4" or without excludeWords. Do not retry more than twice.
A search failed	A row with error: true and a message	Read message. Retry once after a minute. If it keeps happening, post a report in this actor's Issues tab on Apify.
Free Apify plan, 100 results per run reached	Run SUCCEEDED with the first 100 results plus one free explanation row (free_plan_limit)	Tell the user the free plan returns 100 results per run. Run again for the rest; a paid Apify plan removes the limit.
Former employees or loose matches	Profiles that do not fit the company	Use a stricter pattern and check headline. Verify before acting.
Invalid input	Run rejected by the input schema	Fix the field named in the error (usually a pattern passed as a number instead of a string).

Minimal call

{
  "service": "single_employee",
  "companyName": "Stripe",
  "employeePattern": "2",
  "employeeMaxResults": 5
}

---

🔌 Integrations: send results anywhere

Every run writes to an Apify dataset. Dataset items from LinkedIn Employee Search carry url, name, headline, photoUrl, firstName, lastName. Actor id for all recipes: b2bdata/linkedin-employee-search (in API URLs, write it as b2bdata~linkedin-employee-search). Everything below uses the public Apify API and your own Apify token. Native means an Apify integration exists; CSV and automation routes are marked as such.

1. Fetch results over the API (native)

Send the token in a header, never in the URL. Latest successful run, as JSON, CSV or Excel:

curl -H "Authorization: Bearer $APIFY_TOKEN" "https://api.apify.com/v2/acts/b2bdata~linkedin-employee-search/runs/last/dataset/items?format=json&clean=true&status=SUCCEEDED"

Swap format=json for format=csv or format=xlsx (jsonl also works). clean=true drops empty items and hidden fields. Pick fields with jq:

curl -s -H "Authorization: Bearer $APIFY_TOKEN" "https://api.apify.com/v2/acts/b2bdata~linkedin-employee-search/runs/last/dataset/items?format=json&clean=true&status=SUCCEEDED" | jq '.[] | {name, url}'

Replace name and url with any field names from the output list above. For a specific run, use https://api.apify.com/v2/datasets/<datasetId>/items?format=json.

One-shot call (start a run and wait for its items, limited to 300 seconds): POST https://api.apify.com/v2/acts/b2bdata~linkedin-employee-search/run-sync-get-dataset-items?format=json&clean=true with the Actor input as the JSON body and the same Authorization header. For longer runs, start the run normally and fetch the dataset afterwards.

2. Webhook on run success (native)

In the Actor's Integrations tab (or via the API) add a webhook with event type ACTOR.RUN.SUCCEEDED and your own endpoint as the request URL. Apify sends a POST with the default payload, which contains the run under resource. Your endpoint reads resource.defaultDatasetId and calls the dataset items URL from recipe 1 with it. To send a smaller body, set a custom payload template: a JSON object whose values are Apify variables in double curly braces (resource, eventType, userId, createdAt, eventData), with nested values by dot, for example the run id as resource.id and the dataset id as resource.defaultDatasetId. Switch on "Interpolate variables in string fields" in Apify Console when you quote them.

3. n8n (native node)

Apify node, operation "Run an Actor and get dataset" (or "Run an Actor", then "Get dataset items" from the Datasets resource). Select b2bdata/linkedin-employee-search, paste the Actor input as JSON, and connect your Apify token as a credential. Each dataset item becomes one n8n item, so map url, name, headline, photoUrl, firstName, lastName straight into the next node. The Apify node also has an "On new Apify event" trigger for run-finished events.

4. Make (native app)

Apify app: module "Run an Actor" with b2bdata/linkedin-employee-search (or the trigger "Watch Actor Runs" for scheduled or manual runs), then the search module "Get Dataset Items" using the run's default dataset id. Each returned bundle is one row, so map url, name, headline, photoUrl, firstName, lastName into your destination module.

5. Zapier (native app)

Apify app: trigger "Finished Actor run" (or action "Run Actor" with b2bdata/linkedin-employee-search), then the search "Fetch dataset items" with the run's default dataset id. Map url, name, headline, photoUrl, firstName, lastName into your destination step. Add a Looping or similar step if your Zap needs one action per item.

6. Google Sheets

Apify's Store has a "Google Sheets Import & Export" Actor that you add on this Actor's Integrations tab, then choose append or replace mode and paste your spreadsheet URL. This needs a one-time Google login. Alternative with no extra Actor: Make or Zapier recipes above with their own Google Sheets module.

7. Clay (HTTP API)

In Clay, create an HTTP API request with method GET, URL https://api.apify.com/v2/acts/b2bdata~linkedin-employee-search/runs/last/dataset/items?format=json&clean=true&status=SUCCEEDED, and a header Authorization: Bearer <your Apify token>. Treat each returned item as a row and chain your enrichment columns after it.

8. Airtable, HubSpot, Salesforce

No native Apify connector is used here. Two routes:

• CSV: download with format=csv (recipe 1) or from the dataset's Export button, then use the tool's own import (Airtable CSV import, HubSpot Import, Salesforce Data Import Wizard or Data Loader). Use a unique field such as the URL as the dedupe key.
• Automation: use the n8n, Make or Zapier recipe above and the CRM's module there. Their setup and field limits are theirs to define.

9. Map the fields

LinkedIn Employee Search returns url, name, headline, photoUrl, firstName, lastName. Typical placement in a CRM (create custom properties where your CRM has no match):

Output field type	Typical CRM placement
Person name	Contact name (first and last)
Job title or role	Contact job title
Company name	Company or account name
Website or domain	Company website or domain
Profile or page URL	Custom text field, also your dedupe key
Location (city, country)	Contact or company location fields
Email, phone (if returned)	Contact email, phone
Industry, size (if returned)	Company industry, employee count
Run date	Custom date field ("Sourced on")

All recipes use the public Apify API; nothing is stored by the publisher.

---

🕐 Schedule examples

Use Apify Schedules (cron) on a saved task.

• Weekly team watch: 0 6 * * 1, one competitor in companyName, employeeMaxResults 100. Compare url against last week's dataset to see new profiles.
• Monthly account refresh: 0 6 1 * *, bulk mode with your target account list. Send results to your CRM through a webhook.
• Daily small check: 0 8 * * *, pattern "1", one company, 10 results. Cheap and fast.

Keep scheduled runs small. A schedule you forget is still billed.

---

🔗 Related actors

More from the publisher: See all 10 actors by b2bdata

• linkedin-company-search: company page URLs by name or keyword.
• linkedin-person-search: find a named person.
• linkedin-people-search: company and employee search in one actor.
• linkedin-leads-verified-work-emails: lead lists by title, seniority, location and company size.
• company-firmographics-by-domain: firmographics for a company domain.
• executive-email-finder-by-domain: decision-makers by domain.
• ceo-founder-email-finder-by-domain: founder emails by domain.
• email-phone-finder: phone numbers and identity for work emails.

---

❓ FAQ

Data & coverage

Q: How do I find employees of a company on LinkedIn? A: Set service to single_employee, put the company name in companyName and run. You get profile URL, name, headline and photo for each person found.

Q: Do I need a LinkedIn account? A: No. No account, no cookies, no login.

Q: How many employees can I get? A: Up to 100 per search. Several countries means several searches, each with its own max.

Q: Can I filter by job title? A: Not in the form. Search the company, then filter the headline field on your side.

Q: Can I search many companies at once? A: Yes. Set service to bulk_employees and put one company per line in bulkCompanies. Add a country after a comma to limit that line.

Q: Why do I see former employees or unrelated people? A: The search is keyword based on publicly indexed data. Use a stricter pattern, check headline, and review the list by hand.

Q: Is email, phone or work history included? A: No. This actor returns the profile URL, name, headline, photo and parsed name. Use the pipeline above for contacts.

Q: Will brand-new profiles appear? A: Maybe not yet. Results come from publicly indexed data, so very new profiles can be missing.

Q: Am I charged for failed lookups? A: No. Failed lookups are free. You pay one employee event per delivered employee; empty results and notice rows cost nothing.

Q: What are add-ons and are they on by default? A: Add-ons are opt-in inputs, off by default. Each is its own billed event, charged only when it returns data for that row.

Q: How do I only pay for new or changed rows on a schedule? A: Turn on deltaMode. We compare each row to a hash in a store in your account and push only new or changed ones. The summary shows newRows, changedRows, skippedUnchanged.

Q: Can I keep my existing field names? A: Yes. Set outputFormat to compatible for common LinkedIn scraper field names. Default output is unchanged.

Legality & compliance

Q: Is this legal? A: Not legal advice. No account, cookie or login is involved: every employee row comes from publicly available information only. How you use that list is up to you, so apply the privacy and outreach rules that cover your own market. For legal questions or complaints, write to Apify support at https://apify.com/contact; they will route it to us.

Q: Does it break LinkedIn's terms of service? A: No LinkedIn session or account is used at any point, and the actor does not accept LinkedIn's terms on anyone's behalf. Using the output lawfully is your job.

Q: Does it collect personal data? A: Yes, profile data about real people: names, headlines, photos and profile URLs from public pages. If you hold it, you are the data controller. You need a lawful basis for your own use, a way to honour deletion and opt-out requests, and you should keep only what you need.

Q: Is it GDPR and CCPA compliant? A: The compliance duties sit with you as controller: lawful basis, notices, opt-outs, deletion. The Master Terms below explain who does what.

Q: Do you store my results? A: No. We keep no copy of your result data. It lives in your Apify account.

Q: Can I use the output for cold email? A: This actor returns no emails. If you add emails from another tool, you must follow anti-spam and privacy rules for each country you contact.

Q: Can I be blocked or banned? A: Your LinkedIn account cannot be, because it is never used. Your Apify account can be limited if you break the Terms below.

---

🛟 Support

Use the Issues tab on this actor's Apify page for bugs, questions and feature requests. We answer within 24 hours on working days. Please include the run ID and the input you used.

---

📜 Legal

Use for B2B prospecting only. Comply with all applicable laws including GDPR, CCPA, and CAN-SPAM.

Not affiliated with LinkedIn. The LinkedIn name belongs to its respective owner. This actor finds employee profile URLs through publicly indexed data. It does not log in, use cookies, access private pages or bypass authentication. Published on Apify by b2bdata as proprietary software.

📜 Master Terms of Service

Publisher: b2bdata (the "Publisher"), an independent developer publishing on the Apify platform. Applies to: LinkedIn Employee Search (the "Actor"). Version: 1.0.

Acceptance by use

By running the Actor, calling it through the Apify API, the Apify MCP server or any integration, or letting a schedule or an AI agent run it for you, you accept these Terms. This is acceptance by use. No signature is needed.

If you run the Actor on behalf of a company, you confirm you may bind that company. If you do not accept these Terms, do not run the Actor. Continued use after we update the Terms is acceptance of the update. Anonymous or automated use does not remove your responsibility: the Apify account that starts the run is the accountable party.

Preamble: how the Actor is built

The Actor is a thin wrapper over an independent search index. It does not log in to anything, does not use cookies or accounts, and does not fetch pages from the source platform. We are a software vendor. We ship code that turns a query into a structured result. We do not own, host or curate the underlying data.

You / your agent
      |  input (query, filters)
      v
  The Actor (the Publisher's code, runs on Apify)
      |  search request
      v
  An independent search index of publicly indexed data
      |  public result rows
      v
  The Actor (normalises, deduplicates, saves to your dataset)
      |
      v
  Your Apify dataset (you control it)

Each party has one job. The index holds publicly indexed data. The Actor reshapes it. You decide what to search for, what to keep and what to do with it. We keep no copy of your queries or your results once the run ends, beyond what Apify itself stores in your account and what we need for billing and abuse prevention.

1. Nature of the service

1.1 What the Actor is

A software tool that searches publicly indexed data and returns structured rows to your Apify dataset. It is a data-discovery utility, nothing more.

1.2 What the Actor is not

It is not a scraper of the source platform, not an official integration, not a credit bureau, not a background-check service, not an employment or tenant screening tool, and not a source of legal, financial or compliance advice. Results are leads and pointers. They are not verified facts.

1.3 The publisher's limited role

We write and maintain the code. We do not review individual runs, individual results or individual users. We do not guarantee that a result is accurate, current, complete or lawful to use for your purpose.

1.4 Third-party infrastructure

The Actor depends on the Apify platform and on an independent search index. We do not control either. Their availability, rules and changes can affect the Actor at any time.

2. Who may use the Actor

2.1 Eligibility

You must be at least 18, have the legal capacity to contract, and not be barred from using the Apify platform or from receiving services under applicable sanctions or export laws.

2.2 Your representations

By running the Actor you represent that you have a lawful purpose, that you will follow the laws that apply to you and to the people whose data you handle, and that the information on your Apify account is accurate.

3. Permitted uses

Lawful business uses, including market research, account and lead discovery, competitive analysis, recruiting research done in line with local law, investment research, data enrichment of records you are entitled to hold, and building your own internal tools. Any use must comply with Section 4 and Section 6.

4. Prohibited uses

4.1 Illegal activity

Any use that violates a law or regulation that applies to you, to us or to the people in the data.

4.2 Harassment, stalking and personal targeting

Locating, monitoring, intimidating or pressuring a private individual.

4.3 Discrimination

Using results to exclude or disadvantage people on a protected characteristic, including in hiring, lending, housing or insurance decisions.

4.4 Spam and unsolicited commercial communication

Sending bulk messages in breach of anti-spam, e-privacy or telemarketing rules (for example CAN-SPAM, PECR, CASL, GDPR consent rules).

4.5 Fraud and deception

Phishing, impersonation, social engineering, fake profiles or any scheme to mislead.

4.6 Source platform abuse

Using the Actor to evade a block, rate limit or enforcement action by the source platform, or to build a service that competes with the source platform by copying its data wholesale.

4.7 Reselling the Actor's service

Reselling or sub-licensing access to the Actor, or republishing raw output as a competing data product, without our written permission.

4.8 AI training without authorization

Using raw output to train a model that identifies or profiles individuals, without a lawful basis and without checking the source platform's terms.

4.9 Sensitive targeting

Building lists based on health, religion, ethnicity, political opinion, sexual orientation, union membership, immigration status, criminal history or any other special category of data.

4.10 Privacy law violations

Any processing of personal data without a lawful basis, without required notices, or in breach of a data subject's rights.

5. Source platform terms: your responsibility

5.1 Acknowledgment

The source platform named in the Addendum has its own terms. We have no contract with you about them and we do not interpret them for you.

5.2 Your sole responsibility

You alone are responsible for checking whether your use of results is allowed under the source platform's terms and under the law of your jurisdiction. Running the Actor is not a statement by us that your use is allowed.

5.3 Cease-and-desist compliance

If the source platform, a rights holder or a regulator sends us a valid cease-and-desist or takedown notice about specific use of the Actor, we will act on it. If we forward such a notice to you, you must stop the named use within 48 hours of receipt and confirm in writing. We may suspend your access immediately while we assess the notice.

6. Data protection

6.1 Roles under privacy law

For the data you collect with the Actor, you are the data controller (or business, under CCPA). Apify and its infrastructure act for you as processor or service provider under their own terms. We, as the publisher of the code, do not decide the purposes or means of your processing and do not receive your result data.

6.2 No data retention by the publisher

We do not retain your result data. We do not build a database from your runs. We keep only what is needed for billing, security and abuse prevention, such as run metadata and support correspondence.

6.3 Your obligations as data controller

You must have a lawful basis (GDPR, UK GDPR), give required notices, honour access, deletion and objection requests, respect opt-outs and "do not sell or share" rights (CCPA/CPRA), keep records, protect the data, and delete it when you no longer need it.

6.4 Sensitive data targeting

You must not use the Actor to target special-category data (see 4.9). If sensitive data appears in results, you must delete it or handle it under the stricter rules that apply.

6.5 Data subject requests

If a person contacts us about data you collected, we will refer them to you and may ask you to confirm you have handled the request.

7. Intellectual property

7.1 Actor code

The Actor, its code, schemas, documentation and branding belong to the Publisher. This is proprietary software. No licence is granted except the right to run the Actor under these Terms.

7.2 Output data

We claim no ownership of the output. Rights in underlying data belong to their owners. You are responsible for how you use it.

7.3 Restrictions

No reverse engineering, copying of the Actor, or removal of notices, except where the law gives you that right regardless.

7.4 Feedback

If you send feedback or bug reports, we may use them freely to improve the Actor, without payment, and without crediting you.

8. Pricing and payment

8.1 Apify platform billing

Charges are set on the Actor's Pricing tab and billed by Apify. Platform usage costs may also apply, as shown by Apify. We do not handle your payment details.

8.2 Pricing changes

We may change prices. For any increase we give at least 14 days' notice through the Apify platform's change-notification process before it takes effect.

8.3 No refunds for misuse

Results delivered as described are billable. Charges for runs you configured wrongly, repeated by a schedule you forgot, or started by an agent you control are your responsibility. Refund requests for platform or Actor faults go through Apify support or to us.

9. Service availability and changes

9.1 No uptime guarantee

We give no uptime, latency, volume or coverage guarantee. Runs can return fewer results than you asked for, or none, because the underlying index changes.

9.2 Service discontinuation

We may change, limit or stop the Actor at any time. We will try to give notice on the Actor page when practical.

10. Disclaimers

10.1 "As is" service

The Actor is provided "as is" and "as available", without warranties of any kind, including merchantability, fitness for a particular purpose, accuracy and non-infringement.

10.2 No representation of lawfulness

We do not represent that your intended use is lawful.

10.3 No endorsement of source content

Results are not endorsed, verified or vouched for by us. Names can be wrong, profiles can be outdated and similarly named entities can be mixed up.

11. Limitation of liability

11.1 Aggregate cap

To the maximum extent the law allows, our total liability for all claims relating to the Actor is limited to the greater of USD 100 or the fees you paid for the Actor in the 3 months before the event that gave rise to the claim.

11.2 Excluded damages

We are not liable for indirect, incidental, special, consequential or punitive damages, or for lost profit, lost revenue, lost data or lost goodwill, even if advised of the possibility.

11.3 Time limit

Any claim must be brought within 1 year after it arose.

12. Indemnification

12.1 Your indemnification of the publisher

You will indemnify and hold harmless the Publisher, its owners and contractors from claims, losses and reasonable legal costs arising from your use of the Actor or its output, your breach of these Terms, or your violation of any law or third-party right.

12.2 Defense

We will tell you promptly about a claim. You may control the defense, but you may not settle in a way that admits fault for us without our written consent.

12.3 Scope

This applies whatever the legal theory, and survives termination.

13. Suspension and termination

13.1 Termination by the publisher

We may suspend or end your access at any time, with or without notice, especially for a breach of Section 4 or a valid notice under 5.3.

13.2 Effects of termination

Rights to run the Actor stop. Sections that by nature survive (IP, disclaimers, liability, indemnification, disputes) continue.

13.3 Termination by you

Stop running the Actor and delete your schedules and integrations.

14. Dispute resolution

14.1 Informal resolution first

Before any formal action, raise the dispute through Apify support or the Actor's issue tab on Apify, and allow 60 days for a good-faith resolution. The Issues tab is for product questions only and is not a channel for legal notices.

14.2 Apify's process next

If the informal step fails, raise the matter through Apify's dispute and support channels. Your contractual relationship for payment, refunds and platform access is with Apify, under Apify's Terms of Service.

14.3 No chosen court

These Terms do not select a governing law or a court. Any claim that survives 14.1 and 14.2 is subject to the law and forum that apply by default to a dispute between you and an individual software developer reached through Apify.

14.4 No class actions

Claims may be brought only on an individual basis, not as a plaintiff or class member in a class, collective or representative action.

14.5 Attorneys' fees

The prevailing party may recover reasonable attorneys' fees where the law allows.

15. Miscellaneous

15.1 Entire agreement

These Terms, with the Addendum, are the whole agreement about the Actor. Apify's own terms continue to apply to the platform.

15.2 Severability

If a provision is unenforceable, the rest stays in force.

15.3 Assignment

You may not assign these Terms. We may assign them in a merger, sale or reorganisation.

15.4 Force majeure

Neither party is liable for delay caused by events beyond reasonable control, including outages of the platform or of upstream infrastructure.

15.5 Third-party beneficiaries

There are none, except that the Publisher's owners, contractors and affiliates may enforce the protections in Sections 10 to 12.

15.6 Survival

Sections 5, 6, 7, 10, 11, 12 and 14 survive termination.

15.7 Language

The English text controls.

15.8 Publisher identification for legal process

All legal notices, takedown requests, cease-and-desist letters, regulator enquiries and data-subject requests must be directed to Apify (https://apify.com/contact), which forwards them to the Publisher. The Publisher operates on Apify under the username b2bdata. The Publisher's identity is held by Apify for billing and is provided to courts and authorities through valid legal process directed via Apify's official channels. We do not publish personal details on the Actor page.

16. Acknowledgment

By running the Actor you confirm you have read these Terms, that you understand you act as the data controller of what you collect, and that you are responsible for lawful use.

---

🛡️ Actor-Specific ToS Addendum: LinkedIn Employee Search

A. Architectural disclosure

The actor sends your company name to an independent search index of publicly indexed data and returns the matching profile URL, name, headline, photo URL and parsed first and last name. It does not call LinkedIn, does not log in and does not use cookies.

B. Source platform

The source platform is LinkedIn. LinkedIn is not affiliated with, and has not endorsed, this actor. Your use of LinkedIn data is governed by LinkedIn's terms and by the law that applies to you (Section 5 of the Master Terms).

C. Output and accuracy

Results may include former employees, similarly named people, out-of-date headlines or missing profiles. Treat output as leads to verify, not as verified facts about a person or their employer.

D. Personal data

This actor returns names and profile URLs of real people. It returns no emails and no phone numbers. You act as the data controller of what you keep. If you combine its output with data from other actors or tools, you take on the duties for that combined data.

E. Limits

Up to 100 results per search. Free Apify plans get up to 100 results per run; paid plans have no per-run limit.

F. Feedback

To share a problem with any b2bdata actor, run b2bdata/supporter-feedback (free, no rewards) or write in the Issues tab here.

G. Takedown

If a person, a company or LinkedIn asks that specific use of this actor stop, send the request through Apify (https://apify.com/contact) or the actor's issue tab, not to a support mailbox. Section 5.3 of the Master Terms (48 hours) applies.