LinkedIn Sales Navigator Scraper (No Cookies)

Paste a Sales Navigator people-search URL. Get up to 1,000 profiles from that search as clean dataset rows.

From $0.55. 25 profiles, under a minute. $1.30 for 100. $10.30 for 1,000, in about 7 minutes. Input: one Sales Navigator people-search URL. Output: CSV / JSON / Excel. No emails or phones. You (or your client) need Sales Navigator to build the search and copy the URL. Nothing is connected to the actor: no login, no cookie, no extension.

No LinkedIn account to connect. No li_at cookie to paste. No browser extension. The scrape runs on LeadsFactory's managed LinkedIn accounts. LinkedIn profile and company data only. No email addresses, no phone numbers. See Getting emails.

One run, one dataset. Some no-cookie scrapers hand you a job ID and make you run a second actor to collect the rows. Here the profiles land in this run's dataset.

Who this is for

• Anyone who tried another Sales Navigator scraper and stopped at "paste your session cookie".
• Sales teams with a Sales Navigator subscription who want their search results in a spreadsheet instead of clicking "Save to list" 1,000 times.
• Agencies building lists from client-provided Sales Navigator filters.

Cookie-based scrapers are a little cheaper because you supply the account and carry the ban risk. This one does not ask.

Want a specific person at each company instead of a whole search? Use LinkedIn Decision Maker Finder: companies plus job titles in, AI-scored decision-makers out.

How the Sales Navigator scrape works

1. Build your people search in Sales Navigator. Filters, keywords, geography, headcount, anything Sales Navigator supports.
2. Copy the URL from the address bar once the results have loaded. See Getting the right URL.
3. Run the actor. It first counts the results in the search (free), then scrapes the first N profiles, where N is your maxProfiles.
4. Download the dataset as JSON, CSV or Excel, or pull it from the API.

Measured delivery time (real runs): 10 profiles in under a minute, 200 in about 2 minutes, 1,000 in about 7 minutes. Scraping on real accounts is paced to keep the accounts healthy, so large runs are not linear.

Getting the right URL

• ✅ https://www.linkedin.com/sales/search/people?query=(filters:List((type:CURRENT_TITLE,...))) — a loaded people search, URL contains query=.
• ❌ https://www.linkedin.com/sales/search/people?savedSearchId=12345678 — a saved-search link. Open it, wait for the results to load, then copy the full URL from the address bar.
• ❌ https://www.linkedin.com/sales/search/company?... — an account (company) search. People searches only in this version.
• ❌ https://www.linkedin.com/sales/lists/people/... — a lead list. Not supported; see the FAQ.
• ❌ https://www.linkedin.com/search/results/people/?keywords=... — regular LinkedIn search, not Sales Navigator.

Wrong URLs are rejected with a specific message before anything is charged.

What you pay, and when

Pay per event. No LeadsFactory subscription. Apify platform usage (compute, proxies) is included in these prices; you are not billed separately for it.

Event	Price	Charged when
Scrape started (scrape-started)	$0.30	Charged once per run, at the moment the first profiles are written to your dataset. Not charged when the search returns no results or when the scrape fails before delivering anything.
Profile delivered (dataset item)	$0.01	A profile row is written to your dataset.

The $0.30 start fee covers the managed account reserved for your scrape. It is only charged once profiles are actually delivered: a 0-result search or a scrape that breaks before delivering costs $0.00.

Worked examples:

Profiles delivered	Cost
25	$0.30 + $0.25 = $0.55
100	$0.30 + $1.00 = $1.30
500	$0.30 + $5.00 = $5.30
1,000 (maximum per run)	$0.30 + $10.00 = $10.30

What you can hold us to:

• A search with 0 results costs $0.00. The result count is checked before the scrape starts. Nothing is charged, including the start fee.
• A scrape that fails before delivering anything costs $0.00. The run ends failed and the start fee is not charged.
• An invalid URL, a saved-search link, an account-search link, or a request when the daily capacity is exhausted fails before any charge.
• A run that fails on our side before collecting any profile ends as failed, not as succeeded with an empty dataset.
• The start fee is charged together with the first profiles; beyond it, you are charged only for profiles actually written to your dataset.
• Set a maximum cost per run in the Apify Console. The actor stops cleanly at your budget and keeps everything collected so far. Worst case for any input is $0.30 + maxProfiles × $0.01, so $10.30 at the 1,000 maximum.

