LinkedIn automation tools: what the API allows and what gets accounts restricted

LinkedIn automation tools split in two. One family drives your account the way a human would, which LinkedIn's User Agreement forbids. The other calls the official API, which lets you post, comment and like, and nothing else without approval. Seven tools below, with prices and limits checked on October 15, 2026.

That split matters more than any feature list, because it decides who carries the risk. An API-backed tool can be throttled. An account-driving tool can get your profile restricted.

The three families of linkedin automation software

Every tool in this market belongs to one of three groups.

Account drivers. They log into LinkedIn as you, from a browser extension or from their own servers, and click what you would click: connection requests, profile views, messages, endorsements. Dripify and Waalaxy are the well-known ones. They can do things no API exposes, which is exactly why they are outside the rules.

API-backed publishers. They hold an OAuth token with the w_member_social permission and call https://api.linkedin.com/rest/posts. Buffer, Later, Metricool and Hootsuite work this way. They publish, schedule and report. They cannot send a DM, because there is no self-serve endpoint for one.

Agent plugs. Same official API, different consumer: an MCP server or REST API that an AI agent calls, so the agent writes the post and publishes it in one turn. PlugKit is in this group.

What the official LinkedIn API allows

This is the part most listicles skip. LinkedIn publishes an exact list of what any developer can get without applying for anything, and it is short. From the Getting Access page, read on October 15, 2026:

"Most permissions and partner programs require explicit approval from LinkedIn. Open Permissions are the only permissions that are available to all developers without special approval." Those open permissions are the three top rows.

Read the consequence carefully: with a self-serve app you can publish to your own profile and comment as yourself, but you cannot read the comments on your own post. Reading needs r_member_social, which LinkedIn grants to approved developers only. That single asymmetry explains why so many schedulers show you LinkedIn post counts but no LinkedIn engagement.

On content, the Posts API accepts text, images, video, documents, articles, multi-image posts, polls and celebrations as organic posts. Organic carousels are not supported; carousels are sponsored only. Rate limits for the self-serve Share on LinkedIn product are 150 requests per member per day and 100,000 per application per day.

What gets accounts restricted

LinkedIn's User Agreement, section 8.2, is unambiguous. Item 2 forbids members to "Develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services". Item 13 forbids members to "Use bots or other unauthorized automated methods to access the Services".

An account driver does both by design. Whether it runs as a Chrome extension on your laptop or on a vendor's server makes no difference to the clause: it is still unauthorized automated access to your account. The vendors know it, which is why their pages advertise "LinkedIn protection" and daily caps meant to look human.

Messaging deserves its own paragraph, because it is the single feature people buy these tools for. LinkedIn's Messages API is "restricted to approved partners", and even approved partners are told that "a message must be associated with a specific member action" and that "member actions do not include an automated or scheduled event". The member must also opt in to each send and be able to edit the draft. There is no compliant way to run a cold-DM sequence on LinkedIn. A tool that offers you one is routing around the rule, with your profile as the collateral.

Prices and capabilities, checked October 15, 2026

Each figure comes from the vendor's own pricing page, read today. Account drivers are priced per user; API-backed tools are priced per channel, per brand or per social set, which is why the columns are not directly comparable.

The "DMs" and "reads engagement" columns are the honest summary of this whole market. Only the account drivers offer those two, and only by breaking section 8.2. Every API-backed tool in the table, PlugKit included, says no to both because LinkedIn says no.

linkedin post automation: the API route

If publishing is what you actually need, the compliant path is short. The same shape appears in our social media API guide, and the per-platform ceilings are collected in the rate limits table. One thing an API-backed tool does not do is write into LinkedIn's native scheduled list, so see scheduled posts on LinkedIn if you expected to find your queue there.

1. Create an app in the LinkedIn Developer Portal and add the Share on LinkedIn product. That grants w_member_social with no review.
2. Run the OAuth authorization code flow, store the member token, refresh it before it expires.
3. POST https://api.linkedin.com/rest/posts with the Linkedin-Version: YYYYMM and X-Restli-Protocol-Version: 2.0.0 headers. A 201 comes back with the post URN in x-restli-id.
4. Keep your own copy of what you published, because you cannot read it back without r_member_social.

Steps 1 to 3 are a week of work per platform, which is the whole argument for a hosted layer. PlugKit does the token handling and exposes LinkedIn publishing to an agent over MCP, the same way it does for Instagram in the Instagram MCP server guide and the way an agent reaches every connected account in the Hermes Agent setup. Be clear about the ceiling: PlugKit publishes text, up to 20 images or one video to your LinkedIn profile, and it does not do LinkedIn comments, LinkedIn DMs or LinkedIn analytics, because the open permission set does not include them.

Which family should you pick

If you want a connection and messaging machine, you are choosing an account driver and accepting that your profile is the stake. Nobody can sell you that risk-free, whatever the pricing page says.

If you want LinkedIn to be one of several accounts an agent posts to, pick an API-backed tool and keep your engagement work manual. That is the trade LinkedIn currently offers, and it has been stable for years. The same logic plays out on Instagram, where the official API is far more generous: see the Instagram automation tools list for the contrast.

FAQ

Is LinkedIn automation allowed?

Publishing through the official API is allowed and expected: that is what the w_member_social permission is for. Driving your account with a bot, an extension or a cloud agent that logs in as you is not. LinkedIn's User Agreement section 8.2 forbids bots and unauthorized automated methods of accessing the service, and that covers both extensions and server-side drivers.

Can LinkedIn automation tools send messages?

Not compliantly. The Messages API is restricted to approved partners, and those partners are required to tie each message to a specific member action, which explicitly excludes automated or scheduled events. Tools that sell LinkedIn DM sequences are driving your account rather than calling the API.

Will LinkedIn ban me for using automation tools?

Accounts get restricted rather than deleted, usually after a burst of activity that does not look human. The pattern matters more than the tool: a few dozen actions a day spread over hours rarely trips anything, while hundreds in an hour does. There is no safe number published by LinkedIn, which is the point.

What is the cheapest way to automate LinkedIn posts?

Writing against the API yourself costs nothing but your time, and the Share on LinkedIn product is self-serve. If you want it hosted and reachable from an agent, PlugKit is $49 a month for 5 connected accounts, cancel anytime. Buffer starts at $5 per channel per month if you only need a calendar.

Can I automate a LinkedIn company page?

Yes, but it needs approval. Posting as an organization uses w_organization_social, which requires the Community Management API and a LinkedIn review, plus an admin role on the page. Self-serve apps can only post as the member who authorized them.

AB

Antoine BlancoFounder of PlugKit. Runs his own Instagram, YouTube and X accounts through the API and MCP server described here.