Swarmhit vs LinkupAPI

Comparison data last verified on 5 October 2026.

3 reasons to choose Swarmhit over LinkupAPI

What does Swarmhit do differently?

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.

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.7.0, with 133 operations and 107 schemas behind 13 guides. 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?

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. 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 for up to 10 accounts, then $5.50, $5.00 and $4.50 per account by band, with the band rate applied to every account, and $3,000 a month flat for unlimited accounts. 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 (in beta) from $59 a month for 50,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.