Sales Navigator API in 2026: SNAP Is Closed to New Partners
Sales tooling eventually reaches for the Sales Navigator API, and the form it points you at no longer leads anywhere.
LinkedIn has an official Sales Navigator API, and it is not accepting new partners. Its overview page states so directly. Even for approved partners it has no open people-search or lead-list endpoint: it embeds Sales Navigator’s own interface in your product, exports your customer’s sales-team activity, and validates CRM records against LinkedIn.
Search and lead lists were outside the platform before the door closed, so the closure changes less for a sales tool than it first looks. Teams that need them work through a LinkedIn account that holds a Sales Navigator seat instead.
On this page
What SNAP actually is
The Sales Navigator Application Platform, SNAP, is three separate service families with four OAuth scopes between them. Each one solves a narrow integration problem for a CRM or sales-tooling vendor, and none of them is a data feed.
| Family | What it does | Scope |
|---|---|---|
| Display Services | Embeds a Sales Navigator iframe inside your app showing basic profile info, related leads and recent activity. A Sales Access Tokens API covers native apps | r_sales_nav_display |
| Analytics Services | Bulk export of your own customer’s sales team activity, plus Social Selling Index scores | r_sales_nav_analytics |
| Sync Services | CRM Data Validation, flagging stale CRM records against LinkedIn, and Profile Associations, which return profile data matched to records the partner already holds | r_sales_nav_validation, r_sales_nav_profiles |
| People or account search | Running a Sales Navigator search and returning the results | Not offered |
| Lead lists and saved searches | Reading or writing a seat holder’s saved lists | Not offered |
Display Services is the family a sales tool gets pointed at first, and it renders LinkedIn’s own interface while the data behind it stays on LinkedIn’s side. Analytics Services reports on your customer’s sellers, so it answers questions about activity and not about prospects.
Closed to new partners, and the docs disagree
LinkedIn stopped accepting new SNAP partners, and its overview page, last updated on 28 May 2025, says so in a banner:
“We are not currently accepting new partners for access to the LinkedIn Sales Navigator API. We periodically review our onboarding capacity and will update this page if availability changes.”
The complication is that SNAP’s own sub-pages have not been touched since May 2023 and still tell prospective partners to apply to the program, and “Sales Display” is still listed in LinkedIn’s public product catalogue. A developer who lands on a sub-page from search sees an open door that the parent page has already shut. Check the overview page before you plan around an application.
What the SNAP partner terms require
For partners already inside, the SNAP Terms of Use set the shape of what can be built. The published terms, last updated in February 2022, include several clauses that rule out common product ideas.
- You cannot charge for the integration. “You shall not charge Integration Customers, directly or indirectly, for access and/or usage of data obtained via the integration.”
- You cannot build profiles from it. Content “shall not be used for purposes of creating or populating a profile on a third-party service”.
- You cannot enrich beyond the seat. Partners may not “supplement the data that the Licensed Seat Holder has or can view”.
- The data stays with that customer. It may not be used “for sales efforts or management of customer relationships by other customers and partners”.
- Both licences are required. Access is limited to people holding a partner licence and a Sales Navigator seat, and a beta is capped at 25 users per integration customer.
- There is a build clock. Partners have 12 months to ship, after which LinkedIn may terminate on 30 days’ notice.
One caution on how this gets described elsewhere. The SNAP terms do not contain an explicit clause about bulk export, scraping or automated outreach, so claims that SNAP “bans automation” are being read into the document rather than out of it. SNAP also sits on top of LinkedIn’s API Terms of Use and its User Agreement, which do address automated access, so silence in the partner terms is not permission. The clauses above are enough on their own to rule out an enrichment product.
Getting Sales Navigator data programmatically now
An account-based API reaches Sales Navigator the way a seller does, through a logged-in account that holds the seat. That places the capability behind the account, which is also what puts a ceiling on volume. GTM API reports 20,000+ connected accounts at under a 1% monthly ban rate on the stack that holds them there, and its Sales Navigator surface covers search, messaging and capability detection.
- People search, by URL or by parameters. Paste a Sales Navigator search URL, or build the query from the facet vocabulary directly: current and past titles, locations, company headquarters, industries, current and past companies, groups, schools, seniority, function, years in role, years at company, years of experience, headcount, company type, profile language, network degree and connections-of.
- Account search with the firmographic facets. Annual revenue, headcount growth, department headcount and its growth, Fortune ranking, follower count, and the activity filters, plus toggles for hiring on LinkedIn, first-degree connections and saved accounts.
- Decision makers for a company, resolved through the Sales Navigator surface, so seniority comes from LinkedIn’s own classification.
- Facet typeahead. Resolving a company, school, group or list name into the identifier a search filter needs, across 19 facet kinds.
- Sales Navigator messaging and InMail, with conversation and message sync on the Sales Navigator inbox specifically.
- Seat detection. A check call sets the account’s Sales Navigator flag, and searches route only to accounts that carry it. An account without a seat gets an explicit refusal, and the call is never re-routed to one that has it.
A Sales Navigator search can also be saved as a recurring job, so a territory definition re-runs on a schedule and yields new matches without anyone opening the interface.
What this route does not do either
An account-based route to Sales Navigator has five gaps, and the first two come up in every evaluation we see.
- No lead-list or account-list management. Lists appear as filter values in search, and there is no endpoint to create, read or modify a seat holder’s saved lists.
- No saved-search or alert objects. Recurrence is handled by scheduling a search on our side, and Sales Navigator’s own saved searches and alerts stay in the interface.
- No bulk export endpoint. Results come back through the search calls page by page.
- No SNAP integration. This is a separate route to the same screens, and nothing here runs through LinkedIn’s partner platform.
- Recruiter is detection only. An account’s Recruiter access is reported, and there are no Recruiter data or action endpoints behind it.
Peer account-based providers cover overlapping ground, and each is bounded by the same thing: one seat, one account, a real ceiling on how much it can do in a day. Where the ceiling sits and how it moves is on the LinkedIn limits page.
Which Sales Navigator route fits which build
Four situations cover almost every team that asks about this API, and only one of them has an official answer left. The split is between wanting LinkedIn context inside your own product, which SNAP was built for, and wanting to find and contact people, which it never did.
- A CRM showing LinkedIn context in-app. SNAP Display Services is the sanctioned answer, if you were already a partner.
- Reporting on your customers’ sellers. Analytics Services, same caveat.
- Finding people and companies, then contacting them. A seat plus an account-based API. Nothing official covers this.
- Static firmographic data at volume. A dataset provider, a third category that neither route on this page covers and one the profile data API page compares.
# full reference: docs.gtm-api.com curl -X POST https://app.gtm-api.com/linkedin/v4/api/linkedin-scraping/search-sales-nav-people-by-params \ -H "Authorization: Bearer $GTM_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "linkedin_account_sid": "ln_ac_...", "current_titles": ["Head of Growth"], "company_headcounts": ["51-200"] }'
Frequently Asked Questions
What is SNAP, the Sales Navigator API?
The Sales Navigator Application Platform, LinkedIn’s official partner program for Sales Navigator integrations. It has three families: Display Services, which embeds Sales Navigator’s interface in your product, Analytics Services, which exports your customer’s own sales team activity and Social Selling Index, and Sync Services, which validates CRM records and associates profiles. It does not run searches or return lead lists.
Can I still become a SNAP partner?
Not as of August 2026. The SNAP overview page, last updated on 28 May 2025, states that LinkedIn is not currently accepting new partners, that it periodically reviews its onboarding capacity, and that it will update the page if availability changes. Several SNAP sub-pages have not been revised since 2023 and still describe an application process, so a developer arriving from a search result can easily read the outdated version.
Does the Sales Navigator API return search results?
No. Search is not part of any SNAP family. Display Services renders LinkedIn’s own interface inside your app, Analytics Services reports on seller activity, and Sync Services works on CRM records you already hold. Running a Sales Navigator search programmatically means going through an account that holds a seat.
Do I need a Sales Navigator seat to use a Sales Navigator API?
Yes, on both routes. SNAP requires the end user to hold both a partner licence and a Sales Navigator seat. An account-based API reads Sales Navigator as the connected account, so that account needs its own seat, and a call routed to an account without one is refused with an explicit error.
Is there an unofficial Sales Navigator API?
Several providers work this way, gtm-api.com among them, by acting on a connected account that holds a seat. Coverage varies, so check each vendor’s own documentation for what it exposes. That is a different arrangement from a partner integration: the capability comes from the account, so it is bounded by what one account can safely do in a day, and account safety is what you end up evaluating.
Sources & Further Reading
- LinkedIn / Microsoft Learn, Sales Navigator API overview (the notice that new partners are not being accepted), last updated 28 May 2025
- LinkedIn / Microsoft Learn, Display Services and Analytics Services and Sync Services, all last updated 2023 and describing an application route the overview page has since closed
- LinkedIn, Sales Navigator Application Platform Terms of Use, last updated 18 February 2022 (the charging, profile-population, supplementation and seat clauses quoted above)
- LinkedIn / Microsoft Learn, Getting access to LinkedIn APIs (the four SNAP scopes and their partner-approval requirement), last updated 26 June 2025
- LinkedIn, developer product catalogue (Sales Display still listed)
- GTM API, developer documentation
- Related: LinkedIn API: the developer guide · LinkedIn limits · Best LinkedIn API · LinkedIn API access · LinkedIn profile data API
Run Sales Navigator searches from an API today.
A seat you already pay for, driven from an API: the full facet vocabulary for search, and messaging on the same contract. GTM API reports 20,000+ accounts at under a 1% monthly ban rate. Free plan, then from $10 per account at volume.
Last updated: August 2026 · SNAP status, families and partner terms verified against LinkedIn’s own documentation on 14 August 2026