LinkedIn Sales Navigator API: What Exists and What Does Not

• There is no public LinkedIn Sales Navigator API for search or export. Official access means CRM sync on the Advanced Plus plan, and the SNAP partner program is closed to new applications.
• Teams get data out through the seat they already pay for: per-credit export tools, automation platforms, or an outreach platform that imports a search URL directly.
• A single search view is capped at roughly 2,500 results, and operators keep account-level extraction near 2,500 profiles a day per connected seat.
• Pricing checked on 8 August 2026: Sales Navigator Core is $119.99 per month, Evaboot starts at $9, PhantomBuster at $69.

Sales Navigator holds the best B2B search filters on the internet, and no public door to get anything out programmatically. If you came here looking for a LinkedIn Sales Navigator API to run searches or export lead lists, the direct answer is that LinkedIn does not sell one, at any price, to anyone outside a small circle of CRM partners.

That gap between the best data and the closed door explains this entire category. This guide covers what officially exists, what every export route really costs as of this week, the one API call that turns a Sales Navigator search into a campaign audience, and the limits that decide whether your seat survives.

Is there an official Sales Navigator API?

Only for one narrow job: keeping Sales Navigator and a CRM in sync. Everything else you might want an API for, searching, exporting lists, pulling profile data, has no official endpoint. And the historical route into that ecosystem, the Sales Navigator Application Platform (SNAP), is not accepting new applications, in LinkedIn's own words on the partner page.

What the official surface actually covers

Here is the complete official map. It is short on purpose: these are integration programs for software vendors, not developer products you can sign up for.

You will find guides claiming you can apply for Sales Navigator API access through LinkedIn's developer portal with a use-case justification. For search and export, that path leads nowhere: the developer portal products cover sign-in, sharing, ads and partner programs, none of which touch search results. Some of those guides even show code calling endpoints that do not exist.

What CRM Sync actually covers

Since CRM Sync is the closest thing to an official integration, it is worth being precise about what it does, and who gets it. It links a seat on the Advanced Plus plan, and only that plan, to Salesforce, Microsoft Dynamics, HubSpot or Oracle Sales: leads and accounts stay matched between the two systems, activity like InMails and messages can be written back to the CRM record, and reps see CRM context inside the seat. What it never does is answer a search query programmatically or hand you a list. It moves records you already have; it does not create new ones from search results. If your goal is net-new pipeline out of saved searches, CRM Sync is not the tool, and nothing official is.

What does Sales Navigator itself cost?

Every export route below starts with a paid seat, so the seat price is part of the real cost of any pipeline. These are the figures on LinkedIn's compare-plans page, which LinkedIn labels as estimates that can exclude tax and change without notice.

Note the pattern: the only plan that touches anything API-like is the custom-priced one, synced to a CRM you already run. There is no tier, including Advanced Plus, that unlocks programmatic search.

Two billing details change the math. Annual billing saves about 25 percent on Core but only about 6 percent on Advanced, by LinkedIn's own labels, so the discount argument weakens as you move up. And both self-serve plans offer a free trial if the member is not on a paid LinkedIn subscription and has not used a trial in the past year, which is the cheap way to validate a targeting thesis before wiring any tooling to the seat.

The seat also changes what you can do compared to a free or Premium account: the commercial-use search limit disappears, which matters precisely because every export route below leans on heavy search. One thing it does not buy is elastic InMail: credits are fixed per plan and cannot be topped up on this subscription, a constraint to keep in mind if your outreach model depends on messaging beyond your network.

How do teams actually export Sales Navigator results?

Through the seat itself. Every working route operates the member's own Sales Navigator session and walks search results the way the member would, then turns them into rows or campaign contacts. The differences are in packaging, pricing and how much of the downstream work each tool takes on.

Per-credit export tools

