# Verified LinkedIn People Search & Email Finder (`clura/verified-linkedin-people-search`) Actor

Search LinkedIn by job title, company, and location and get back people confirmed to still be there — every result freshness-checked before delivery, with optional verified email lookup. Pay per confirmed result, not per attempt.

- **URL**: https://apify.com/clura/verified-linkedin-people-search.md
- **Developed by:** [Clura](https://apify.com/clura) (community)
- **Categories:** AI, Agents, Lead generation
- **Stats:** 6 total users, 5 monthly users, 96.2% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 results

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Verified LinkedIn People Search & Email Finder

Search LinkedIn by job title, company, and location — and get back people who are confirmed to still be there. Every result is freshness-checked against a live source before it's delivered, not pulled from a static, aging list. Add verified email lookup for any result, priced separately so you only pay for it when you need it.

Most LinkedIn data tools sell you a snapshot from whenever it was last scraped. We re-check every lead before delivery and stamp it with `lastVerifiedAt` — so "verified today" actually means today, not "verified sometime."

### How it works

**Two ways to search — use whichever fits:**

- **Natural-language** — describe who you want in plain English (e.g. *"Senior software engineers in Bangalore, MERN stack, open to work"*). We turn that into a set of targeted searches, pull live results, and keep only the ones whose location genuinely matches. Good for open-ended or business-intent searches ("decision makers I could sell to," "recruiters I could partner with") that don't reduce cleanly to a single job title.
- **Structured fields** — set Job title / City / Industry directly for an exact, filtered search against our verified database.

If you set the natural-language field, the structured fields are ignored — the two modes don't combine.

**Structured-search flow specifically:**

1. **Check the cache first** — anything already confirmed current in our database within the last 30 days is returned immediately, no re-check needed.
2. **Live-verify the rest** — for anything older or never checked, we re-confirm it against a live, independent source before counting it toward your total. If someone's moved on, we don't just drop the stale record — we update it with where they went, if we can find it.
3. **Stop at your target** — we keep working through matching candidates until we hit the number you asked for, or run out of matching candidates in our database. You're never charged for a candidate that didn't pan out.
4. **No repeats** — every account gets its own delivery history, so running the same search again (either mode) surfaces new people instead of the same list.

### Input

| Field | Type | Description |
|---|---|---|
| `query` | string | Plain-English search. When set, this replaces the structured fields below. |
| `title` | string | Job title to match — supports partial/keyword matching (e.g. `"Product Manager"`). Ignored if `query` is set. |
| `city` | string | Exact city name to filter by. Optional — leave blank to search all locations. Ignored if `query` is set. |
| `industry` | string | Filter candidates by industry. Optional. Ignored if `query` is set. |
| `targetCount` | integer | How many *confirmed, verified* people you want back. Default 100. |
| `includeEmail` | boolean | Attempt verified email lookup on every result (Email tier pricing applies). Default false. **Not yet available for natural-language search** — ignored (and charged at the no-email rate) in that mode. |

### Output

Each record: `name`, `linkedinUrl`, `title`, `seniority`, `company`, `city`, `state`, `country`, `location`, `lastVerifiedAt`, and `email` (if requested).

That's it — deliberately. We only return fields we can actively stand behind. Company firmographics (industry, website, employee count, revenue, tech stack) aren't included: they go stale the moment someone changes jobs, we don't re-verify them, and a mix of confirmed and unconfirmed fields on the same record is worse than just not shipping the unconfirmed ones.

`city`/`state`/`country` are populated for structured search directly from our verified database. For natural-language search, `location` (the single combined location string straight from the live source) is always populated, and `city`/`state`/`country` are split from it automatically — any part not clearly stated in the source string (e.g. an umbrella area like "Greater Bengaluru Area" with no explicit city) is left null rather than guessed. `seniority` is only populated for structured search.

### Pricing

Pay only for confirmed, delivered results — not per attempt, not per candidate checked.

| Tier | Price |
|---|---|
| **Verified Contact** (no email) | **$6 / 1,000 results** |
| **Verified Contact + Email** | **$12 / 1,000 results** |

### What this actor does NOT do (please read before running)

- **We never touch LinkedIn's login or authenticated systems.** No account, no session cookie, no risk to any LinkedIn profile — ours or yours. Results are sourced from public, independently indexed data, cross-checked against our own verification database.
- **Structured-search city matching is exact**, not fuzzy — a misspelled or alternate city name won't match today.
- **Volume isn't unconditionally guaranteed.** A narrow combination of title + industry + city may simply not have enough matching, verifiable people in our database (structured search) or enough live-indexed profiles (natural-language search) — you'll get however many genuinely qualify, not padded results to hit the number.
- **Natural-language matching is keyword-based, not identity-verified.** A result can occasionally reflect a past role or bio mention rather than someone's current primary title — we filter aggressively on location and role, but this mode doesn't carry the same freshness-check guarantee structured search does.
- **Email lookup is best-effort, structured search only.** Not every result will resolve to a found email, even on the Email tier — we only return one when we can independently confirm it, never a guess. Not available at all for natural-language search yet.
- **Freshness is "checked," not "live real-time," for structured search.** A result confirmed within the last 30 days is served from that check rather than re-verified on every single request. Natural-language search results are fetched live on every run instead.

### Who this is for

- **SDR and outbound sales teams** who need current contacts, not a list that's half wrong by the time they start calling.
- **Recruiters** sourcing candidates who are confirmed to still hold the role/title they're being searched for.
- **RevOps and lead-enrichment teams** refreshing existing CRM records against a live check rather than re-buying a static export.
- **Agencies** running outbound campaigns for clients where bounce and "no longer there" rates directly hurt deliverability and reputation.
- **Market researchers** needing an accurate current headcount/role snapshot for a company or region, not a historical one.

# Actor input Schema

## `query` (type: `string`):

Describe who you're looking for in plain English, e.g. "Senior software engineers in Bangalore, MERN stack, open to work" or "HR heads in Pune I could sell recruiting software to". When set, this replaces Job title/City/Industry below — those are ignored. Leave blank to use the structured fields instead.

## `title` (type: `string`):

Job title or role to search for, e.g. "Product Manager". Supports partial/keyword matching. Ignored if Natural-language search is set.

## `city` (type: `string`):

Exact city name to filter by, e.g. "Chennai". Optional — leave blank to search all locations. Ignored if Natural-language search is set.

## `industry` (type: `string`):

Filter candidates by industry. Optional. Ignored if Natural-language search is set.

## `targetCount` (type: `integer`):

How many verified, confirmed people you want back. We keep checking candidates until we hit this number or run out of matches — you're never charged for a candidate that didn't pan out.

## `includeEmail` (type: `boolean`):

Attempt verified email lookup for every result. Charged at the Email tier rate ($12/1,000 vs $6/1,000). Not yet available for Natural-language search — ignored (and charged at the no-email rate) when Natural-language search is set.

## Actor input object example

```json
{
  "targetCount": 100,
  "includeEmail": false
}
```

# Actor output Schema

## `results` (type: `string`):

Every confirmed, freshness-checked person matching your search, with optional verified email.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("clura/verified-linkedin-people-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("clura/verified-linkedin-people-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 '{}' |
apify call clura/verified-linkedin-people-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,clura/verified-linkedin-people-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/939rDceR2LdcFK5Hg/builds/gNN5qahpeSVqwkJDw/openapi.json