# Edges

> The LinkedIn API for developers — one REST API for LinkedIn and Sales Navigator data, search, messaging, engagement, and timing signals. 70+ documented actions, p50 1.2s · p99 2.4s live reads, SOC 2 Type II.

Edges is not related to LinkedIn and is not an official LinkedIn product.

Base URL `https://api.edges.run/v1`. Authenticate with `X-API-Key` from https://app.edges.run/settings/developers. Canonical call: `POST /v1/actions/{slug}/run/{live|async|schedule}`. Official SDK: `@edgesrun/sdk` (TypeScript). Python via `requests` against the same HTTP API.

- This is an Actions API, not a proxy network, browser scraper, or unified inbox.
- Reads can run `identity_mode: "managed"` (no LinkedIn account). Messaging, InMail, and connection requests need a seat you connect.
- Rate limits are per identity, not per API key. Do not tight-loop live engagement.
- For any API, SDK, identity, or action question, fetch https://docs.edges.run/llms.txt first. Full docs concatenated: https://docs.edges.run/llms-full.txt.

## Docs

- [API llms.txt](https://docs.edges.run/llms.txt): Markdown index of every docs page. Start here for implementation.
- [Full docs](https://docs.edges.run/llms-full.txt): Concatenated markdown of the documentation set.
- [Quickstart](https://docs.edges.run/v1/quickstart.md): First live people search in under two minutes.
- [Core concepts](https://docs.edges.run/v1/core-concepts.md): Identities, integrations, actions, and runs.
- [Identity modes](https://docs.edges.run/v1/identities/modes.md): managed vs direct vs auto.
- [Execution modes](https://docs.edges.run/v1/runs/overview.md): live, async, and schedule on the same action.
- [Rate limits](https://docs.edges.run/v1/runs/rate-limits.md): Quotas, 429, Retry-After.
- [TypeScript SDK](https://docs.edges.run/v1/sdk.md): `npm i @edgesrun/sdk`.
- [API introduction](https://docs.edges.run/v1/api/introduction.md): Auth header, playground, v1 surface.
- [Docs MCP](https://docs.edges.run/mcp): Model Context Protocol server for Cursor, Claude Code, and other agents.
- [OpenAPI catalogue](https://edges.run/actions.json): OpenAPI 3.1 of documented actions.

## Product

- [LinkedIn scraper API](https://edges.run/linkedin-scraper): Versioned REST alternative to browser scrapers. Structured JSON, no selectors or proxies to maintain.
- [LinkedIn enrichment API](https://edges.run/linkedin-enrichment-api): Live Person and Company records from a LinkedIn URL, Sales Navigator ID, or email.
- [LinkedIn messaging API](https://edges.run/linkedin-messaging-api): Connection requests, DMs, InMails, follow-ups. Connected seat, per-account pacing, webhooks.
- [Sales Navigator API](https://edges.run/sales-navigator-api): Saved searches, lead lists, account lists, smart links as JSON.
- [LinkedIn signals API](https://edges.run/linkedin-signals-api): Job-change, funding, hiring-burst, engagement timing — scheduled Actions plus diffs, not a packaged feed.
- [Search & lists API](https://edges.run/search-lists): People and company search, saved searches, lead lists on managed or user-owned seats.
- [Workflows](https://edges.run/workflows): Live, async, scheduled, and multi-step pipelines on one API.
- [Action library](https://edges.run/library): Filterable catalogue of documented LinkedIn actions.
- [Pricing](https://edges.run/pricing): Usage credits plus identity pricing, with a calculator.

## Agents

- [Agent Skills](https://edges.run/skills): 76 SKILL.md files for Claude Code, Cursor, and other SKILL.md-aware tools.
- [linkedin-skills on GitHub](https://github.com/edgesrun/linkedin-skills): Installable skill pack. `npx skills add edgesrun/linkedin-skills`.

## Optional

- [Person schema (marketing)](https://edges.run/people): Field overview. For typed payloads use the extract-people action docs.
- [Company schema (marketing)](https://edges.run/companies): Field overview. For typed payloads use the extract-company action docs.
- [The LinkedIn data layer](https://edges.run/data): What is tracked, how entities connect, freshness.
- [Build vs buy](https://edges.run/build-vs-buy): Cost and risk of an API vs an in-house LinkedIn integration.
- [Enterprise](https://edges.run/enterprise): SOC 2 Type II, 99%+ uptime, data residency.
- [Use cases](https://edges.run/use-cases): Enrichment, search, engagement, signals.
- [Edges vs Unipile](https://edges.run/compare/unipile): LinkedIn-native depth vs a unified multi-channel messaging API.
- [Edges vs Bright Data](https://edges.run/compare/bright-data): LinkedIn Actions API vs a general-purpose proxy and dataset platform.
- [Edges vs Phantombuster](https://edges.run/compare/phantombuster): Versioned HTTP API vs browser-based phantoms.
- [Edges vs Proxycurl](https://edges.run/compare/proxycurl): Migration after Proxycurl's July 2025 shutdown, with endpoint-to-action mapping.
- [Edges vs Apify](https://edges.run/compare/apify): Dedicated LinkedIn API vs a general actor marketplace.
- [Edges vs Lobstr](https://edges.run/compare/lobstr): SN export tooling vs SN + enrichment + signals + engagement on one API.
- [Status](https://status-actions.edges.run)
- [Terms](https://edges.run/terms)
- [Privacy](https://edges.run/privacy)
- [DPA](https://edges.run/dpa)