Tools like Evaboot attach to your seat and export search results to CSV, priced per credit: one exported lead costs one credit, one found and verified email costs another, and a lead with a verified email costs two. Plans start at $9 per month for 100 credits and scale to $1,699 for 200,000, with unused credits rolling over while you stay subscribed. Two fine-print points worth knowing before you commit: the tool requires an actual Sales Navigator subscription (it does not work on a free LinkedIn or Recruiter seat), and the credit meter means your real cost tracks list size plus email coverage, not a flat fee. You get clean rows fast; everything after the spreadsheet, enrichment, sequencing, sending, stays your problem.

Automation platforms

PhantomBuster runs cloud automations against your session, Sales Navigator export included, from $69 per month on the Start plan (5 automation slots, 20 hours of execution time) through $159 on Grow to $439 on Scale, with about 20 percent off on annual billing. Each plan bundles email-finder credits on top, from 500 a month on Start. It is flexible and covers many networks, but you assemble the pipeline yourself, chain the automations, watch the pacing, and the execution-time model means big exports consume your monthly quota quickly. It is a power tool for a growth engineer, not a turnkey pipeline.

Direct import into an outreach platform

The third route skips the spreadsheet: paste the Sales Navigator search URL into an outreach platform and the results land as a campaign audience, deduplicated and ready to sequence. Swarmhit works this way, with extraction capped at 2,500 profiles a day per connected seat. If you are comparing this category more broadly, our prospecting tools guide covers it.

Side by side, with pricing read from each vendor's own page this week:

The Unipile row deserves one clarification: a raw account API gives you endpoints against the connected seat, not a Sales Navigator search API, and you build and host the extraction logic yourself. We compare that trade-off in depth in our Unipile comparison.

Which route should you pick?

Start from the destination, not the tool. If the rows are headed for a warehouse, a data team, or an enrichment waterfall you already run, a per-credit exporter is the honest fit: you pay for exactly the records you take and nothing pretends to do the outreach for you. If the destination is a campaign, count the steps between the search and the first message sent; every extra hop is a place where lists go stale and ownership gets fuzzy.

Then run the cost math on your real volume. A thousand exported leads costs about $49 a month on Evaboot's 1,500-credit tier before you have sent anything, plus whatever your sequencer and sending infrastructure cost. On the import route, one $39 seat covers the same thousand leads and the campaign that works them, because the extraction and the outreach are the same product. PhantomBuster sits in between: the subscription is fixed, but execution hours are the real currency and heavy exports spend them fast.

Finally, be honest about who operates it. Credit exporters need a data-literate owner, automation platforms need someone who enjoys plumbing, and raw account APIs need engineers on the payroll. The import route needs a rep who can paste a URL. Match the route to the team you have, not the team you plan to hire.

How do you import a Sales Navigator search through an API?

If your product or workflow needs this programmatically, here is what the working version looks like on the Swarmhit API. One call creates an import job from a search URL against a connected sender account:

curl -X POST https://app.swarmhit.com/api/v1/lead-imports \
  -H "Authorization: Bearer swh_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "accountId": "ACCOUNT_ID",
    "url": "https://www.linkedin.com/sales/search/people?...",
    "listName": "Fintech CTOs",
    "maxLeads": 500,
    "tags": ["fintech"]
  }'

A few details in that call carry the whole workflow. The accountId is the connected seat that will do the walking, so the import inherits that seat's caps and pacing instead of hammering the search. The url is the search you built in the interface, filters included, which means targeting stays where it belongs, in Sales Navigator's filter UI, and code only handles the handoff. And maxLeads bounds the job explicitly rather than trusting a tool to stop. The import runs as a job you can poll:

curl https://app.swarmhit.com/api/v1/lead-imports/IMPORT_ID \
  -H "Authorization: Bearer swh_live_..."

