The LinkedIn API Landscape (2026): What the Official API Does & Doesn't Allow

LinkedIn's official API is built for managing your own presence — signing members in, publishing posts, running ads, and managing your Company Page. It is not built for reading other members' profiles, searching people or companies, enriching a CRM, or sending messages at scale — LinkedIn explicitly restricts those uses. This guide maps what the official API allows, what it forbids (in LinkedIn's own words), and where a third-party LinkedIn API like Edges fits.

The official LinkedIn API, product by product

Access is granted per "product" in the LinkedIn Developer Platform, and most require review or partner approval. The main ones:

• Sign In with LinkedIn (OpenID Connect) — authenticate a member and read their own basic profile (name, photo, email). Not other members.
• Share on LinkedIn / Posts — publish posts as the authenticated member or organization.
• Marketing Developer Platform — manage organization Pages, ad campaigns, and analytics. Partner-approved.
• Community Management API — manage an organization's own posts, comments, and mentions. Partner-approved.
• Lead Sync & Conversions API — retrieve Lead Gen Form submissions and send conversion events.
• Talent / Recruiter System Connect — ATS integrations, partner-gated.
• Sales Navigator (partner API) — limited CRM sync for approved partners; no general search export.

The pattern is consistent: every product is about managing your account, your ads, or your Page — or signing a member into your app.

How official API access works

Official access uses OAuth 2.0 scopes tied to approved products — for example openid / profile / email for Sign In, w_member_social to publish, and rw_ads for the Marketing Developer Platform. You request a product, LinkedIn reviews it, and scopes are granted on approval. Crucially, there is no scope that grants another member's profile, a people or company search, or a message send — those products don't exist for general developers.

What the official API does not allow

LinkedIn is explicit in its API terms and restricted-use policy. Member data obtained through the official APIs cannot be used for:

• Sales, advertising, or recruiting use cases
• Identifying sales/marketing prospects or prospective hires
• Lead creation or building audience lists
• Enhancing or appending customer data in a CRM or marketing-automation platform
• Account-based marketing or ad targeting

The terms also prohibit exporting or transferring member data out of your app, combining it with your own or third-party data to build profiles or leads, and cap storage at 24 hours for profile data and 48 hours for activity data. Mass messaging is prohibited, and so are "headless" or fake accounts. Violations cost you API access.

The upshot: the things most teams want from LinkedIn — enrichment, people/company search, prospect lists, and outreach — are out of scope for the official API. There is no official endpoint to read an arbitrary member's profile, search LinkedIn, or send a 1:1 message or InMail programmatically.

Why there's a gap

This leaves a wide gap between what the platform can technically do and what the official API permits. Teams building CRMs, sourcing tools, sales-engagement platforms, and AI agents need to read profiles and companies, run searches, detect signals like job changes, and send messages — none of which the official API exposes. That gap is why a category of third-party LinkedIn APIs exists.

How third-party LinkedIn APIs fill the gap

Third-party LinkedIn APIs work differently: instead of your app acting as itself against LinkedIn's ad/Page endpoints, they act through a LinkedIn member session you connect — doing what that member could do in the browser, but as structured API calls. That's how you get profile and company data, search, enrichment, signals, and messaging the official API doesn't offer.

Edges is one such API — a LinkedIn Actions API with 70+ actions across:

• Data & enrichment — extract profiles and companies as structured JSON; resolve names and domains to canonical URLs.
• Search & lists — people and company search, Sales Navigator saved searches and lead lists.
• Messaging & outreach — send DMs, InMails, and connection requests on a connected seat, with per-identity pacing.
• Signals — job changes, hiring, and engagement as scheduled actions.

Reads can run on a managed identity pool (no LinkedIn account required); outreach runs on a seat you connect. Live reads are ~1.2s p50, and the platform is SOC 2 Type II.

Official vs third-party: which should you use?

Use the official API when the job is to manage your own presence — sign members in, publish posts, run and measure ads, or manage your Company Page. Use a third-party API like Edges when you need to read other members' or companies' public data, search, enrich a CRM, detect signals, or send outreach — the things the official API restricts.

Coverage map: what each API can actually do

The same landscape as a coverage map — the jobs developers actually need, and which API can do them (🚫 = unavailable or restricted, ✅ = supported):

• Read another member's full profile — Official 🚫 (only the signed-in user's basic profile). Edges ✅ — profile & company data.
• Search people or companies — Official 🚫. Edges ✅ — people & company search.
• Resolve a name or domain to a LinkedIn URL — Official 🚫. Edges ✅ — Find Profile / Company URL.
• Enrich a CRM with LinkedIn data — Official 🚫 (explicitly restricted). Edges ✅.
• Detect job changes & hiring signals — Official 🚫. Edges ✅ — signals API.
• Send a DM or InMail — Official 🚫 (no messaging endpoint; mass messaging prohibited). Edges ✅ — messaging API.
• Send & manage connection requests — Official 🚫. Edges ✅ — connect & invitations.
• Publish a post (as a member or Page) — Official ✅ (Share on LinkedIn). Edges ✅.
• Run & measure ad campaigns — Official ✅ (Marketing Developer Platform). Edges 🚫 (out of scope).
• Manage your own Company Page — Official ✅ (Community Management API). Edges 🚫 (out of scope).

Two honest takeaways: the official API wins for managing your own presence and ads; a third-party API wins for anything involving other members' data or outreach. They're complements, not substitutes.

A note on compliance

Third-party access sits in a space LinkedIn's official terms restrict, so treat compliance as a design constraint, not an afterthought. Edges runs on managed identities with per-account pacing and ramp-up, is SOC 2 Type II, and offers a DPA — but you remain responsible for how you use the data and your own LinkedIn ToS posture. This article is informational, not legal advice.

Common questions

Does LinkedIn have an official API?

Yes — but it's for managing your own presence: authentication, posting, ads, and Page and lead management. It does not expose other members' profiles, search, or messaging.

Can I get someone's profile data from the official LinkedIn API?

No. The official API only returns the authenticated member's own basic profile. Reading other members' profiles is not a supported use case, and enriching a CRM with member data is explicitly restricted.

Is there an official LinkedIn search or messaging API?

No public one. There's no people/company search product for general developers, and no official endpoint to send a 1:1 message, InMail, or connection request. See the LinkedIn messaging API for the third-party route.

How do third-party LinkedIn APIs get the data?

They act through a connected LinkedIn member session rather than LinkedIn's ad/Page endpoints — returning what that member can access, as structured JSON.

Is using a third-party LinkedIn API compliant?

It operates outside LinkedIn's official partner terms, so evaluate it for your use case. Edges reduces risk with managed pacing, SOC 2 Type II, and a DPA, but the decision — and ToS posture — is yours.

Want the capabilities the official API doesn't offer? Explore the Edges LinkedIn API or browse the full action library.