LinkupAPI Overview (2026): Features, Pricing & Limits
What the per-account ladder costs, how your users' accounts connect, the LinkedIn limits it recommends but leaves to you, and what its API and MCP server reach.
Guides and engineering notes on LinkedIn APIs, MCP servers and safe automation, written on the stack that runs 20,000+ LinkedIn accounts.
What the per-account ladder costs, how your users' accounts connect, the LinkedIn limits it recommends but leaves to you, and what its API and MCP server reach.
What a LinkedIn account costs on Woodpecker, the limits it sets by account type and the hours it sends in, and how much its API and MCP server reach.
What Breakcold's CRM does with LinkedIn, what each plan costs, the limits it publishes, and what its API and MCP server can send.
What a plan costs per LinkedIn account, the daily quotas each plan allows, and what its API and MCP server can send for you.
What a LinkedIn slot costs on top of the Sales Suite, the daily limits you set per action, and how much of LinkedIn its API and MCP server can reach.
How LinkedIn runs as one channel of a Reply.io sequence, what each plan charges for it, the daily limits per action, and what its API and MCP server reach.
Every limit, price, API quota and enforcement figure LinkedIn publishes about the activity automation tools run, each with its source. No estimates, and a list of the numbers LinkedIn leaves out.
The clause in the User Agreement, the limits, LinkedIn's own enforcement reports and the court record, each with its date. Then the 2026 crackdown stories, checked against their sources.
You can't look inside a vendor's stack, but you can read what it commits to in writing. Here is how to check that, and what each tool has on the record.
You want to try LinkedIn automation before paying for it, and almost every vendor says free somewhere. What that word buys you differs by a long way from one tool to the next.
Two products from one company: a LinkedIn app you pay for by the seat, and an API called We-Link you pay for by the credit.
Sales Navigator shows you up to 2,500 leads per search and gives you no file to take away. Evaboot builds that file on your own seat and bills you by the lead.
What a seat buys, the weekly limits you set on each profile, and how much of the product you can reach from its API and MCP server.
Getting ChatGPT to write the message was always the easy half. Sending it takes a server that holds your account and a workspace plan that allows writes.
A buying-signal product that sends from your own LinkedIn session, which makes the browser on somebody's desk part of the infrastructure.
A different company from Linked API, and a different kind of product: a read-only data API with no account attached and a rate limit that falls as you spend.
A Chrome extension costs little and keeps your login on your own laptop, and it stops when the laptop does. A cloud tool keeps going all night, with your account signed in on a server you don't run.
You want code or an AI agent to do on LinkedIn what a person does by hand. LinkedIn's own API will not, so the API that does acts on an account you connect.
The badge next to a name looks like a fact about that person. It is measured from your account, and it decides what LinkedIn lets you do next.
The address is almost never on the profile, so the tool that promises to scrape it is quietly doing something else, and the something else is where both the accuracy and the legal exposure live.
Two builds answer to the name, and the one you pick decides whether a bad afternoon costs you an IP pool or a LinkedIn account.
There is no single Apify LinkedIn scraper. There is a marketplace of them, and the one you pick decides what a run costs and whether your own LinkedIn session is anywhere near it.
Model quality decides how good the message reads. The account it sends from decides whether there is a second week of sending.
Three separate rulebooks govern a cold LinkedIn message, and each one punishes something different.
For agencies sizing it up: how sender rotation works, what a seat buys, and what the vendor publishes about its own LinkedIn presence.
Every action runs in one cloud browser held open for one connected account, and the seat it costs is what decides the fit.
You rarely lose an account to the invitation you sent this morning. You lose it to the pattern of the past few weeks.
Safety is in the name, and the two pages that put a number behind it do not put the same number.
You have probably been told a court made this legal. The same case ended with the scraper shut out of LinkedIn for good.
For the developers who built on it and the ones still finding it in old code: what the API was, what ended it, and where the work goes now.
Sizing it up before you build on it: what the API covers, how an account connects, what a linked account costs, and where its MCP server stops.
Two official APIs answer to the name, only one searches people, and the rows it returns have no job title in them.
The seat is not the expensive part. What the seat quietly refuses to do is what decides whether it pays.
Publishing is the one thing LinkedIn hands out with no application at all, and reading the same posts back is the thing it stopped handing out.
It is not on linkedin.com, it is not one set of docs, and its foundations were last touched in 2023.
The LinkedIn node n8n ships can only publish a post. Anything else takes a community node, and this page covers ours.
Searching for a LinkedIn jobs API is the obvious first move, and it returns the one product that cannot read a job listing.
The cheapest way to pull LinkedIn data is also the one most likely to cost you the account you meant to use it from.
Reach sags, invites sit unread, and nothing arrives in your inbox, because this is the one enforcement state LinkedIn applies without telling you.
Three workflows that invite, follow up on acceptance and route replies, with each account's daily budget kept on the server.
Both platforms ship a LinkedIn app of their own, and neither of those apps can send an invitation or a message.
Everyone who looks concludes the API does not exist. It does, and its terms are the discouraging part.
A counter you cannot see, on a limit support will not raise, quietly spent by a browser tab you forgot was open.
The message limit everyone goes looking for does not exist, and the one that actually stops you is not counted anywhere you can see.
One LinkedIn account, the full UI, API and MCP, no card. What runs unlimited, what runs on a daily allowance, and what stays paid.
Open the assistant in the docs, describe the play in plain English, and let it name the endpoints.
Reuse the GoLogin profile a sender already runs on. No new browser session, no LinkedIn re-login, no change to the proxy.
The obvious move is to paste the server into Claude's config file. Claude Desktop quietly discards it, and nothing in the app tells you why.
The obvious place to get a LinkedIn profile is LinkedIn, and it is the one source that will only ever return your own.
Creating the app takes ten minutes. Getting permission to call anything useful with it is the part with no timeline.
Sales tooling eventually reaches for the Sales Navigator API, and the form it points you at no longer leads anywhere.
You can design around a number you know. LinkedIn gives you one you can only find by hitting it.
Account-based APIs, scraper APIs and MCP servers compared, for developers shipping AI agents and platforms adding LinkedIn to a product.
Every cap in one place: invitations, messages, InMail, search, profile views and the network ceiling, per plan, with what actually resets when.
Adding accounts is the obvious way to send more, and it is also how you lose the ones you already have.
What the restriction message actually means, what reopens the account, and how to avoid a second one.
Twenty-seven vendors, nine ways to charge, sorted by what each one actually bills for, so a per-call number and a per-account number stop looking comparable when they are not.
The weekly ceiling, the daily send limit that differs per account, how the rolling window works, whether invites expire, and how sending capacity is actually earned.
For developers picking an integration path: what LinkedIn sanctions, what it doesn't, what the alternatives cost, and how to run one without losing the account.
Why accounts really get banned, the limits that keep them alive, and how to automate at volume without losing the account.
Point Claude, ChatGPT, or any AI agent at LinkedIn: find people, send invites and messages, and pull enriched profiles, on accounts that stay safe by design.
How a company brings a product to a market and turns it into revenue, from first principles to the AI-agent era.
Ranked by account safety and stability, on published specs and on how each tool actually runs, for teams that can't afford bans.