Compare

Swarmhit vs LinkupAPI

LinkupAPI sells raw LinkedIn, WhatsApp and email endpoints per connected account, and leaves the sequencer, the inbox screen, and LinkedIn pacing to your code. Swarmhit sells two APIs: a Raw API at the same layer, with a sign-in that carries 2FA and CAPTCHAs through and limits enforced before LinkedIn sees a call, and a Smart API that runs the whole campaign on LinkedIn, email and WhatsApp. New to LinkupAPI? Start with our full LinkupAPI review.

  • Sequencer built in
  • 250+ safeguards monitored 24/7
  • API and webhooks

Swarmhit

Built in

Sequencing and throttling

Branching, delays, schedules, retries and multi-sender rotation run on our side.

LinkupAPI

None

“No campaign builder, no settings”, in its own words; your queue, your delays.

Swarmhit

250+

Safeguards, monitored 24/7

Dedicated proxies, managed warmup, health checks and smart sending caps on every send.

LinkupAPI

No limits

No LinkedIn limits enforced on its side; published recommendations only.

Swarmhit

1B+

Contacts, 60M companies

Prospect database refreshed weekly, plus Sales Navigator imports.

LinkupAPI

Lookups

A prospect data API; email finder and verifier billed in credits at an unpublished price.

Swarmhit

$16.90

Per LinkedIn sender, tiered

Down to $6.90 as the fleet grows; sequencer, proxies and warmup included.

LinkupAPI

$55/mo

Up to 15 accounts, then $3.70 down to $3.00 each; raw endpoints only, the outreach layer is your build.

Swarmhit has two APIs. So there are two comparisons.

The Raw API sits at the same layer as LinkupAPI: one endpoint per action. The Smart API sits one layer up: it runs the whole campaign on LinkedIn, email and WhatsApp, with the logic handled.

Raw API vs LinkupAPI

Same layer, one endpoint per action on both sides: sign-in, limits, retries and events. The Raw API is in early access.

Shape and channels

What you call
Swarmhit Raw APIOne endpoint per action; your code decides when, how fast and what comes next
LinkupAPIOne POST endpoint per category, the action chosen by a field in the body; your code decides what comes next
Channels
Swarmhit Raw APILinkedIn, WhatsApp (early access) and email, on the same paths, bodies, errors and events
LinkupAPILinkedIn with Sales Navigator and Recruiter, WhatsApp, email, and iMessage lines as an add-on

Signing accounts in

2FA
Swarmhit Raw APISend the account's authenticator secret once and Swarmhit answers 2FA by itself, at connect and on every later sign-in
LinkupAPIA checkpoint per code (email, SMS, authenticator app, app approval); the person types each code; no authenticator-secret field in the connect reference
CAPTCHA
Swarmhit Raw APIA live view: the real sign-in browser streamed over a websocket, taking clicks and keys, so the person solves it inside your product, unknown steps included
LinkupAPINot covered in the connect reference
Hosted connect page
Swarmhit Raw APIOn the Smart API: a one-time link under your organization's name and picture
LinkupAPIA single-use hosted link for LinkedIn, WhatsApp and email, with your brand name, your logo and a custom domain
Placement
Swarmhit Raw APIEach account keeps its own browser identity and a sticky IP in the country you choose; reconnects reuse them
LinkupAPIA dedicated IP per account in the country you choose, France by default, or your own proxy

Safety and retries

What gets refused
Swarmhit Raw APIOne write at a time per account, a gap between writes, daily caps per kind of action, and a rest after LinkedIn pushes back; all refused before anything reaches LinkedIn
LinkupAPI“We don't enforce any limits on our side”, in its own docs: recommendations only, and LinkedIn's own refusals come back as 429 or 500
Sending twice
Swarmhit Raw APIIdempotency-Key on email, client_id on WhatsApp, and unless_replied_since to skip a follow-up the lead already answered
LinkupAPINo idempotency mechanism documented for sends
Webhooks
Swarmhit Raw APISigned with HMAC SHA-256 over the raw body, a separate sandbox webhook
LinkupAPIHMAC SHA-256 signing opt-in and off by default; retries, a delivery log, replay, and an SSE mode with 30 days of history; the connect-link callback is unsigned
Testing
Swarmhit Raw APISandbox keys with test credentials for a checkpoint, a wrong password or a restricted account, never billed
LinkupAPINo sandbox documented; a free trial

