# LinkedIn Event Attendees Extractor (`fanndev/linkedin-event-attendees-extractor`) Actor

Turn a LinkedIn event into a list of the people who registered for it - an audience that has already raised its hand on your topic. Requires your own li\_at session cookie: LinkedIn shows logged-out visitors no event page at all.

- **URL**: https://apify.com/fanndev/linkedin-event-attendees-extractor.md
- **Developed by:** [Faisal Ahdan naufal](https://apify.com/fanndev) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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 Event Attendees Extractor

People who registered for an event about your category have already raised their hand on the topic. This actor turns a LinkedIn event URL into that list: names, headlines and profile links, ready for a connection request or a cold email that can honestly open with "I saw you signed up for…".

### Read this before you buy

**This actor requires your own `li_at` session cookie.** That is not a design preference. LinkedIn redirects `/events/{id}` straight to the login wall for anonymous visitors — there is no guest view of an event at all, let alone its attendees. Verified 2026-09-20.

**And a cookie is not always enough.** Two limits are LinkedIn's, and no scraper gets past them:

1. **Attendee lists are permissioned.** LinkedIn serves the roster only to accounts it decides may see it — typically the organiser, and attendees of events whose organiser left the list visible. A cookie for an account with no relationship to the event will often read the event fine and return **no attendees**.
2. **Many events publish a count but withhold the names.** You will see `eventAttendeeCount: 340` and get zero `ATTENDEE` rows.

When either happens, this actor writes an `attendee_list_withheld` notice explaining which case it hit, reports the count it *did* get, and **exits successfully**. It does not fail, and it does not hand you a silent empty dataset that looks like a bug.

If your use case is "scrape any event I can find a link to", this will disappoint you more often than not. If it is "extract the roster from events I organise or attend", it does exactly that.

### Getting your cookie

Sign in to LinkedIn in your browser → DevTools → Application → Cookies → `www.linkedin.com` → copy the **value** of `li_at` → paste into `sessionCookie`.

This actor never asks for your password and never signs in on your behalf. It sends the cookie you pasted, in that run, and nowhere else.

**The honest risk.** Scraping while signed in breaches LinkedIn's User Agreement, and LinkedIn does restrict accounts for it. Three things reduce the odds, and this actor does or exposes all three:

- **Use a residential proxy in your own country.** This is the default here, and it matters: LinkedIn weighs the exit IP against where your account normally signs in, and an Apify datacenter IP is exactly the mismatch that flags a session. The actor warns in the log if you turn the proxy off.
- **Keep the caps low.** `maxAttendees` defaults to 1,000 and `maxAttendeesPerEvent` to 200. Long, greedy runs are what abuse scoring reacts to.
- **Leave the delays alone.** The 3–8 second randomised gap is not padding — with a cookie in play it is also what keeps the run looking like a person rather than a script.

Use an account you would not mind losing.

### Input

```json
{
  "eventUrls": [
    "https://www.linkedin.com/events/my-webinar-7178068349686366208/",
    "7178068349686366208"
  ],
  "sessionCookie": "AQEDAT...",
  "maxAttendeesPerEvent": 200,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}
```

Full event links and bare 19-digit event ids both work.

### Output

One `EVENT` row per event — name, description, organiser, start time and the attendee count LinkedIn reports — and one `ATTENDEE` row per person.

```json
{
  "recordType": "ATTENDEE",
  "fullName": "Jane Doe",
  "firstName": "Jane",
  "lastName": "Doe",
  "headline": "Head of Demand Generation at Acme",
  "profileUrl": "https://www.linkedin.com/in/janedoe",
  "location": "Berlin, Germany",
  "attendanceStatus": "REGISTERED",
  "eventName": "Scaling B2B Pipeline in 2026",
  "eventAttendeeCount": 340
}
```

`eventAttendeeCount` sits on every attendee row on purpose: compare it against your row count and you can always see how much of the roster LinkedIn actually gave you, rather than assuming you got all of it.

Names are split into `firstName` / `lastName` with pronouns, emoji hiring frames and credential suffixes (PhD, MBA, CFA) stripped — a mail merge that greets someone as "Hi Dr, PhD" is worse than no personalisation. Profile URLs have tracking parameters removed and country subdomains folded onto `www`, so your CRM de-duplicates correctly.

### No email addresses

This actor does not guess email addresses. A fabricated `first.last@company.com` that bounces costs you your sending domain's reputation, which is a far more expensive mistake than a missing column. Take the name and headline and put them through a verification tool that actually checks.

### Before you use this on people

These are real people, and in the EU, UK and similar jurisdictions they carry data-protection rights even though they registered for a public event. Legitimate interest is a defensible basis for B2B outreach; it is not a blank cheque. Say where you got the data when you make contact, honour opt-outs, and do not mix event attendees into a consumer marketing list. That is your obligation as the data controller, not the actor's.

### Related actors

- **LinkedIn Post Engagers Scraper** — commenters on a post, no cookie needed for most of it.
- **LinkedIn Company Employee Role Filter** — decision makers inside a target account.

# Actor input Schema

## `eventUrls` (type: `array`):

LinkedIn events to read. A full linkedin.com/events/... link or a bare 19-digit event id both work.

## `startUrls` (type: `array`):

The same event links in the request-list format, for callers that already keep one.

## `sessionCookie` (type: `string`):

Mandatory. LinkedIn redirects /events/ straight to the login wall for logged-out visitors - there is no guest view of an event at all, let alone its attendees. To get it: sign in to LinkedIn in your browser, open DevTools > Application > Cookies > www.linkedin.com, copy the VALUE of li\_at. This actor never asks for your password and never signs in on your behalf. Scraping while signed in breaches LinkedIn's User Agreement and accounts do get restricted - use one you are willing to risk, pair it with a residential proxy, and keep the caps low. Without a cookie the run still finishes successfully and explains itself in the dataset.

## `maxAttendeesPerEvent` (type: `integer`):

Cap per event. Keeping this modest is the best protection for your session cookie - long, greedy runs are what LinkedIn's abuse scoring reacts to.

## `maxAttendees` (type: `integer`):

Overall ceiling across every event.

## `minDelaySeconds` (type: `integer`):

LinkedIn answers request bursts with HTTP 999 and a near-empty page. With a session cookie in play the randomised gap does double duty: it keeps the run under the rate gate and keeps it looking like a person rather than a script.

## `maxDelaySeconds` (type: `integer`):

The ceiling of the randomised gap. Raise both bounds if the log shows rate-gate warnings.

## `exportFormats` (type: `array`):

Besides the dataset, write ready-made files into this run's key-value store.

## `proxyConfiguration` (type: `object`):

This actor always runs with your session cookie, so use RESIDENTIAL in your own country. LinkedIn scores the exit IP against where your account normally signs in, and an Apify datacenter IP is precisely the mismatch that gets a session flagged.

## Actor input object example

```json
{
  "eventUrls": [
    "https://www.linkedin.com/events/7178068349686366208/"
  ],
  "maxAttendeesPerEvent": 200,
  "maxAttendees": 1000,
  "minDelaySeconds": 3,
  "maxDelaySeconds": 8,
  "exportFormats": [],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

One EVENT row per event, one ATTENDEE row per person, plus NOTICE rows when LinkedIn withheld the roster and ERROR rows on failure.

# 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 = {
    "eventUrls": [
        "https://www.linkedin.com/events/7178068349686366208/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("fanndev/linkedin-event-attendees-extractor").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 = { "eventUrls": ["https://www.linkedin.com/events/7178068349686366208/"] }

# Run the Actor and wait for it to finish
run = client.actor("fanndev/linkedin-event-attendees-extractor").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 '{
  "eventUrls": [
    "https://www.linkedin.com/events/7178068349686366208/"
  ]
}' |
apify call fanndev/linkedin-event-attendees-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,fanndev/linkedin-event-attendees-extractor"
        }
    }
}
```

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/rMC0hcUO0CfSSsEUI/builds/ET8F720P2K6l1wcPb/openapi.json