# Official LinkedIn APIs versus unofficial access
> LinkedIn's developer platform covers ads, some Page features, auth, and partner programs. Personal invite bots and scrapers are a different, riskier category.
- HTML: https://omentir.com/linkedin-api
- Markdown: https://omentir.com/linkedin-api.md

## Start in the docs, not in a GitHub gist

The [LinkedIn Developer docs](https://learn.microsoft.com/en-us/linkedin/) are the source of truth for what Microsoft will issue tokens for. Today that public story includes Sign In with LinkedIn (OpenID), Marketing Developer Platform for ads and related advertising objects, Community Management APIs for organization Pages, and other products that require a developer application and, often, an access request. Sales Navigator has a partner program (SNAP) for approved integrations. None of that is a secret. None of that is a personal-inbox takeover.

If you are building a product, you apply, you scope permissions, you pass review for the APIs that require it, and you live inside rate limits. If your product idea is 'send 200 connection requests a day from the user's profile,' the docs will not hand you that endpoint. That is the whole article for a lot of startups, and it is the one they skip.

*If a vendor says they use 'the LinkedIn API' for outbound DMs, ask which product and which partnership.*

## What official APIs are for

Marketing APIs are how a legitimate ads tool creates campaigns, pulls reporting, and syncs audiences without scraping Campaign Manager. Community Management is how a social inbox might read and reply to comments on a company Page the company administers. Sign In with LinkedIn is how a member proves who they are to your app without you storing a password. Partner Sales APIs, where granted, are how a CRM might show Navigator data to a rep who already pays for Navigator.

Those are integrations. They assume the user or the company already has the LinkedIn product (an ad account, a Page admin role, a Navigator seat). They do not replace LinkedIn. They sit next to it.

## What unofficial usually means

Unofficial access means a session cookie, a mobile-app protocol, a browser bot, or a third-party 'LinkedIn API' vendor that is not in Microsoft's partner list for that action. The engineering can be tidy. The terms are still LinkedIn's. Detection, checkpoints, and account restriction are the enforcement mechanisms. A wrapper that encrypts the cookie is a security choice. It is not permission.

Libraries on GitHub that 'just work' against linkedin.com will break when LinkedIn changes an internal endpoint. They also tend to concentrate risk: one shared integration pattern becomes easy to fingerprint. If you ship that in a SaaS, you are in the automation-software business, with all of the account-risk honesty that category requires. Do not tell customers it is official.

## How to ask a vendor the only useful question

Ask: 'Which LinkedIn product and which documented API, or is this session-based automation?' Demand a docs URL. If they say 'we use an API partner' for member DMs, ask whether that partner is a Microsoft-listed SNAP or Marketing partner for that use case, or a messaging gateway that holds sessions. The second can be a reasonable architecture for a sequencer. It is still unofficial relative to LinkedIn's public developer platform. Your security review should treat it that way: token handling, data residency, and what you will do when LinkedIn locks a profile.

## What not to build

Do not scrape the graph to resell contacts. Do not store member passwords. Do not market a reverse-engineered client as 'the LinkedIn API.' If your use case fits Marketing or Community Management, build that and apply. If it does not, you are choosing unofficial automation on purpose. Write that down for your users instead of hiding it in a compliance footnote.

## Related

- [LinkedIn updates: changelog versus algorithm gossip](https://omentir.com/linkedin-updates.md)
- [Automating LinkedIn outreach: invites and follow-ups](https://omentir.com/linkedin-outreach-automation.md)
- [What Dripify is and who it fits](https://omentir.com/dripify.md)

## Common questions

**Is there an official API for connection requests?**

Not as a public, self-serve outreach API for member profiles. If a partner program exists for a narrow use case, it will be documented and gated. Assume no until Microsoft's docs say yes.

**Does using OAuth mean my outreach tool is official?**

OAuth for Sign In with LinkedIn proves identity. It does not authorize bulk invites. Official status is about the product and permission, not about whether a token looks like OAuth.

[Create an Omentir account](https://omentir.com/signup). Pro is $49/month.