The short answer: The LinkedIn API is a set of programs documented on Microsoft Learn, organized by business line: Consumer, Compliance, Learning, Marketing, Sales and Talent. LinkedIn’s docs, read Nov 15, 2026, say most permissions need LinkedIn’s approval and that only Open Permissions are available to every developer. Those cover Sign in with LinkedIn and Share on LinkedIn.
We make a LinkedIn outreach tool. This page describes what LinkedIn’s developer programs offer, so you can see where a tool like ours sits.
What does the LinkedIn API offer?
LinkedIn’s API documentation home, read 2026-11-15, is organized by business line:
- Consumer: Sign in with LinkedIn using OpenID Connect, Share on LinkedIn, Verified on LinkedIn and plugins.
- Marketing: the Advertising API, for which LinkedIn says developers “must be approved.”
- Talent: programs such as Apply Connect, Job Posting, Recruiter System Connect and CRM Connect, through partner applications.
- Learning: LinkedIn Learning integrations, by requesting access.
- Sales: the Sales Navigator Application Platform, for approved partners.
- Compliance: listed for reference, with the page saying access is closed and may not be requested.
Which parts of the LinkedIn API are open to every developer?
Three permissions. The page Getting Access to LinkedIn APIs, read 2026-11-15, says “Open Permissions are the only permissions that are available to all developers without special approval.” It lists:
| Product | Permission | What LinkedIn says it does |
|---|---|---|
| Sign in with LinkedIn using OpenID Connect | profile | Retrieve the authenticated member’s name, headline and photo |
| Sign in with LinkedIn using OpenID Connect | Retrieve the authenticated member’s primary email address | |
| Share on LinkedIn | w_member_social | Post, comment and like posts on behalf of an authenticated member |
LinkedIn’s Share on LinkedIn page, read the same day, lists rate limits of 150 requests a day per member and 100,000 a day per application. Its general rate-limit page says standard limits for other endpoints aren’t published in the documentation, and that you can look yours up in the Developer Portal.
Does LinkedIn have an API for messaging?
Not among the open permissions. The Open Permissions table above has no permission for sending connection requests or messages. A LinkedIn API for messaging, in the sense of sending a message to a lead from your own software, isn’t in the open list.
The nearest thing in the docs is the Sales Navigator Application Platform. Its Display Services page, read 2026-11-15, describes UI modules, embedded in a partner’s application, for “connecting and sending messages (including InMail) to leads.” The same page carries a note: “We are not currently accepting new partners for access to the LinkedIn Sales Navigator API.” Its Analytics Services export activity data, such as searches, profile views and InMail, for approved partners only.
So a team that wants a tool to send connection requests and messages from its own accounts can’t get that through LinkedIn’s open APIs. We found no open program that does it.
How do outreach tools work without that API?
They act through the member’s own session. In our tool you connect each LinkedIn account yourself, either by pasting that account’s linkedin.com cookies, exported with the third-party Cookie-Editor extension, or by signing in with its email and password. We then run the account’s activity through a dedicated residential proxy per sender, chosen by country or your own. It is the account holder’s session, not a LinkedIn developer integration, and we don’t create, rent or sell LinkedIn accounts. See connect a LinkedIn account with Cookie-Editor.
Each sender then sends within its own limits: 15 connection requests a day (up to 25), 100 a week, and 40 messages a day (up to 80), from Monday to Friday, 09:00 to 18:00 in the sender’s time zone. With five senders, that is up to 500 connection requests a week across the team. We charge $29 per connected sender a month, with every feature on every plan.
What about a LinkedIn automation API from us?
Our API is ours, not LinkedIn’s, and it works on our campaigns. LinkedIn automation API is a loose phrase, so to be exact: our API key lets your software list campaigns, add leads, pause or resume a campaign and stop a lead, create lists and add leads to them, read leads with their lists, campaigns, state and tags, and read and reply to conversations.
Our webhooks send events to your endpoint, with a campaign filter and custom headers: connection.sent, connection.accepted, message.sent, message.replied, message.received, lead.tagged, lead.finished and campaign.finished. That is how a reply can reach Slack or your CRM. We have no native CRM sync in the first version, so the webhooks and API are the hand-off. None of this calls LinkedIn’s APIs for you.
What this page can’t tell you
We read LinkedIn’s documentation on Microsoft Learn. We couldn’t read developer.linkedin.com, which returned an access error to us, so we don’t describe it. LinkedIn updates these programs, and the docs for approved partners may go further than the public pages. Check the Microsoft Learn pages and your Developer Portal before you plan an integration.
Sources, read 2026-11-15
- LinkedIn API documentation: business lines and programs.
- Getting Access to LinkedIn APIs: Open Permissions, approvals, closed Compliance access.
- Share on LinkedIn: permission and rate limits.
- LinkedIn API rate limiting: limits not published for standard endpoints.
- Sales Navigator Application Platform documentation: Display Services, not accepting new partners.
- Sales Navigator Analytics Services: partner-only activity export.