LinkupAPI Overview
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.
LinkupAPI is an API for developers and AI agents that acts on their users’ own LinkedIn, email, WhatsApp and iMessage accounts from its servers. It sends invitations, messages and InMails, reads profiles and searches, and posts and comments, through one endpoint per category with the action in the request body. It is priced per connected account, $55 a month for up to ten and less per account above that, with no per-call fees. LinkedIn’s limits are left to LinkedIn: LinkupAPI publishes recommended daily numbers and does not enforce them, and a hosted MCP server exposes the same actions to AI assistants.
On this page
What LinkupAPI is
LinkupAPI calls itself “The outreach API for your AI agents”: “Reach your prospects on LinkedIn, Email, WhatsApp and iMessage through a single powerful API. Built for AI agents and software.” Its documentation adds that it connects “your product or AI agent” to those channels “to automate outreach, find contacts, and gather market insights for sales and recruitment”.
It is a developer product. There is no campaign app on top. Your code or your agent decides what to send and when, and LinkupAPI carries it out on accounts your users connect: “Send messages, InMails, invitations, Sales Navigator and more from your users’ own accounts.” It runs on its own servers, “100% cloud-based”, with “no browser extension, nothing installed on your users’ machines”. The company is LINKUPAPI SAS, registered in Paris, and its data “is processed and hosted in the European Union”.
How an account connects and sends
“One account = one LinkedIn profile, one Gmail or Outlook mailbox, or one WhatsApp number.” A LinkedIn account connects in one of three ways.
- A hosted page. “Let your users connect their LinkedIn, WhatsApp or email account on a page hosted by LinkupAPI, so their credentials never reach your servers”. The page can run on your own domain with your name and logo.
- Credentials over the API. An email and password, with any two-factor check answered through a separate checkpoint call.
- A session token. A LinkedIn cookie in place of the password.
Sales Navigator and Recruiter seats attach to the same login. Each account gets a proxy in a country you pick, France by default, from 52 countries, and the country can be changed later with the account’s device identity kept, or you can supply your own proxy. LinkupAPI states that “we never keep your users’ passwords” and that sessions are “isolated per account and revocable at any time”.
Once connected, every channel is reached the same way: one URL per category, with “the action in the request body instead of calling different URLs”. Replies, accepted invitations and bounces arrive by webhook or through an events endpoint.
LinkupAPI pricing
LinkupAPI meters one thing: connected accounts. “No credits, no per-call fees. Only each platform’s own limits apply.” Prices are in US dollars, before VAT, billed monthly, and the pricing page carries no date stamp.
| Connected accounts | Price | LinkupAPI’s example |
|---|---|---|
| Up to 10 | “$55 a month, flat” | $55 for 10 accounts |
| 11 to 50 | $5.50 per account | $275 for 50 accounts |
| 51 to 200 | $5.00 per account | $1,000 for 200 accounts |
| 201 to 640 | $4.50 per account | $2,880 for 640 accounts |
| Unlimited | “$3,000 a month, flat” | Any number of LinkedIn, email and WhatsApp accounts |
Every tier includes “Every endpoint on every channel, plus Sales Navigator, Recruiter and the MCP server”. The plan is billed upfront each month, and accounts added during the month “are billed at the end of the cycle, on the peak number connected at the same time”. Auto-upgrade can be switched off to cap the number of accounts. Email enrichment is the one thing that still uses credits. An iMessage line is an add-on at $199 a month.
The terms give a 7-day free trial, “offered once per customer”, that needs a payment method. There is no free plan and no published yearly price. The documentation’s own pricing summary, “$55 for the first 10 accounts, then $5.50 per extra account, capped at $3,000/month”, leaves out the $5.00 and $4.50 tiers the pricing page shows.
The limits LinkupAPI publishes
LinkupAPI does not cap LinkedIn activity itself: “We don’t enforce any limits on our side”, so “you’ll hit the exact same limit as in the LinkedIn UI.” Its homepage puts the stance as “We don’t impose blind daily limits”, with health tracking and an alert when an account gets flagged. The terms add an account-protection layer, with “cooldowns after provider warnings” that “may delay or pause actions on an account showing signs of a provider restriction”. The documentation then publishes recommendations, framed as “conservative recommendations. You may increase them at your own risk.”
| Action | LinkupAPI’s recommendation |
|---|---|
| Invitations, paid LinkedIn account | 80 to 100 a day, about 200 a week |
| Invitations, free LinkedIn account | About 150 a week without a note, about 5 a month with one |
| Profile views and profile data | About 100 per account a day |
| Messages and InMails | 30 to 50 a day each |
| Searches | About 1,000 profiles a day, at most 1,000 per query |
| Posts | 1 to 2 a day |
| Comments and reactions | About 100 a day |
| Any other action | About 100 a day per account |
The rest of the guidance is also for the developer to apply: a new or inactive account should “start with low volumes and increase gradually over 2-3 weeks”, actions should be spread across business hours, and requests should use random delays. When LinkedIn limits an account, the API returns an error such as LINKEDIN_RATE_LIMITED, and the advice is to pause that action on the account. iMessage is the exception, where LinkupAPI “checks the sending rules before each send and refuses a send that would break them”. LinkedIn’s own published numbers are compiled on LinkedIn automation statistics.
The LinkupAPI API
The current API is version 2, at api.linkupapi.com/v2, with the API key in an x-api-key header. “Each category has a single endpoint”: profiles, messages, network, content, recruiter, mail, credits and webhooks, with accounts and connection links beside them.
- Size. LinkupAPI says “50+ endpoints”. Its documentation index lists 78 version 2 actions, counted on 3 November 2026, and 50 of them are LinkedIn-only: profiles, network, content and recruiter. Messages and accounts are shared across channels.
- LinkedIn sends. Invitations, messages, InMails, posts, comments and reactions, and withdrawing invitations, all as actions in the request body.
- Rate limits. No number is published. A 429 means “Too many concurrent requests on your key, or LinkedIn limited the account.”
- Version 1. “V1 will be deprecated”, with no date given, and the OpenAPI file LinkupAPI publishes is still the version 1 specification.
Webhooks push replies, accepted invitations and bounces “in real time, with retries and a delivery log”, and the events endpoint keeps events for 30 days. Make, n8n and Zapier connect through a plain HTTP request, with no native app.
The LinkupAPI MCP server
LinkupAPI runs a hosted MCP server at https://mcp.linkupapi.com/mcp: “One URL for every client. Nothing to install, nothing to host.” It signs in with “OAuth 2.1 (recommended)”, approved from the LinkupAPI dashboard, or with the API key in a header, and the documentation names Claude, ChatGPT, Cursor, Gemini CLI, VS Code and Windsurf.
- Tools. “Every LinkupAPI capability becomes a native tool”, from finding prospects and sending LinkedIn messages to reading the inbox, engaging on posts and recruiting. The number of tools is not published.
- Confirmation. No server-side confirmation step is documented. A LinkupAPI article on connecting Claude says “You stay in the conversation to approve what goes out”, without naming the mechanism.
- Cost. “Nothing on top of the API. Tool calls follow your LinkupAPI plan.”
The shape of job it fits
LinkupAPI fits a developer building outreach into a product or an agent, with many end users who each connect their own LinkedIn, email or WhatsApp account. The hosted connection page under your own brand, the per-account ladder that gets cheaper with volume, and the flat $3,000 tier for an unlimited number of accounts all point at software with many users. The MCP server gives an assistant the same reach with no extra cost.
The edges follow from leaving decisions to the developer. LinkedIn limits, pacing, warm-up and working hours are recommendations your code has to apply, and the API’s own rate limits have no published number. The MCP tool count and any server-side confirmation are not documented. And version 1 is on its way out without a date.
LinkupAPI alternatives
GTM API is our own product, so it is listed first. The others are described from their own pages, in alphabetical order. They split by job: APIs for building LinkedIn into a product or agent, and campaign apps that come with their own interface.
| Tool | How it runs | Price unit and entry | API | MCP server |
|---|---|---|---|---|
| gtm-api.com, ours, listed first | A cloud browser and proxy per connected account, driven over REST or MCP | Per connected account: free plan with one account and no card, then from $10/account | Typed REST, a daily budget per action checked on the server before each call | Hosted, 250+ typed tools, sends return a preview to confirm |
| HeyReach | Cloud app that rotates one campaign across many connected senders | Per sender: $79 a month on Growth, teammates free | API and webhooks on every plan | Hosted, per-workspace URL |
| Reply.io | A sequencer for email, LinkedIn, calls and messaging | Per user: LinkedIn included from $89 a month billed yearly on Multichannel | REST v3 with LinkedIn sends | Hosted, no LinkedIn sends |
| SalesRobot | Cloud app with a dedicated IP per LinkedIn account | Per LinkedIn account: $39 a month billed yearly on Basic | REST, including connection requests and messages | Hosted, sends included |
| Unipile | A multichannel API on the accounts your users connect | Per linked account, priced in volume bands | REST, LinkedIn and other channels | Developer MCP server |
Read the table by job. To build LinkedIn into your own product or agent, LinkupAPI, Unipile and GTM API are APIs on your users’ accounts, and they differ in who holds the daily limits: LinkupAPI and Unipile leave them to the caller, while GTM API checks a budget on the server before each call. For a team that wants a campaign app with its own interface, HeyReach and SalesRobot are priced per account and Reply.io puts LinkedIn next to email. How APIs in this category divide the budget is on LinkedIn automation API.
Frequently Asked Questions
How much does LinkupAPI cost?
$55 a month covers up to 10 connected accounts. Above that each account costs $5.50 up to 50, $5.00 up to 200 and $4.50 up to 640, and $3,000 a month covers an unlimited number. Prices are in US dollars before VAT, with no per-call fees, and a 7-day trial needs a payment method.
Does LinkupAPI limit LinkedIn actions?
No. “We don’t enforce any limits on our side”, its documentation says, so an account meets LinkedIn’s own limits. LinkupAPI publishes recommendations instead, such as 80 to 100 invitations a day on a paid account and 30 to 50 messages, and pauses an account after a provider warning.
How do users connect a LinkedIn account to LinkupAPI?
Through a connection page hosted by LinkupAPI, which can run on your own domain, or over the API with an email and password or a LinkedIn session token. Each account gets a proxy in a chosen country, and Sales Navigator and Recruiter seats attach to the same login.
Does LinkupAPI have an MCP server?
Yes, hosted at mcp.linkupapi.com/mcp with OAuth 2.1 or an API key, at no extra cost. Every API capability is a tool, including sending LinkedIn messages and invitations. The number of tools and any server-side confirmation step are not published.
Is LinkupAPI the same as Linkup?
No. LinkupAPI, at linkupapi.com, is a Paris company selling an API for LinkedIn, email, WhatsApp and iMessage accounts. Linkup is a separate web search API.
What are the alternatives to LinkupAPI?
Unipile is another API on users’ own accounts that leaves limits to the caller. HeyReach, SalesRobot and Reply.io are campaign apps with their own interface. GTM API, our own product, is an API and MCP server that checks each account’s daily budget on the server before a call, from $10/account with a free plan.
Sources & Further Reading
- LinkupAPI, homepage · pricing · MCP · n8n, Make and Zapier · terms of use (last updated 12 October 2026) · legal notice · connecting Claude, read 2026-11-03
- LinkupAPI developer documentation, introduction · index · best practices · error codes · account login · connection link · MCP setup · V1 to V2 migration · webhook events, read 2026-11-03
- Related: LinkedIn automation API · Best LinkedIn API · Unipile overview · Safest LinkedIn automation tools · LinkedIn automation statistics
LinkedIn actions as typed API calls.
Connect an account server-side, send a connection request or a message as one endpoint, and read the limits before the call goes out. The same contract runs as an MCP server for your agent. Free plan with one connected account, then from $10/account.
Last updated: November 2026 · Definitions and benchmarks verified at time of publication