Comparison data last verified on 14 November 2026.

Smart API vs LinkupAPI

Raw outreach endpoints per account versus an engine that runs the campaign on LinkedIn, email and WhatsApp, feature by feature.

Build outreach into your product

What the API drives
Swarmhit Smart APICampaigns, sequences, senders, leads, and inbox as first-class resources
LinkupAPI50+ endpoints for LinkedIn, WhatsApp and email actions, plus prospect data and email finder lookups
Raw endpoints
Swarmhit Smart APIAlso sold: the Raw API, in early access, one endpoint per LinkedIn, email or WhatsApp action on the same infrastructure
LinkupAPIRaw endpoints are the whole product, LinkedIn, WhatsApp and email
Sequencer
Swarmhit Smart APIBuilt in: branching, delays, schedules, retries, automatic multi-sender rotation
LinkupAPINone: its docs tell you to run calls through your own queue with random delays, and its campaign tutorial is a recipe you host
Channels
Swarmhit Smart APILinkedIn, email and WhatsApp (early access), in one sequence
LinkupAPILinkedIn including Sales Navigator and Recruiter, WhatsApp, email from Gmail, Outlook or any SMTP and IMAP mailbox, and iMessage lines as a $199 add-on
Prospect data
Swarmhit Smart API1B+ contact database, 60M companies, refreshed weekly; Sales Navigator imports
LinkupAPIProspect data API for people, company, job and funding data; email finder and verifier billed in credits

Protect the accounts

Account safety
Swarmhit Smart API250+ safeguards monitored 24/7: dedicated proxies, managed warmup, health checks, smart sending caps
LinkupAPIDedicated IP per account; on LinkedIn it enforces no limits of its own and publishes recommendations instead
Sending limits
Swarmhit Smart APIPer-sender limits enforced server-side on every send
LinkupAPIRecommended 80 to 100 invitations and 30 to 50 messages a day on a paid account; nothing stops your code from going past them
Who carries the risk
Swarmhit Smart APISwarmhit operates pacing, per-sender limits and account health checks
LinkupAPIYour team: its terms exclude liability for restrictions by LinkedIn or other providers, and it enforces no LinkedIn limits of its own

Manage replies

Inbox
Swarmhit Smart APIInbox API: every sender's replies in one place, readable and answerable through the API, with AI interest classification and message.received webhooks
LinkupAPIMessage and inbox endpoints plus real-time webhooks; the inbox product is your build

Integrations and events

Webhooks
Swarmhit Smart APISigned with HMAC SHA-256, full delivery log, replayable
LinkupAPIReal-time webhooks with retries, a delivery log, replay and 30 days of stored events; HMAC SHA-256 signing is opt-in
Connecting accounts
Swarmhit Smart APIA one-time hosted link under your organization's name and picture; 2FA answered from the stored authenticator secret, CAPTCHAs solved in a live view of the real sign-in browser
LinkupAPIHosted login, or credentials and session tokens sent through the API
Developer tooling
Swarmhit Smart APIREST API, OpenAPI specification, signed webhooks, dashboard playground
LinkupAPIREST API, MCP server on every plan, Make, n8n and Zapier; no SDKs

API documentation

Machine-readable spec
Swarmhit Smart APIOpenAPI 3.1 file at version 1.27.0: 193 operations, 158 named schemas, bearer auth declared
LinkupAPIIts published OpenAPI file still describes the V1 API: 33 routes, 2 schemas, no security scheme declared, no examples; V2 lives in the pages only
Resource model
Swarmhit Smart APIREST resources for campaigns, leads, lists, senders and inbox, with GET, POST, PATCH and DELETE
LinkupAPIOne POST endpoint per category, the operation chosen by an action field in the body
Retry safety
Swarmhit Smart APICampaign sends are paced and retried by the platform; sends your code triggers, such as inbox replies and direct actions, accept an Idempotency-Key so a retry replays the first response
LinkupAPINo idempotency mechanism documented for sends; the only idempotent call it documents is the V1 to V2 account login
Rate-limit errors
Swarmhit Smart APIA sender-limit 429 returns the limit, the count used and the window, plus the reset time for daily and weekly caps
LinkupAPI429 RATE_LIMITED, with the advice to slow down and retry after a short delay
Webhook signatures
Swarmhit Smart APIEvery delivery signed with HMAC SHA-256, plus a delivery log, replay and test deliveries
LinkupAPIHMAC SHA-256 signing is opt-in and off by default; custom mode retries with a delivery log and replay, and a hosted mode streams events over SSE with 30 days of history
Size of the docs
Swarmhit Smart APIGuides plus a reference page for each of its 193 operations
LinkupAPI74 V2 pages, indexed next to 72 pages for the V1 API it is replacing

