# LinkedIn Profile Search Scraper (No Cookies) (`chirpy_polygon/linkedin-profile-search-scraper-no-cookies`) Actor

Search LinkedIn profiles by keyword, job title, location, company and school. Export name, headline, job title, company, location and profile URL with no cookies or login.

- **URL**: https://apify.com/chirpy_polygon/linkedin-profile-search-scraper-no-cookies.md
- **Developed by:** [Bhojraj Pilaniya](https://apify.com/chirpy_polygon) (community)
- **Security:** Full permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 profile 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?

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 Profile Search Scraper (No Cookies)

Search LinkedIn profiles by keyword, current job title, location, current or past company, and school. **No LinkedIn login, cookies, or account required.**

Export clean, deduplicated profile records for recruiting, sales prospecting, market research and workflow automation.

This Actor is unofficial and is not affiliated with LinkedIn.

### What you get

- Full name
- Headline
- Current job title
- Current company name and LinkedIn URL
- Location
- LinkedIn profile URL
- Profile picture URL
- Premium / open-profile flags
- Deduplicated records

### Popular use cases

- Find decision makers by role and location (e.g. `Head of Marketing` in `United Kingdom`)
- Build prospect lists from a target employer
- Recruiting sourcing by title, location and school
- Alumni or past-employer research
- Job-change triggers (`Recently Changed Jobs Only`)
- Feed profiles into n8n, Make, Zapier, Google Sheets, Airtable or a CRM

### Why this Actor

- No cookies or LinkedIn login needed
- Combine free-text search with precise title/company/school filters
- Optional job-change and recent-activity filters for timely outreach
- Deduplicates profiles automatically
- Clean normalized schema, ready for sheets and CRMs

### Input

| Field | Description |
| --- | --- |
| Search Query | Free-text LinkedIn search, e.g. Founder, Marketing Manager |
| Current Job Titles | Precise role filter, e.g. Software Engineer |
| Locations | Full location names, e.g. United Kingdom, United States |
| Current Companies | Full LinkedIn company URLs |
| Past Companies | Full LinkedIn company URLs |
| Schools | e.g. Stanford University |
| Recently Changed Jobs Only | Profiles that changed jobs in the last 90 days |
| Recently Posted on LinkedIn Only | Profiles active in the last 30 days |
| Maximum Profiles | Cap on collected profiles. Keep low for the first run |

### Quick start

1. Enter a search query or at least one current job title.
2. Optionally add a location such as `India`.
3. Keep `Maximum Profiles` at 25 for the first run.
4. Run, inspect the profile URLs, then increase the limit.

### Example input

```json
{
  "currentJobTitles": ["Head of Marketing"],
  "locations": ["India"],
  "maxProfiles": 25
}
```

### Output example

```json
{
  "name": "Jane Doe",
  "headline": "Head of Marketing at Example Company",
  "jobTitle": "Head of Marketing",
  "companyName": "Example Company",
  "companyUrl": "https://www.linkedin.com/company/example/",
  "location": "Mumbai, Maharashtra, India",
  "profileUrl": "https://www.linkedin.com/in/example/",
  "isPremium": false,
  "isOpenProfile": false
}
```

### Pricing and total cost

- This Actor charges a fixed price **per saved profile** (see the Pricing tab for the current rate and plan discounts).
- It runs a paid no-cookie data source underneath. That source charges per profile **and per search page**, and those source charges are passed through and disclosed separately.
- Because search pages are charged by the source, very broad queries with a high profile limit cost more. Start small and increase gradually.
- A small Actor-start fee can apply even when no profile is saved.
- Dry Run writes a sample row only and does not trigger a result charge.

### Limits and result interpretation

- Results reflect publicly visible LinkedIn profiles at the time of the run.
- Location matching is fuzzy: use full country names (`United Kingdom`, `United States`).
- Very broad queries can return fewer unique profiles than requested.
- A `SUCCEEDED` run means the run finished. Always inspect the dataset before importing.

### Legal and platform note

Use this Actor responsibly and only for lawful purposes. Review LinkedIn terms and applicable privacy/data protection rules for your use case.

# Actor input Schema

## `dryRun` (type: `boolean`):

Preview only; returns a sample row instead of live data. No result event is intended; an Actor-start fee can still apply.

## `searchQuery` (type: `string`):

Free-text LinkedIn profile search, e.g. Founder, Marketing Manager, John Doe. Supports search operators.

## `currentJobTitles` (type: `array`):

Filter by current job title, e.g. Software Engineer. Use this for precise role targeting.

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

Filter by LinkedIn location. Use full names, e.g. United Kingdom (not UK), United States.

## `currentCompanies` (type: `array`):

Filter by current employer. Provide full LinkedIn company URLs.

## `pastCompanies` (type: `array`):

Filter by past employer. Provide full LinkedIn company URLs.

## `schools` (type: `array`):

Filter by school, e.g. Stanford University.

## `recentlyChangedJobs` (type: `boolean`):

Only profiles that changed jobs in the last 90 days.

## `recentlyPostedOnLinkedIn` (type: `boolean`):

Only profiles that posted on LinkedIn in the last 30 days.

## `maxProfiles` (type: `integer`):

Maximum number of profiles to collect. Keep this low for the first run.

## `sourceMaxTotalChargeUsd` (type: `number`):

Advanced safety cap for the underlying data collection run. Leave empty for an automatic cap based on your profile limit.

## `sourceWaitSecs` (type: `integer`):

Maximum time to wait for the underlying data collection run.

## Actor input object example

```json
{
  "dryRun": false,
  "recentlyChangedJobs": false,
  "recentlyPostedOnLinkedIn": false,
  "maxProfiles": 25,
  "sourceWaitSecs": 1800
}
```

# Actor output Schema

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

No description

## `runSummary` (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 = {
    "dryRun": false,
    "maxProfiles": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("chirpy_polygon/linkedin-profile-search-scraper-no-cookies").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 = {
    "dryRun": False,
    "maxProfiles": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("chirpy_polygon/linkedin-profile-search-scraper-no-cookies").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 '{
  "dryRun": false,
  "maxProfiles": 25
}' |
apify call chirpy_polygon/linkedin-profile-search-scraper-no-cookies --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,chirpy_polygon/linkedin-profile-search-scraper-no-cookies"
        }
    }
}
```

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/AsHbau3XNnbCkuIJ0/builds/bfnOsdfSJwYIFGqJx/openapi.json