Edges vs iScraper
More than profile reads — a LinkedIn API you can bet a roadmap on.
Who this comparison is for
You're shipping a product feature that depends on LinkedIn data, and "one endpoint for profiles" is not enough. You need the surrounding actions — and a vendor whose security review won't block your enterprise deal.
At a glance
The axes that matter when you’re picking between us.
| Topic | Edges | iScraper |
|---|---|---|
| Action catalog | 70+ documented LinkedIn actions across data, signals, Sales Navigator, and engagement. | LinkedIn profile and company endpoints; confirm current catalog in their docs. |
| Request shape | Consistent REST shape, shared error model, single rate-limit policy across actions. | Per-endpoint conventions; test request shapes and error codes against your stack. |
| Enterprise readiness | SOC2 Type II, DPA, dedicated security page, enterprise tier with SLA and DPO contact. | Review their security posture, certifications, and procurement process directly. |
| Cost modeling | One credit balance across all actions — predictable as your call mix shifts. | Per-endpoint or per-call tiers; re-model cost when your feature set changes. |
| Support tier | Shared Slack for enterprise accounts; documented incident comms. | Email / ticket support; check response SLAs for production-grade plans. |
Pick the right one
Choose Edges when
You need enterprise-grade posture (SOC2 Type II, DPA, EU data handling) and a single action catalog that keeps up as your LinkedIn feature set grows from enrichment into signals, lists, and engagement.
Consider iScraper when
A few iScraper endpoints cover 95% of your needs, you're operating at small volume, and your buyers haven't yet asked for SOC2 or an enterprise agreement.
Migration
Map your current iScraper calls or automations to Edges actions using the Library and the documentation. Ask support for the OpenAPI spec and it drops straight into Postman, Hoppscotch, or any code generator. Share your integration outline and we can suggest parity endpoints and credit estimates.
FAQ
What does Edges cover that iScraper doesn't?
Beyond profile and company enrichment, Edges ships Sales Navigator search, list exports, engagement actions (connections, messages), and the scheduled extracts you use to build timing — all behind the same API key.
How do I estimate monthly cost on Edges?
Use the credit calculator on the pricing page with your expected monthly call mix. Because credits are shared across actions, you don't need to model each endpoint separately.
Is Edges SOC2 compliant?
Yes — SOC2 Type II. Enterprise buyers can request the report, a signed DPA, and EU data-residency details from our security page.
What happens to API behavior when LinkedIn changes?
Edges absorbs upstream changes and communicates material differences via the changelog and status page. You don't own selector maintenance — we do.
Can we migrate gradually from iScraper?
Yes. Most teams cut over one feature at a time, keeping iScraper for legacy calls during a 1–2 sprint dual-run before consolidating.
Does Edges support webhook-based workflows?
Yes — webhooks (callbacks) for async and schedule Action runs. See the callbacks guide on docs.edges.run. You can also poll GET /runs/{run_uid}/outputs.
Build on Edges
Credits-based pricing, SOC 2 Type II, and a growing catalog of LinkedIn actions — see Pricing and Enterprise for scale.
// go deeper
// other comparisons
Edges is not related to LinkedIn and is not an official LinkedIn product.