Pricing

Pricing model
Swarmhit Smart APIPublic and tiered per connected sender: $16.90 a month for the first 50, down to $6.90 between 1,501 and 2,500, set with sales above that; cold email from $59 for 125,000 sends
LinkupAPIPer connected account: $55 a month flat for up to 15, then $3.70, $3.30 and $3.00 per account, each band at its own rate; Unlimited at $3,000 a month flat, cheaper from about 974 accounts; billed upfront monthly, extra accounts billed at the end of the cycle on the peak; free trial offered, no annual option on the pricing page

Comparison data last verified on 14 November 2026.

Beyond the price per account

Who answers when something breaks?

A table compares endpoints. What you also buy, from LinkupAPI or from us, is the team behind them.

A team from the GTM space

Everyone on our team comes from the GTM space and ran outbound campaigns on the big tools before building one. We know what a sales team needs on a Monday morning and what breaks at scale.

Engineers from lemlist, senior only

Members of our tech team are ex-lemlist, so we know what we are doing. Everyone who builds the API is a senior engineer, so the person who answers your question is the person who wrote the code.

A Slack channel with our engineers

Every customer gets a shared Slack channel with two of our engineers: support dedicated to your team, not a ticket queue.

The Smart API when you outgrow raw calls

Start on raw endpoints and move a flow to the Smart API later, on the same accounts, when you would rather not maintain the sequencer, the pacing and the inbox yourself.

3 reasons to choose Swarmhit over LinkupAPI

Ship the feature, skip the build

LinkupAPI gives you endpoints and a tutorial for assembling a campaign yourself on its webhooks. The queue, the delays, the follow-ups and the reply stops are your code. Swarmhit exposes a working sequencer, inbox, and data layer through one API.

Safety on every LinkedIn send

LinkupAPI's best practices page says it enforces no limits on its side, so your account hits the same ceilings as in the LinkedIn interface. On Swarmhit, per-sender limits are enforced server-side on every send, with managed warmup and 250+ monitored safeguards. That judgment layer is what we mean by a Smart API.

Read the contract, not the landing page

LinkupAPI's solution pages advertise zero storage while its terms and privacy policy store tokens and credentials encrypted at rest, keep API logs for up to 12 months and allow message data to be kept as long as those logs. Its terms, dated February 2025, still describe the credit plans it has retired. Read both sets of pages before your compliance review signs off.

What does Swarmhit do differently?

A sequencer your product can call

Create a campaign with its sender pool, sequence, branching, schedule and exclusion rules through the API, add leads and activate it. Rotation, retries, and delays are the platform's job, not your codebase's. The full surface is documented at developer.swarmhit.com.

More than 250 safeguards, monitored 24/7

Dedicated proxy per sender, managed warmup, live health checks, and smart sending caps are the visible part. Behind them, Swarmhit runs over 250 safeguards tuned to LinkedIn's behavior and monitored around the clock. In campaigns, pacing is never your problem; on direct actions, per-sender caps are still enforced server-side.

One inbox for the whole team

Every reply from every sender lands in one inbox with AI-detected interest, and the same chats are readable and answerable through the API, so there is no polling loop to write and no inbox screen to build.

When is LinkupAPI the better fit?

You need WhatsApp without a call

LinkupAPI covers WhatsApp alongside LinkedIn and email on the same per-account price. Swarmhit's WhatsApp is in early access, opened team by team after a call.

You want a fully branded connect page on your own domain

LinkupAPI's hosted link takes your brand name, your logo and a custom domain. Swarmhit's hosted connect page carries your organization's name and picture, on our domain.

A very large fleet on a fixed budget

