LinkedIn Profile Scraper – No Login, Public Data
Pricing
$20.99/month + usage
LinkedIn Profile Scraper – No Login, Public Data
Extract public LinkedIn profile data without login. Name, headline, company, location, about, skills. Auth wall detection + Google Knowledge Panel fallback. Residential proxy required. Bulk usernames or full names supported. JSON/CSV.
Pricing
$20.99/month + usage
Rating
0.0
(0)
Developer
Scrape Pilot
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
13 hours
Issues response
4 days ago
Last modified
Categories
Share
👔 LinkedIn Profile Scraper v3 — Public Data, No Login, Auth Wall Bypass
Extract public LinkedIn profile data without logging in.
Fetches name, headline, current position, company, location, connections count, about section, experience summary, education, and skills. Uses multiple URL variants (no‑www, www, mobile) to avoid auth walls. When blocked, falls back to Google Knowledge Panel extraction. Residential proxy required (LinkedIn blocks datacenter IPs).
💡 What is LinkedIn Profile Scraper v3?
LinkedIn Profile Scraper v3 is a professional Apify actor that extracts publicly visible information from LinkedIn profiles – no account, no login, no cookies. It works around LinkedIn’s soft authentication walls by:
- Trying multiple URL formats:
linkedin.com/in/{username},www.linkedin.com/in/{username}, andm.linkedin.com/in/{username}. - Detecting “Welcome to your professional community” auth walls by checking OG title and HTML content.
- Falling back to Google Knowledge Panel extraction when all LinkedIn pages are blocked.
- Supporting full name input – automatically searches Google to find the correct LinkedIn username.
The result is a clean JSON object with the profile data that is publicly accessible, plus a search_status field indicating whether the data is complete (FOUND), partial (PARTIAL from Google KP), or blocked (AUTH_REQUIRED).
📦 What Data Can You Extract?
| 🧩 Data Type | 📋 Description |
|---|---|
| 👤 Name | Full name from the profile. |
| 🔗 Profile URL | LinkedIn profile URL (canonical). |
| 📌 Headline | Current title / tagline (e.g., “Chairman and CEO at Microsoft”). |
| 💼 Current Position | Job title (parsed from headline or meta). |
| 🏢 Company | Current employer. |
| 📍 Location | City, state, country (if public). |
| 👥 Connections | Number of connections (often shown as “500+” if high). |
| 📝 About | Summary / bio section (if public). |
| 📋 Experience Summary | First few experience entries (truncated). |
| 🎓 Education | Degrees and institutions (if public). |
| 🛠️ Skills | List of skills (when available in page). |
| 🔍 Search Status | FOUND, PARTIAL (Google KP), or AUTH_REQUIRED. |
| 🛡️ Data Quality | Public, Partial, or note. |
| ⏱️ Scraped At | ISO timestamp. |
⚙️ Key Features
- No Login Required – Uses only public web pages.
- Auth Wall Detection – Recognises LinkedIn login/signup prompts and switches strategy.
- Multiple URL Fallbacks – Tries
linkedin.com/in,www, and mobile versions. - Google Knowledge Panel Fallback – Extracts profile data from Google search results when LinkedIn blocks.
- Full Name Support – Enter a person’s name (e.g., “Satya Nadella”) and the actor will find their LinkedIn username via Google.
- Residential Proxy Ready – LinkedIn aggressively blocks datacenter IPs; residential proxies are required.
- Bulk Processing – Scrape up to 20+ profiles in one run.
- Keyword Filtering – Filter results by keyword in headline, company, or about text.
- Clean JSON Output – Ready for CRM, lead enrichment, or analytics.
📥 Input Parameters
The actor accepts a JSON object with the following fields:
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
profile_urls | array or string | No | – | List of LinkedIn usernames or full profile URLs. Can be newline‑separated string. |
profile_url | string | No | – | Single username or URL (alternative to profile_urls). |
username | string | No | – | Same as above. |
keyword | string | No | – | Filter results by keyword in headline/company/about. |
max_results | integer | No | 20 | Maximum number of profiles to process. |
proxyConfiguration | object | No | – | Apify proxy configuration. Residential proxies are required. |
Note: You can provide either a LinkedIn username (e.g.,
satyanadella), a full LinkedIn URL (e.g.,https://linkedin.com/in/satyanadella/), or a person’s name (e.g.,Satya Nadella). The actor will handle all formats.
Example Input (Usernames)
{"profile_urls": ["satyanadella", "sundarpichai", "tim-cook"],"max_results": 10,"proxyConfiguration": {"useApifyProxy": true,"apifyProxyGroups": ["RESIDENTIAL"]}}
Example Input (Full Name)
{"profile_url": "Elon Musk","keyword": "Tesla","proxyConfiguration": {"useApifyProxy": true,"apifyProxyGroups": ["RESIDENTIAL"]}}
📤 Output Fields
Each profile returns an object. Fields may be omitted if not publicly available.
| Field | Type | Description |
|---|---|---|
name | string | Full name. |
profile_url | string | LinkedIn profile URL. |
url_used | string | Which URL variant succeeded (e.g., https://linkedin.com/in/...). |
headline | string | Current title / tagline. |
current_position | string | Job title (extracted). |
company | string | Current employer. |
company_url | string | LinkedIn company page URL (if found). |
location | string | City, state, country. |
connections | string | Connection count (e.g., 500+). |
about | string | Summary / bio. |
experience_summary | string | First few experience entries (truncated). |
education | string | Degrees and institutions. |
skills | array | List of skills (if available). |
search_status | string | FOUND, PARTIAL (from Google KP), or AUTH_REQUIRED. |
data_quality | string | Public, Partial, or note. |
security | string | No Login Required. |
source_input | string | Original input value. |
scraped_at | string | ISO timestamp. |
Example Output (Successful)
[{"name": "Satya Nadella","profile_url": "https://www.linkedin.com/in/satyanadella","url_used": "https://linkedin.com/in/satyanadella/","headline": "Chairman and CEO at Microsoft","current_position": "Chairman and CEO","company": "Microsoft","company_url": "https://www.linkedin.com/company/microsoft","location": "Redmond, Washington, United States","connections": "500+","about": "Satya Nadella is the Chairman and CEO of Microsoft...","experience_summary": "Chairman and CEO at Microsoft (2014-present); Executive Vice President at Microsoft (2000-2014)","education": "MS in Computer Science - University of Wisconsin-Milwaukee; MBA - University of Chicago Booth School of Business","skills": ["Leadership", "Cloud Computing", "AI", "Strategy"],"search_status": "FOUND","data_quality": "Public","security": "No Login Required","source_input": "satyanadella","scraped_at": "2026-04-12T12:00:00Z"}]
Example Output (Partial – Google Knowledge Panel)
[{"name": "Satya Nadella","profile_url": "https://www.linkedin.com/in/satyanadella","headline": "Chairman and CEO at Microsoft","company": "Microsoft","about": "Indian-American business executive...","connections": "500+","search_status": "PARTIAL","data_source": "Google Knowledge Panel","source_input": "Satya Nadella","scraped_at": "2026-04-12T12:00:00Z"}]
Example Output (Blocked)
[{"name": null,"profile_url": "https://www.linkedin.com/in/privateprofile","search_status": "AUTH_REQUIRED","note": "LinkedIn requires login. Try again with a different RESIDENTIAL proxy IP.","source_input": "privateprofile","scraped_at": "2026-04-12T12:00:00Z"}]
🛠 How to Use on Apify
- Create a task with this actor.
- Provide input – one or more LinkedIn usernames, URLs, or full names.
- Enable residential proxies – required (LinkedIn blocks datacenter IPs). Select
RESIDENTIALproxy group. - Run – the actor will try multiple strategies and return results.
- Export – download results as JSON, CSV, or Excel.
Running via API
curl -X POST "https://api.apify.com/v2/acts/your-username~linkedin-profile-scraper/runs" \-H "Content-Type: application/json" \-H "Authorization: Bearer YOUR_API_TOKEN" \-d '{"profile_urls": ["satyanadella", "sundarpichai"],"proxyConfiguration": {"useApifyProxy": true,"apifyProxyGroups": ["RESIDENTIAL"]}}'
🎯 Use Cases
- Lead Enrichment – Add LinkedIn profile data to your CRM (name, company, title).
- Sales Intelligence – Prospect decision makers by extracting their current roles.
- Recruitment – Quickly gather public profile information of potential candidates.
- Competitive Research – Monitor leadership changes at competitor companies.
- Data Enrichment – Augment existing datasets with LinkedIn public fields.
- Investor Research – Background checks on startup founders.
❓ Frequently Asked Questions
Q1. Do I need a LinkedIn account?
No. The actor does not require login. It uses only public pages.
Q2. Why do I need residential proxies?
LinkedIn aggressively blocks datacenter IP addresses (AWS, Google Cloud, etc.). Residential proxies mimic real users and are essential to avoid 999 or 403 errors.
Q3. What does search_status: PARTIAL mean?
The actor could not fetch the full LinkedIn page (likely blocked), but it extracted some information from Google Knowledge Panel (name, headline, company, about). This data is usually accurate but less detailed.
Q4. Why is connections always 500+?
For high‑profile profiles, LinkedIn often shows “500+ connections” without the exact number. The actor returns that string as is. For lower‑connection profiles, the exact number may appear.
Q5. Can I extract email addresses or phone numbers?
No. Those are not public on LinkedIn.
Q6. What if I enter a full name (e.g., “Elon Musk”)?
The actor will Google site:linkedin.com/in "Elon Musk" to find the correct username. If found, it will then scrape that profile. If not found, it will fall back to Google Knowledge Panel.
Q7. How accurate is the data from Google Knowledge Panel?
It is usually accurate for public figures (CEOs, founders, famous people). For less known individuals, the panel may be missing.
Q8. Why does the actor sometimes return AUTH_REQUIRED?
Even with residential proxies, some profiles are set to “private” or require login to view any information. The actor cannot bypass that.
📝 Technical Notes
- Dependencies:
curl_cffi(for TLS fingerprint spoofing) andBeautifulSoup4. Both are bundled. - Auth wall detection: Looks for phrases like “welcome to your professional community”, “sign in to linkedin”, etc. in the first 5000 chars and OG title.
- Fallback order:
https://linkedin.com/in/{username}/(no‑www)https://www.linkedin.com/in/{username}/(www)https://m.linkedin.com/in/{username}/(mobile)- Google Knowledge Panel extraction
- Proxy: The actor uses
Actor.create_proxy_configuration()to get the proxy URL. You must selectRESIDENTIALgroup. - Rate limiting: The actor adds a 2–4 second random delay between profiles to avoid being blocked.
- Error handling: If a profile fails completely, the actor returns a minimal object with
search_status: AUTH_REQUIREDand continues.
🔍 SEO Keywords
LinkedIn scraper, LinkedIn profile extractor, LinkedIn public data, LinkedIn no login, LinkedIn auth wall bypass, Google Knowledge Panel LinkedIn, LinkedIn lead generation, Apify LinkedIn actor, sales intelligence tool, LinkedIn username finder