
Linkedin Profile Full Sections Scraper - No Cookies
Pricing
$10.00 / 1,000 results
Go to Store


Linkedin Profile Full Sections Scraper - No Cookies
Scrape complete LinkedIn profile data including work experience, education history, certifications, and location details. Get structured information from any public LinkedIn profile using their username.
5.0 (4)
Pricing
$10.00 / 1,000 results
7
Total users
124
Monthly users
82
Runs succeeded
>99%
Issues response
1.3 hours
Last modified
a day ago
neal-mohan is always included as input
Closed
toribio142857 opened this issue
3 days ago
No matter which linkedin username i use the actor includes neal-mohan
as input automatically and the response is for that linkedin user.
build 0.1.19
2025-07-01T09:37:43.966Z ACTOR: Pulling Docker image of build 9QKgqOPs2p6jzGLWW from registry.2025-07-01T09:37:43.969Z ACTOR: Creating Docker container.2025-07-01T09:37:44.125Z ACTOR: Starting Docker container.2025-07-01T09:37:45.092Z INFO System info {"apifyVersion":"3.2.6","apifyClientVersion":"2.10.0","crawleeVersion":"3.12.0","osType":"Linux","nodeVersion":"v20.19.2"}2025-07-01T09:37:45.191Z Input received: {2025-07-01T09:37:45.193Z "username": "https://www.linkedin.com/in/micaelavillalobos/",2025-07-01T09:37:45.193Z "usernames": [2025-07-01T09:37:45.194Z "neal-mohan"2025-07-01T09:37:45.194Z ]2025-07-01T09:37:45.195Z }2025-07-01T09:37:45.195Z Processing 1 profile(s)...

3 days ago
should work now. But the actor is updated to support list of input, it's better to use "usernames" only moving forward