Its Unlimited plan caps the bill at $3,000 a month for any number of connected accounts, which no per-account model matches at the high end.

You only need raw endpoints and an MCP server

LinkupAPI sells raw LinkedIn, WhatsApp and email endpoints today, with an MCP server on every plan. Swarmhit's Raw API, in early access, covers LinkedIn and email, with WhatsApp in early access too, priced per account by band, and opens team by team.

If the goal is a LinkedIn outreach feature that works and keeps your users’ accounts safe, Swarmhit gets you there without writing the campaign layer: less a LinkupAPI replacement than the layer you were otherwise going to build on top of it.

TL;DR verdict

LinkupAPI is an inexpensive, broad set of raw outreach endpoints: LinkedIn, WhatsApp and email on one per-account price, an MCP server on every plan, and a $3,000 cap for unlimited accounts. What it does not sell is the layer above the endpoints: no campaign engine, no enforced LinkedIn limits, no inbox screen your team can work from. Swarmhit is the Smart API for teams that want that layer already running: sequencer, throttling, 250+ safeguards monitored 24/7, inbox API and prospect data behind one API.

When raw actions stop being enough

Nobody picks LinkupAPI by accident; the price per account and the channel list are genuinely attractive. Teams go looking when they price what sits above the endpoints: a queue with delays, a campaign state machine, follow-ups that stop on a reply, an inbox the team can work from, and LinkedIn limits that nobody on the vendor side enforces. The other trigger is due diligence, when a compliance review reads the legal pages next to the landing pages.

The comparison is also apples to oranges, and it is worth being honest about. LinkupAPI is a raw endpoints API; Swarmhit is a Smart API with the outreach engine built in. Decide first which one you are shopping for: endpoints to build on, or outcomes your product can call.

What does LinkupAPI actually give you?

LinkupAPI, operated by LINKUPAPI SAS in Paris, sells one API between your software and B2B channels. Its engagement endpoints cover LinkedIn messages, invitations, Sales Navigator InMails, comments, likes, posts and searches, WhatsApp messaging, and email sending from Gmail, Outlook or any SMTP and IMAP mailbox. A prospect data API adds people, company, job and funding data, and a mail API finds and verifies professional email addresses. Version 2 is action-based, one endpoint per category with an action field, and its documentation index lists about 70 actions. Each connected account gets a dedicated IP, accounts connect through a hosted login or through credentials and session tokens, and an MCP server ships on every plan for Claude, ChatGPT, Cursor and other clients. There are no official SDKs; integrations run through the REST API, the MCP server, Make, n8n and Zapier.

What do its legal pages say?

The landing pages and the legal pages tell two stories. Solution pages advertise a “zero-storage architecture” and the homepage says “passwords never stored”. The terms store “connected-account tokens and credentials (encrypted at rest)” and message data, the privacy policy keeps API logs for up to 12 months and lets message data be kept as long as the matching logs, and a sub-processor page dated September 2026 places that data on servers in the European Union. The homepage shows 99.9% uptime while the terms provide access “on a best-effort basis”. The terms, dated 28 February 2025, still describe the credit plans it no longer lists on its pricing page.

None of that is unusual for a young vendor, and encrypted credential storage is normal for the category. It is the gap between the two sets of pages that a compliance review will catch. Swarmhit runs every action on a LinkedIn account your customer owns and has connected, on a dedicated proxy, under per-sender limits we enforce and 250+ safeguards we monitor around the clock.

How do the API docs compare?

Page by page, LinkupAPI’s version 2 documentation is better than its reputation. Most of its 74 pages carry a parameter reference and a response example, there is a full error-code table, the webhook signature guide ships code in Python and Node.js, and a migration guide walks V1 customers through the switch. Its webhooks also offer something we do not: a hosted mode that streams events over SSE, with 30 days of stored history, for teams that cannot expose an endpoint.

The gaps sit in the layer your tooling reads rather than the one your developers read. The OpenAPI file its docs publish still describes the V1 API: 33 routes, 2 schemas, no security scheme declared and no examples, so importing it into Postman or a code generator gives you the API it is deprecating. Version 2 replaces V1’s one POST URL per action with one POST endpoint per category and an action field in the body, and no V2 spec is published to generate a typed client from. No idempotency key is documented for sends, so nothing in the docs protects a retried message call from sending twice. Webhook signing is opt-in and off by default. And the documentation index still lists 72 V1 reference pages next to the 74 for V2.

