One API for everything LinkedIn — not just enrichment pulls.
You run LinkedIn enrichment in production and your backlog now includes signals, Sales Navigator flows, or outbound actions. You don't want to onboard a second vendor to get there.
| Topic | Edges | Proxycurl |
|---|---|---|
| Scope | 60+ LinkedIn actions: profiles, companies, signals, Sales Navigator, engagement. | Profile and company enrichment endpoints; narrower surface area. |
| Pricing model | Usage-based credits. Mixed action costs tracked in one balance. | Per-credit with separate caps per endpoint family — review current plans. |
| Roadmap overlap | Built for teams whose next feature is "add Sales Nav" or "add intent signals". | Focused on enrichment; adjacent workflows require other tools. |
| Integration | One API key, consistent request shapes, shared rate policy across all actions. | One API key, endpoint-specific conventions; rate policy varies by product. |
| Compliance posture | SOC2 Type II, dedicated security page, enterprise tier for regulated buyers. | Consult their security documentation for current certifications. |
You want a single REST API that covers today's Proxycurl calls and the next twelve months of LinkedIn features your product team will ask for — signals, engagement, Sales Navigator workflows — without stitching vendors.
Your use case is strictly point profile or company enrichment, Proxycurl's published pricing fits, and you have no plans to add signal, engagement, or Sales Navigator flows.
Map your current HTTP calls or automations to Edges actions using the Library and documentation. If you share your integration outline with support, we can suggest parity endpoints and credit estimates.
Credits-based pricing, SOC2, and a growing catalog of LinkedIn actions—see Pricing and Enterprise for scale.