Sales Navigator, as an API.

Yes. Edges exposes saved people and account searches as first-class actions — point the request at the saved search URL and paginate through results as structured JSON. You do not rebuild filters, parse HTML, or script a browser; you call an endpoint and consume the rows. Search metrics (total results, page-level counts) are also available for teams that track list sizes over time.

Yes. Lead lists and account lists are exposed as dedicated actions that return a normalized row shape — profile or company fields, list membership, and the identifiers you need to rejoin to your CRM. You can run exports on a schedule, diff them against your warehouse, and keep lists in sync without a human touching the Sales Navigator UI.

You'll need at least one Sales Navigator seat per identity making SN-specific calls — yours or one Edges manages for you. Edges runs the session for that seat; your application never needs the SN UI. Managed seats are available when you don't want to hold a licence yourself.

Lobstr and Evaboot are operator-facing tools — someone clicks through a UI or an extension to export a list. Edges is a developer API: one REST endpoint, versioned payloads, webhooks for long jobs, and the same authentication you use for the rest of Edges' 70+ LinkedIn actions. If a human is the bottleneck, their tools are fine. If a backend is the consumer, you want an API.

Yes — that is the consolidation pattern most teams land on. Run a Sales Navigator search, take the returned profile IDs, and feed them into linkedin-extract-people or linkedin-extract-company for deeper fields. Everything charges against one credit balance, so you do not have to budget SN and enrichment as separate vendor lines.

Smart links and account-level signals (employee distribution, headcount metrics, company search filters) are available as dedicated actions in the library. The typical pattern is: resolve an account, pull its employees and distribution, and keep that snapshot in your warehouse for account planning or ABM scoring.

Yes. Sales Navigator surfaces have their own upstream friction, and Edges applies sensible defaults so you do not burn through a seat on a cold start. Enterprise plans negotiate higher concurrency and dedicated capacity. We recommend async runs and webhooks for large exports rather than hammering the live endpoint.

One credit balance across every action Edges ships — Sales Navigator searches, enrichment, messaging, and the extracts you schedule for timing. Credit costs per action are documented in the library; teams with a mixed SN + enrichment workload usually see lower fully-loaded cost than splitting spend across a Lobstr-style tool and a separate enrichment vendor. See the pricing page for current plans or talk to sales for enterprise volume.

No. LinkedIn does not offer a public API for Sales Navigator saved searches, lead lists, account lists, or smart links. Edges is a third-party Actions API for that surface — connect a seat (yours or one we manage) and call those jobs as JSON. Edges is not related to LinkedIn and is not an official LinkedIn product. You own how you use it.

No. Authentication to Edges is an API key. The Sales Navigator seat is connected as an identity (cookie or email + password, or a seat Edges manages). Your application never holds the SN session.

Live Sales Navigator searches return in p50 1.2s · p99 2.4s. Rate posture is per connected identity, not per API key: automatic ramp-up, daily budgets, 429 with Retry-After and X-RateLimit-* headers. Large list exports should run async with a webhook rather than a tight live loop. Enterprise plans negotiate higher concurrency.

Proxycurl was a profile and company enrichment API. It did not expose Sales Navigator saved searches, lead lists, or smart links. If you are replacing those enrichment pulls, see the Proxycurl comparison. This page is the SN surface: searches, lists, and account maps as actions.