When the job completes, the leads sit in a list, deduplicated against your workspace, ready to attach to a campaign or enrich. Leads are upserts in this model, so re-importing an overlapping search refreshes existing records instead of duplicating them, which makes weekly re-runs of a saved search safe. From there the same API drives the outreach itself: sequences, InMails, inbox and webhooks, which we cover in our guide to the LinkedIn messaging API. That is the practical difference between an export pipeline and an outreach pipeline: the second one ends in conversations, not rows.

What are the real limits on Sales Navigator extraction?

Two layers, and they are different in kind. The first is what the interface shows you: a single search view is capped at roughly 2,500 results (100 pages of 25), so no tool, whatever it claims, exports more than that from one query. Teams work around it by segmenting searches with filters, by geography, headcount, or seniority, until each slice fits under the cap. The segmentation is not wasted work: slices that fit the cap are usually also the slices that deserve different messaging.

The shape of the extraction matters as much as the total. A seat that pulls its daily volume in one burst at 3 a.m. looks nothing like a person; the same volume spread across business hours does. Fresh seats deserve extra caution: an account that joined the tool on Monday and extracts at full ceiling on Tuesday is the pattern detection systems exist for, which is why warm-up ramps exist. None of this is paranoia, it is the operating discipline that separates seats that run for years from seats that die in a month.

The second layer is behavioral, and LinkedIn publishes no numbers for it. What it watches is how a seat behaves: volume, pace, regularity. The operating figures are operator-reported, and the ceiling Swarmhit enforces per connected seat is 2,500 profiles a day from Sales Navigator search and 1,000 a day from standard search, paced like a person rather than pulled in one burst. Extraction sits outside LinkedIn's terms, like all member-account automation, and the seat doing the work carries the risk. That is the reason caps and behavioral safeguards matter more than raw speed, a trade-off we cover in is LinkedIn automation safe and in our review of LinkedIn scraper APIs. One more boundary worth stating plainly: none of this covers cookie-less scraping of profiles at scale, which we consider illegal and do not do.

Do you need the export at all?

Sometimes the spreadsheet is the detour. If the destination is a data warehouse, an export tool is the right shape. But if the destination is a campaign, exporting to CSV only to re-import into an outreach tool adds a step, loses the live link to the source search, and parks personal data in a file nobody will delete. B2B data also ages badly: titles change, people move, companies reorganize, and a static export starts decaying the day it lands, while a re-runnable import stays anchored to a search that always reflects the present. Importing directly into the platform that will run the outreach removes the middle entirely, and leaves fewer copies of personal data sitting around, which your next compliance review will thank you for.

It also keeps you honest on scope: a campaign audience of 500 well-filtered prospects beats a 25,000-row export that will never be worked. The teams that get the most out of Sales Navigator treat it as a targeting engine feeding a sequencer, not as a database to be drained. For the wider picture of what LinkedIn does and does not let you do programmatically, our LinkedIn API guide maps the whole landscape.

FAQ

Is there a free Sales Navigator API?

No. There is no public Sales Navigator API at any price, free or paid. The official programs are CRM sync for Advanced Plus subscribers and partner integrations, and the SNAP partner program is closed to new applications.

Can I apply for access through the LinkedIn developer portal?

Not for search or export. The developer portal covers sign-in, content sharing, ads and partner products. Guides describing an application path to Sales Navigator search data describe something LinkedIn does not offer.

How many results can I export from one search?

About 2,500, because a Sales Navigator search view stops at roughly 100 pages of 25 results. To cover a bigger universe, split the search into narrower filter slices and run them separately.

How many profiles a day can I extract safely?

LinkedIn publishes no threshold, so treat every number as operator practice, not policy. Swarmhit caps each connected seat at 2,500 profiles a day from Sales Navigator search and 1,000 from standard search, spread across the day with human-like pacing.

Is exporting Sales Navigator data against LinkedIn's terms?

Yes, member-account automation and extraction sit outside the user agreement, and the connected seat carries the risk. That risk is managed with caps, pacing and behavioral safeguards, which is exactly the layer to evaluate when you pick a tool.