LinkedIn Profile Search Scraper (No Cookies)
Pricing
from $4.00 / 1,000 profile results
LinkedIn Profile Search Scraper (No Cookies)
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.
Pricing
from $4.00 / 1,000 profile results
Rating
0.0
(0)
Developer
Bhojraj Pilaniya
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
6 days ago
Last modified
Categories
Security
Full permissionsShare
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 MarketinginUnited 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
- Enter a search query or at least one current job title.
- Optionally add a location such as
India. - Keep
Maximum Profilesat 25 for the first run. - Run, inspect the profile URLs, then increase the limit.
Example input
{"currentJobTitles": ["Head of Marketing"],"locations": ["India"],"maxProfiles": 25}
Output example
{"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
SUCCEEDEDrun 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.