Swarmhit publishes a current OpenAPI 3.1 file, version 1.27.0, with 193 operations and 158 named schemas. Campaign sends are paced and retried by the platform, and the sends your code triggers, such as inbox replies and direct actions, accept an Idempotency-Key, so a retry replays the first response instead of sending again. A sender-limit 429 tells your code the limit, how much of it is used, the window and, for daily and weekly caps, when it resets. Every webhook delivery is signed, logged and replayable. The full reference is at developer.swarmhit.com.

What are you signing up to build on raw endpoints?

Who builds the campaign layer?

You do, and LinkupAPI's own pages say so once you get past the homepage. The homepage promises multi-step LinkedIn outreach campaigns and sequences; the version 2 action index lists about 70 actions and not one campaign, sequence or scheduling endpoint, and its MCP page puts it plainly: “No campaign builder, no settings.” Its campaign tutorial is a client-side recipe built on webhooks, and its best practices tell you to process API calls through a queue with random delays between jobs. That is a competent specification of the product you were hoping to buy, with your team as the vendor.

Who decides how hard an account is pushed?

On LinkedIn, your code does. LinkupAPI enforces no limits of its own there; it publishes recommendations instead: 80 to 100 invitations a day on a paid account and about 200 a week, 30 to 50 messages, around 100 profile views, and a two to three week warm-up for new accounts. Email mailboxes carry a daily limit setting, 40 by default, that LinkupAPI uses to route sends across a mailbox pool, but its docs say a send over that limit still goes out and is only flagged. Nothing stops a bug or an eager customer from going past the LinkedIn numbers, and the terms say restrictions by providers are not LinkupAPI's liability. Swarmhit enforces per-sender limits server-side on every send, and its campaigns add human-like scheduling on top, so a buggy loop hits a 429 instead of the account's ceiling.

What does the price actually buy?

LinkupAPI is one of the cheapest raw APIs per account, and that is real. Since moving to per-account pricing it bills per connected account, $55 a month flat for up to 15 accounts, then $3.70, $3.30 and $3.00 per account, each band at its own rate, and an Unlimited plan at $3,000 a month flat, with usage unlimited. What the price buys is the endpoints: the sequencer, the inbox, the pacing judgment and the campaign state are still yours to build and run. Swarmhit's Smart API costs more per sender because it includes all of those; Swarmhit's Raw API (early access) is the like-for-like option, from $3.90 down to $2.50 per LinkedIn account, from 15 accounts.

Competitor pricing and product facts on this page were checked against LinkupAPI’s own pricing page, documentation, terms of use, privacy policy and sub-processor list on 5 October 2026; pricing, account connection, the hosted link and the best practices page were read again on 14 November 2026. Vendors change prices without notice, so treat anything older than a month as indicative.

What does each option cost?

LinkupAPI bills per connected account, in US dollars excluding VAT, upfront each month: $55 flat for up to 15 accounts, then $3.70, $3.30 and $3.00 per account, each band at its own rate, and $3,000 a month flat for unlimited accounts, cheaper from about 974 accounts. Accounts added during the month are billed at the end of the cycle on the peak number connected. One account is one LinkedIn profile, one Gmail or Outlook mailbox or one WhatsApp number. Email finder and verifier lookups are billed in credits at a price the pricing page does not publish.

Swarmhit’s pricing is public: $16.90 per connected LinkedIn sender a month for the first 50, decreasing band by band down to $6.90 between 1,501 and 2,500 senders, and cold email from $59 a month for 125,000 sends. Each band of senders is priced at its own rate, so adding senders lowers what the next ones cost rather than repricing the fleet you already have. Above 2,500 senders, pricing is set with our team.

The difference buys the work itself: Swarmhit absorbs LinkedIn’s changes behind 250+ monitored safeguards and ships the campaign logic, so you build on a working foundation instead of rediscovering it with your customers’ accounts at risk. See the integration models or book the call.

FAQ

Swarmhit vs LinkupAPI, answered.

Buy the outreach layer,
not another build.

Ship a LinkedIn outreach feature with the sequencer, throttling, safeguards, inbox, and data already running, driven through an API and webhooks.