Linkedin Sales Navigator Scraper
Pricing
Pay per event
Go to Apify Store
Linkedin Sales Navigator Scraper
A powerful tool designed to extract detailed leads information from a sales navigator URL — without the need for cookies or login.
Pricing
Pay per event
Rating
5.0
(2)
Developer
FreshData
Maintained by Community
Actor stats
13
Bookmarked
392
Total users
2
Monthly active users
13 hours
Issues response
2 days ago
Last modified
Categories
Share
🚀 LinkedIn Sales Navigator Scraper
The LinkedIn Sales Navigator Scraper is a powerful tool designed to extract detailed lead information from a Sales Navigator URL — without the need for cookies or login. It provides both personal and company-related insights.
✨ Features
-
👤 Personal Profile Extraction
Retrieve names, current title, about section, and more. -
🍪 No Cookies Required
The scraper works without any LinkedIn login or cookies — simplifying setup and execution. -
🏢 Company Information
Automatically collects data such as company name, company_id.
📌 How It Works
I made a little tool to help you test and use my actor quickly and easily: https://drive.google.com/file/d/1cWpDkqesMYBvntbH9hZGhxofpOSIi68E/view?usp=sharing. All the instructions you need are already in the folder.
The actor supports two main flows:
- 🔍 Init Search — Start a new search using your
sales_url - 📥 Fetch Results — Retrieve results of an existing search using
request_id
You can run either flow independently, depending on your input.
📥 Inputs
| Parameter | Type | Required | Description |
|---|---|---|---|
sales_url | string | optional | Sales Navigator search URL for initializing a search |
limit | integer | optional | Max items to queue for a new search (default: 25; maximum: 2500) |
request_id | string | optional | Existing search ID to check/fetch results |
page | integer | optional | Page number when fetching results (default: 1; maximum: 25) |
⚠️ Each page returns a maximum of 100 leads/profiles.
🔍 Flow 1 — Init Search
- Provide
sales_url(and optionallylimit). - You will receive:
request_id— use this for fetching results later.message— confirmation note (expect results in ~5–10 minutes).
- Billing: Charges the
init_searchevent once on success. ($0.5 / 1 search)
Example Input
Example Output
📥 Flow 2 — Check Status & Fetch Results
This flow is used after you already have a request_id from Flow 1.
🔎 Step 1 — Provide Your Request ID
- In your input, set
request_idto the value you received from Flow 1. - Optionally, include
pageto specify which page of results you want. - Default:
page = 1.
Example Input
⏳ Step 2 — Actor Checks Search Status
When you provide a request_id, the actor will:
- Check the status of the search related to your
request_id. - Tell you if your search is still processing.
Possible Status Values & What They Mean
| Status value | Meaning | What Happens Next? |
|---|---|---|
processing | The search is still running. Data is not ready yet. | Actor returns the status; you should wait and retry later. |
pending | The search has been queued but not started. | Actor returns the status; you should wait and retry later. |
- Recommended: Wait 5–10 seconds between each check to avoid unnecessary requests.
Example Output (still processing)
- If your search is completed: The actor will automatically proceed to Step 3 to fetch your results.
📦 Step 3 — Retrieve the Results
Data returned: A list of leads/profiles, with a maximum of 100 items per page.
Billing: The actor charges the fetch_results event with count = number_of_items_returned. ($0.01 / 1 results)
🔁 Step 4 — Paginate if Needed
Each page contains up to 100 results.
To fetch more, increase page in your next request.
Example:
Example Output (done + data)
