LinkedIn Profile Scraper - No Cookies, Pay Per Result
Pricing
from $0.30 / 1,000 results
LinkedIn Profile Scraper - No Cookies, Pay Per Result
Scrape LinkedIn public profiles without login or cookies. Extracts name, headline, current and past positions, education, about section, follower count, and articles.
Pricing
from $0.30 / 1,000 results
Rating
0.0
(0)
Developer
Thirdwatch
Maintained by CommunityActor stats
0
Bookmarked
127
Total users
17
Monthly active users
13 days ago
Last modified
Categories
Share
LinkedIn Profile Scraper
Thirdwatch portfolio: 5K users across 88 public Actors, 2M+ records delivered, and >99% run success. Explore all Thirdwatch Actors.
Scrape structured data from public LinkedIn profile URLs and usernames. Get names, headlines, current roles, companies, locations, education, profile summaries, follower counts, profile photos, and recent articles without using a LinkedIn account or cookies.
Value proposition
LinkedIn profile URLs are common in CRMs, applicant lists, conference exports, Google results, and prospecting workflows, but they are not directly usable as clean structured data. This actor turns public LinkedIn profile URLs into JSON records that can be loaded into a CRM, ATS, enrichment pipeline, spreadsheet, or internal research tool.
Use it when you need a reliable profile-enrichment step for:
- Sales prospecting and SDR research
- RevOps and CRM enrichment
- Recruiting and candidate research
- Founder, executive, or investor research
- Talent movement and market-mapping workflows
What's new
- No-login profile enrichment: scrape public
/in/{username}profile pages without cookies or a paid LinkedIn seat. - Flexible URL input: accepts full profile URLs,
/in/...paths, or plain usernames. - CRM-friendly fields: current title, current company, location, headline, education, and profile URL are returned as structured fields.
- Pairs with company discovery: use LinkedIn Company Employees Scraper to find profile URLs, then this actor to enrich them.
What data you get
| Field | Description |
|---|---|
name | Full name |
headline | Public professional headline |
current_titles | Current visible job titles |
current_companies | Current companies with start dates when available |
past_positions | Previous positions with company, title, and date range when available |
education | Schools, degrees, and fields of study when available |
about | Public About or summary section |
location | Public profile location |
profile_photo_url | Profile image URL |
followers_count | Public follower count |
profile_url | Canonical LinkedIn profile URL |
articles | Recent public articles when available |
Quick-start input examples
1. Enrich one profile URL
{"profileUrls": ["https://www.linkedin.com/in/satyanadella/"],"maxProfiles": 1}
2. Enrich usernames and profile paths
{"profileUrls": ["satyanadella", "/in/williamhgates", "https://www.linkedin.com/in/example/"],"maxProfiles": 3}
3. Batch-enrich CRM records
{"profileUrls": ["https://www.linkedin.com/in/profile-one/","https://www.linkedin.com/in/profile-two/","https://www.linkedin.com/in/profile-three/"],"maxProfiles": 100}
Input parameters
| Parameter | Required | Default | Description |
|---|---|---|---|
profileUrls | Yes | - | LinkedIn profile URLs, /in/... paths, or usernames. |
maxProfiles | No | 5 | Maximum number of profiles to process from the input list. |
maxConcurrency | No | 5 | Profiles resolved in parallel; maximum 10. |
proxyConfiguration | No | Residential fallback | Direct HTTP and free search run first. The configured proxy is used only after those paths fail. |
preferFullProfile | No | false | Try paid residential recovery before accepting a partial search result. |
Sample output snippet
{"name": "Satya Nadella","headline": "Chairman and CEO at Microsoft","current_titles": ["Chairman and CEO"],"current_companies": [{"name": "Microsoft","start_date": "2014"}],"past_positions": [{"name": "EVP, Cloud and Enterprise","company": "Microsoft","start_date": "2011","end_date": "2014"}],"education": [{"school": "University of Wisconsin-Milwaukee","degree": "MS","field": "Computer Science"}],"about": "Public profile summary text...","location": "Redmond, Washington","followers_count": 10000000,"profile_url": "https://www.linkedin.com/in/satyanadella/"}
Use cases
- CRM enrichment: update contact records with current title, company, location, headline, and canonical profile URL.
- Sales prospecting: enrich LinkedIn URLs from search exports, conference lists, founder directories, or account research.
- Recruiting research: summarize public candidate backgrounds before outreach or screening.
- Investor research: profile founders, operators, and executive teams across a portfolio or market segment.
- Data pipelines: normalize LinkedIn usernames and URLs into structured fields for downstream workflows.
Pricing examples
This actor uses path-aware pay-per-event pricing. Ordinary direct profiles cost $0.0012-$0.0003 each, depending on your Apify tier. A paid fallback is charged only after it successfully recovers a profile that the direct path could not return.
| Path | FREE | GOLD |
|---|---|---|
| Direct HTTP / free search | $1.20 / 1,000 | $0.30 / 1,000 |
| Rendered-search recovery | +$4.00 / 1,000 recovered | +$4.00 / 1,000 recovered |
| Residential recovery | +$12.00 / 1,000 recovered | +$12.00 / 1,000 recovered |
Failures are not pushed to the dataset, so they do not incur a result or fallback event.
Limitations
- Only public profile data is returned. Restricted profiles may return limited or no data.
- Skills, endorsements, recommendations, and certifications are not returned when they require login-only access.
- Some fields are optional because LinkedIn profiles vary by user privacy settings and public visibility.
- The actor does not create LinkedIn sessions, send messages, connect with users, or access private LinkedIn data.
FAQ
Do I need a LinkedIn account or cookies?
No. The actor uses public profile URLs and does not require a logged-in LinkedIn session.
What input formats work?
Full URLs, /in/... paths, and plain usernames are accepted when they resolve to public LinkedIn profile pages.
Can I enrich profiles found through Google or another scraper?
Yes. If the result resolves to a public LinkedIn /in/{username} profile, it can be used as input.
How many profiles can I scrape in one run?
The actor supports batch input. Use maxProfiles to control how many profiles from your input list are processed in a run.
Is the data fresh?
Data is pulled at run time from public profile pages, subject to what LinkedIn makes publicly visible.
Support and custom builds
Need a custom LinkedIn enrichment flow, CRM mapper, webhook integration, or combined company-employee plus profile-enrichment actor? Contact Thirdwatch through Apify or visit thirdwatch.dev for custom builds.
Pairs well with LinkedIn Company Employees Scraper to find profiles and LinkedIn Jobs Scraper to connect people data with hiring signals.
Use cases and recipes
Step-by-step guides on thirdwatch.dev/blog:
- Build a Candidate Shortlist from LinkedIn Profiles (2026)
- Enrich Your CRM with LinkedIn Profile Data (2026 Guide)
- Find Decision-Makers by Title and Company on LinkedIn (2026)
- Scrape LinkedIn Profiles Without Login at Scale (2026)
Last verified: 2026-07