Sales Navigator scraper: export a search to CSV or JSON

Each page of the search is one API call, and each call is also a typed MCP tool, so an AI agent can run the export. Send the search link as url and the page you want:

curl -X POST "https://app.gtm-api.com/linkedin/v4/api/linkedin-scraping/search-sales-nav-people" \
  -H "Authorization: Bearer gtm_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://www.linkedin.com/sales/search/people?query=...",
       "page": 1, "linkedin_account_sid": "ln_ac_YOUR_ACCOUNT"}'

• Paging. Rows sit at result.rows, 25 a page. Call again with the next page while result.paging.has_more is true; it turns false on the last page, and page 100 is the ceiling. result.paging.total is LinkedIn's own count of the search: exact on a small search, an estimate on a large one.
• The row. The lead fields of the export above, plus pending_invitation (the account that ran the search has an invitation out to the lead).
• MCP. The tool is scrape_linkedin_search_sales_nav_people on https://mcp.gtm-api.com/mcp. For a collector that pages to the end on its own and waits out the budget, an agent calls create_linkedin_auto_scrape with the link and reads the leads back with search_linkedin_auto_scrape_results.
• Budget. A call over the account's daily budget answers 429 with retry_after, the moment it can run again. An account without a seat answers 422 sales_nav_required before anything runs.

The docs: People and company search, Collect leads with an auto-scrape, and the reference for the search call, creating an auto-scrape and reading its results. Connecting a client is on the MCP config generator.

• It does not find email addresses. A Sales Navigator row has none, and gtm-api.com does not look one up or guess one. A full profile read returns contact details only where LinkedIn shows them to your account, which means your first-degree connections.
• It does not run without a seat. Sales Navigator results exist only for a signed-in seat, so the export needs a connected account that holds one, and the call is refused before anything runs on an account that does not.
• It does not pass 2,500 leads per search. Sales Navigator stops at page 100. A bigger segment is several narrower searches, by region, headcount or seniority, each exported on its own, with sn_id as the key to drop the leads two searches share.
• This page fetches nothing. It reads the link you paste and does the arithmetic in your browser. Leads come only from a connected account.

Every route to LinkedIn data, ours and everyone else's, is compared on LinkedIn scraping in 2026, and what LinkedIn's own Sales Navigator API offers is on Sales Navigator API. More checks that need no account are on Free tools.

Disclosure first: gtm-api.com publishes this page and sells the first row, so it comes first. The others are as each vendor publishes its prices, read on 16 October 2026. They charge for different units, so compare the unit before the number.

Sources, read 16 October 2026: Evaboot pricing (the credit, and the Sales Navigator account it needs), Vayne pricing, PhantomBuster pricing. Evaboot and gtm-api.com both read through a Sales Navigator seat of your own, which LinkedIn bills separately.