LinkedIn Event Attendees Extractor
Pricing
from $1.00 / 1,000 results
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.
LinkedIn events to read. A full linkedin.com/events/... link or a bare 19-digit event id both work.
The same event links in the request-list format, for callers that already keep one.
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.
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.
Overall ceiling across every event.
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.
The ceiling of the randomised gap. Raise both bounds if the log shows rate-gate warnings.
Besides the dataset, write ready-made files into this run's key-value store.
[]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.
{ "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ]}