Depth on LinkedIn vs breadth across inboxes — pick the API that fits your product.
You're building a product where LinkedIn is the main surface — prospecting tools, sales intelligence, recruiting automation — not a CRM that happens to wire up five messaging channels.
| Topic | Edges | Unipile |
|---|---|---|
| Center of gravity | LinkedIn as a first-class platform: data, signals, Sales Nav, engagement. | Unified messaging abstraction across LinkedIn, email, WhatsApp, Messenger, etc. |
| LinkedIn depth | Full Sales Navigator coverage, intent signals, lead lists, profile and company enrichment. | Messaging-side LinkedIn features (DMs, connections); data and SN depth is narrower. |
| API shape | Action-oriented endpoints aligned to discrete LinkedIn jobs. | Resource model centered on accounts, threads, and messages across channels. |
| Ideal buyer | Prospecting tools, sales intelligence, recruiting platforms, LinkedIn-heavy AI agents. | Omnichannel CRMs, shared inboxes, multi-channel AI copilots. |
| Single-channel ROI | High: every feature compounds on LinkedIn capabilities. | Lower if LinkedIn is 100% of your use case — you pay for breadth you don't use. |
LinkedIn is your primary surface. You need depth across enrichment, Sales Navigator, intent signals, and engagement — not just "a LinkedIn connector" alongside Gmail and WhatsApp.
You're building a multi-channel inbox (CRM, ATS, omnichannel outreach, AI agent) where LinkedIn is one of several messaging integrations and you need a shared thread/account abstraction.
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.