How this compares:

	This actor	Other no-cookie URL scrapers
100 profiles	$1.30	$1.00–$1.50
1,000 profiles	$10.30	$8.00–$10.50
Cookies from you	No	No
Runs to get results	1	1–2, depending on the actor
Profiles per run	1,000	up to 2,500

On price we are at market, not below it. Where this actor is different: no session cookie, no second run to fetch results, a start fee that is not charged when the search returns nothing, and a run that fails loudly when the scrape breaks instead of succeeding with an empty dataset. If you need more than 1,000 profiles from one search, split it by region or headcount and run each URL. Three runs for 2,500 profiles cost $25.90 ($0.90 in start fees plus $25.00 in rows): within a couple of percent of a $0.50-per-search competitor, and more than the cheapest per-row ones. If your only criterion is price at that volume, they win.

Input

Field	Type	Required	Default	What it does
salesNavigatorUrl	string	yes	–	Full Sales Navigator people-search URL containing query=.
maxProfiles	integer	no	100	Stop after this many profiles (1–1,000).
searchName	string	no	run id	Optional label shown in the run summary.

Input example

{
    "salesNavigatorUrl": "https://www.linkedin.com/sales/search/people?query=(filters:List((type:CURRENT_TITLE,values:List((text:Head%20of%20Sales,selectionType:INCLUDED))),(type:REGION,values:List((id:105015875,selectionType:INCLUDED)))))",
    "maxProfiles": 500,
    "searchName": "Heads of Sales - France"
}

What you get: LinkedIn profile and company fields

One dataset row per profile. Fields with no data are null. Example row (illustrative: fictional person and company):

{
    "full_name": "Anna Example",
    "first_name": "Anna",
    "last_name": "Example",
    "linkedin_url": "https://www.linkedin.com/in/anna-example",
    "job_title": "Head of Sales",
    "headline": "Head of Sales at Northwind Logistics | B2B freight",
    "company_name": "Northwind Logistics",
    "company_linkedin_url": "https://www.linkedin.com/company/northwind-logistics",
    "company_industry": "Transportation, Logistics, Supply Chain and Storage",
    "company_location": "Rotterdam, South Holland",
    "company_employee_count": 850,
    "location": "Rotterdam, Netherlands",
    "start_date": "2025-04",
    "tenure_at_position": "1 yr 5 mos",
    "tenure_at_company": "4 yrs 11 mos",
    "summary": "Sales leader with 12 years in B2B logistics ...",
    "spotlight_badges": ["Changed jobs in the last 90 days"],
    "connection_degree": "2nd",
    "open_to_inmail": true,
    "premium_profile": false
}

Group	Fields
Person	full_name, first_name, last_name, linkedin_url, job_title, headline, location, summary
Company	company_name, company_linkedin_url, company_industry, company_location, company_employee_count
Tenure	start_date, tenure_at_position, tenure_at_company
Sales Navigator signals	spotlight_badges, connection_degree, open_to_inmail, premium_profile

Field coverage, measured on a 1,000-profile run: 100% of rows had a vanity /in/ LinkedIn URL, title, company, tenure and industry. 97% had a vanity company URL. summary was present on about 70%; the rest have no About section on their profile.

Download from the Dataset tab as CSV, JSON or Excel, or read it from the API. The run's OUTPUT record in the key-value store holds the summary: job id, status, profiles scraped, total results available in the search, and the daily capacity remaining after your run.

Getting emails

This actor returns LinkedIn identity and firmographic data. It does not return email addresses or phone numbers.

Every row has linkedin_url. Pass it to your email-finding step: an enrichment actor on Apify, a Clay waterfall, or any enrichment API that accepts a LinkedIn profile URL.

