LinkedIn API for messaging and sales automation: what exists

LinkedIn has no open API for automated outreach. Its documented Messages API is restricted to approved partners under an API agreement, and its rules say a message must follow a specific member action, not an automated or scheduled event. Its Marketing API covers advertising. So tools that run outreach act through the member's own account, which LinkedIn's help pages say breaks its User Agreement.

If you build or buy sales automation for LinkedIn, the first question is how it talks to LinkedIn. Developers often search for "the LinkedIn API for messaging" and find the answer confusing, because LinkedIn has several APIs and none of them is what the outreach industry uses. This post reads LinkedIn's own developer documentation, says what each API is for and explains what that means for the choices you have and the risk you carry. It is a plain explainer, not legal advice.

What APIs does LinkedIn offer?

LinkedIn publishes developer documentation on Microsoft Learn. Three groups matter for sales teams.

The Advertising API has two access tiers, Development and Standard, which govern how many ad accounts an application can manage. LinkedIn's page on the tiers says access is reserved for applications building supported use cases, and that LinkedIn reserves the right to review applications and select partners at its discretion. None of that is about sending messages to prospects.

What does the Messages API say?

Its documentation opens with a note: "Usage of this API is restricted to approved partners, subject to limitations via API agreement." It describes a way for members to create messages to one or more first degree connections or reply to existing conversations. Then it lists requirements for posting a message:

• A message must be associated with a specific member action. Member actions do not include an automated or scheduled event.
• Members must opt in to sending the message, with a choice about whether to send it.
• A pre prepared message must be shown as an editable draft, and the member must take an affirmative action to send it.
• A message must be posted at, or around the time the member took action to send it.
• An application must not offer incentives to the member for sending a message, or to the recipients.

Read those lines as an outreach engineer would. The API exists for a member who clicks send in an application. It does not describe a system that decides on its own to message a thousand people overnight. Scheduled or automated sending falls outside the documented rules, and access itself is by approval.

What about Sales Navigator and the rest?

Sales Navigator is a LinkedIn product for searching and saving leads in the LinkedIn interface. We did not find a public developer route in LinkedIn's documentation that lets an outside tool send outreach through it. Some third party guides discuss partner programmes for integrations. We could not verify those claims against LinkedIn's own pages, so we do not rely on them. If you plan an integration, check LinkedIn's developer portal and partner pages directly.

Our post on Sales Navigator filters that find buyers covers how people use it by hand, and Sales Navigator vs a lead database compares the sources.

How do outreach tools work, then?

With no open messaging API, tools that automate LinkedIn outreach act through the member's own logged in account. The member connects the account, and the tool then performs actions on their behalf: visiting profiles, sending invitations and messages, reading replies. In Sellinger, you connect your own LinkedIn account through a hosted login, Sellinger does not store your LinkedIn password, and access runs through our connection provider, Unipile. You can also connect through your own proxy.

This is not a loophole in the API rules. It is a different route, and LinkedIn's position on it is stated in its help pages: LinkedIn says third party tools that scrape, modify the appearance of or automate activity on its site violate its User Agreement, and members who use them risk restrictions. Our post on LinkedIn terms of service and automation quotes the page and goes through what it covers.

What does that mean for risk?

Honestly: automation on LinkedIn carries a risk of restriction, and no tool can remove it. What a tool can do is reduce the chance of a problem and give you control.

The defaults are in code and can be changed per account. Higher limits do not make a campaign better and they raise the odds of trouble. Our LinkedIn safety checklist for AI outreach and the post on whether LinkedIn automation is safe go through the rest, including what to do if an account is restricted.

Should you build on the official API instead?

For some jobs, yes.

• A product feature where a member sends a message from inside your app. The Messages API fits, if you can become an approved partner and accept the agreement.
• Advertising. Use the Marketing API for ad accounts, campaigns and lead sync.
• Sign in. Use LinkedIn's sign in flow.

For autonomous outreach, the official route is closed by design. A company that tells you it uses the official API to run scheduled outreach at scale deserves a hard question: which API, under which agreement, and where is it documented?

What should you ask a vendor?

1. How does your tool connect to LinkedIn: official API or the member's session?
2. What are the default limits, and can I change them?
3. What happens when LinkedIn restricts an account?
4. Do you store my password?
5. Do you promise that accounts will never be restricted? (If yes, be wary.)
6. Who sends from the account, and can I keep a person in the loop?

Our buyers checklist for AI SDRs has the full list.

What does a careful setup look like?

The Lamothermic case study is a small, careful example. A foundry's president runs the Sellinger agent on his own LinkedIn profile. The agent asks one real engineering question, follows up every five days and hands every buying signal to him. Of 879 engineers and buyers messaged, 293 replied (33%), and the follow ups cost almost no goodwill: 7 negative first replies across 1,699 follow up recipients. It is one profile run gently, with a person reading the threads. See the case study.

A short summary

• LinkedIn's Messages API is restricted to approved partners and ties messages to a specific member action.
• The Marketing API is about advertising.
• Outreach tools act through the member's own session, and LinkedIn says that breaks its User Agreement.
• No tool can guarantee that an account will never be restricted.
• Use limits, quiet hours, approval and a human who reads the threads.