What teams build on the LinkedIn API.
Every play below is built on two entities — People and Companies — read at request time, with the fields cached datasets leave null. One REST surface, one credit pool, every common LinkedIn workflow as a documented action.
Edges is not related to LinkedIn and is not an official LinkedIn product.
// Where to start
Pick where you'll start. Compose the rest later.
Most teams start with one pillar, then expand. Because every action shares the same auth, errors, and credit pool, the second pillar takes a sprint — not a re-platform.
Profile & company data
Turn LinkedIn URLs, Sales Navigator IDs, or thin CRM rows into structured people and company JSON — CRM-, warehouse-, and agent-ready in one call.
Search & lists
Discover people, companies, jobs, saved searches, and lists with full-API filters and stable cursor pagination — ICP-tight, agent-friendly, no UI scraping.
Signals & timing
Job changes, hiring moves, funding fields, viewers, reactions — timing you detect by scheduling LinkedIn Actions on your watchlist and diffing live reads in your stack.
Messaging & outreach
Connection requests, messages, InMails, replies, reactions — every LinkedIn action a salesperson takes, behind one identity-aware API with rate ramping built in.
LinkedIn scraper
The alternative to running your own scraper — no proxies, no cookies, no maintenance.
// By product
What you ship determines the calls you make.
Six common shapes. Each is one or two pillars composed — and almost always builds on the next one within six months.
// Sales intelligence
CRM enrichment on lead create
Resolve thin CRM rows into full profiles + company firmographics the instant a SDR adds a contact — no batch nightly jobs.
- resolve url
- linkedin-extract-people
- company
- linkedin-extract-company
// Prospecting tools
ICP search + bulk export
Run Sales Navigator-aligned searches, page through results with stable cursors, enrich each row in the same credit pool.
- paginate
- cursor + ndjson
- enrich
- linkedin-extract-people
// Intent + GTM
Job-change & funding alerts
Schedule extracts on people and companies you care about. Diff in your worker, enrich, then notify your AE in Slack — all on the Actions API.
- diff
- your snapshot store
- fanout
- callback · enrich
// Outbound automation
Multi-step LinkedIn sequences
Invite → wait → message → InMail fallback, across an identity pool. Per-seat rate limits enforced for you; ramping built in.
- invite
- linkedin-connect-profile
- follow up
- linkedin-message-profile
- fallback
- linkedin-inmail-profile
// AI agents
LinkedIn-native research agent
One API key, typed responses, predictable credits. Drop into your tool-use loop and let the agent enrich + search + reach out.
- tools
- plain http
- research
- linkedin-extract-people
// Recruiting
Candidate sourcing & outreach
Sales Nav recruiter-style search + parallel enrichment, then InMail from a connected identity in direct mode, with reply tracking.
- enrich
- linkedin-extract-people
// Composed flow
A pillar is rarely shipped alone.
Most production workflows touch two pillars in a single request graph. Here's a typical outbound flow — trigger, enrich, filter, engage — all on one API key.
Pick one pillar. Ship in a sprint.
Every action behind one API key. Start with 100 free credits and one free identity — no card required.