Free Apify plan. Runs started from a free Apify plan are limited to 20 profiles (enough to see real output). Any paid Apify plan unlocks up to 1,000 profiles per run. The run log says when the limit was applied.

Limits and daily capacity

• 1,000 profiles per run. LinkedIn itself caps any Sales Navigator search at 2,500 visible results; that is a platform constraint, not a scraper failure. For more, split the search with filters (region, headcount, industry) until each part is under 1,000, and run each URL.
• Daily capacity. The managed account pool has a shared daily ceiling across all users, resetting at 00:00 UTC. The remaining capacity is written to every run's OUTPUT record, so you can check it from the API before you queue a large job. If your run would exceed what is left, maxProfiles is lowered to the remainder, the log says so, and you are charged only for what you receive. If nothing is left, the run fails before any charge. If you need reserved throughput for a recurring job, contact us through leadsfactory.io.
• Minutes, not seconds. See measured delivery time above.
• People searches only. Account (company) search URLs, saved-search links and lead lists are rejected.
• No email addresses, no phone numbers.
• One search URL per run. Run the actor once per search, or call it from the API in a loop.
• Rows are unique within a run (duplicates Sales Navigator returns are removed; a 1,000-profile run delivered 995 unique rows). Runs are independent: the same URL twice returns the same profiles twice, and bills twice. Dedupe on linkedin_url downstream.
• Profiles hidden from search by their owners are not returned. The data is what Sales Navigator shows at run time.

Try it before you trust it

• Smallest real test: $0.55. Run it on a search whose results you already have open, 25 profiles, and compare.
• Support: issues on this actor are answered by the LeadsFactory engineering team on the Issues tab. Include the run ID.
• Maintained: the account pool is the same infrastructure behind the LeadsFactory web app and API. This actor is not a side project.

FAQ

Do I need a LinkedIn or Sales Navigator account? You need Sales Navigator to build the search and copy the URL. You do not connect it, log in through the actor, or share a cookie. The scrape runs on LeadsFactory's accounts.

Is my LinkedIn account at risk? Your account is not used by this actor, so nothing here can get it flagged or restricted.

Are emails or phone numbers included? No. You get LinkedIn profile and company fields plus the profile URL. See Getting emails.

Does it work with account searches, saved lead lists or account lists? Not in this version. This actor takes people-search URLs containing query=. To scrape a lead list, apply the equivalent filters in a normal Sales Navigator people search and copy that URL.

My search has 6,000 results. How do I get them all? Sales Navigator caps any search at 2,500 visible results, and this actor at 1,000 per run. Split the search by region, headcount or industry until each part is under 1,000, then run each URL.

Why did I get fewer profiles than I asked for? One of three reasons, and the log plus the OUTPUT record say which: the search had fewer results; the daily capacity limit cut the run short; or your maximum run cost was reached. In every case you pay the $0.30 start fee plus $0.01 for each profile actually delivered, never for the profiles you did not get; if nothing was delivered, you pay nothing.

Can I run it from code? Yes. Use the Apify API, SDKs or the Apify MCP server as with any actor. For direct access with higher limits, use the LeadsFactory API.

What happens to the search URL I submit? It is used to run your scrape. It is not sold or shared with other users. Results live in your Apify dataset, under your account, with your retention settings.

Where does the data come from, and is it compliant? Rows are read from LinkedIn Sales Navigator search results and profile fields as they appear to a logged-in Sales Navigator user at the time of the run. We return no email addresses, no phone numbers, and no data you could not see yourself with a Sales Navigator seat. You are the data controller for your outreach and are responsible for GDPR and CCPA obligations, including notice and opt-out.

Something failed. Where do I ask? Open an issue on this actor's Issues tab with the run ID. The LeadsFactory team answers there.

About LeadsFactory

LeadsFactory finds the right buyer at every company for outbound teams and agencies. The same infrastructure powers a web app, a REST API and a hosted MCP server, with Clay and CRM integrations.

• Website: leadsfactory.io
• API reference: apiv2.leadsfactory.io/docs