An unofficial LinkedIn API, with WhatsApp and email on the same calls.
The Raw API gives your code one endpoint per action on the LinkedIn accounts, WhatsApp numbers and mailboxes your users connect: send, invite, react, search, read, and receive every event as a signed webhook. Swarmhit keeps each account signed in, on its own browser identity and IP, through 2FA, checkpoints and CAPTCHAs. Your code decides what to send and when. From $3.90 per account.
Opened team by team after a call · Sandbox keys to build first
3 channels
One API shape
LinkedIn, WhatsApp and email share paths, bodies, errors and events.
$3.90
Per account, down to $2.50
A month, from 15 accounts. WhatsApp numbers count the same.
Live view
For CAPTCHAs
The real sign-in browser, streamed over a websocket.
gw_test_
Sandbox keys
Build against simulated accounts before you touch a real one.
You decide, Swarmhit executes
Your logic. Our accounts layer.
The Raw API is for teams that already have a sequencer, or want to write their own. You keep full control of the logic. We run the part that is painful to run yourself: real accounts that stay signed in.
Your code
Swarmhit
What to send and to whom
Keeping every account signed in
When it goes out: pacing, schedules
A browser identity and sticky IP per account, in its country
Daily limits and warm-up
2FA, checkpoints, CAPTCHAs, reconnects
Matching replies to your leads
Every event pushed as a signed webhook
Your sequencer, your logic
Refusing what a runaway client would do, before it reaches LinkedIn
Account connection
Sign-in is where LinkedIn APIs break. Ours carries it through.
A credentials connect signs in the way the member would, so LinkedIn may answer with a code, an app approval, a phone number or a puzzle. Each one comes back typed, with a way to finish it, instead of a dead end.
Connect a LinkedIn account
Raw APIcurl -X POST https://console.swarmhit.com/api/v1/accounts \
-H "X-API-KEY: gw_live_…" -H "Content-Type: application/json" \
-d '{"provider":"LINKEDIN","username":"jane@acme.com",
"password":"…","totp_secret":"…","country":"FR"}'
# 201 AccountCreated signed in, store account_id
# 202 Checkpoint LinkedIn wants something:
# OTP | 2FA | PHONE_REGISTER POST /api/v1/accounts/checkpoint
# IN_APP_VALIDATION wait for the OK event
# CAPTCHA | UNKNOWN open the live view
# 202 AccountQueued the result arrives as eventsSolve a CAPTCHA inside your product
live view// res = the 202 Checkpoint answer, checkpoint.type "CAPTCHA"
const ws = new WebSocket(
`wss://console.swarmhit.com/li-live/${res.live_view.token}`);
ws.onmessage = ({ data }) => {
const m = JSON.parse(data);
if (m.type === "frame") img.src = "data:image/jpeg;base64," + m.data;
if (m.type === "state" && m.state === "ended") done();
};
// forward the person's clicks and keys to the real browser
canvas.onclick = (e) => ws.send(JSON.stringify(
{ type: "mouse", action: "mousePressed", x: e.offsetX, y: e.offsetY }));CAPTCHA live view
The real sign-in browser as JPEG frames over a websocket, taking mouse, wheel and key input. Show it in your own UI; the account turns OK when the person is through.
2FA without a person
Send the account's authenticator secret with the connect and Swarmhit answers 2FA by itself, now and on every later sign-in.
Password or cookie
Connect with credentials, or with the member's session cookie when that is what you have. A cookie connect never stops at a checkpoint.
Same device, same IP
Each account keeps its browser identity and a sticky IP in the country you choose. Retries and reconnects reuse them; recover picks a new IP in the same country.
One endpoint per action
Three channels, one API shape.
Same base URL, same keys, same error envelope, same webhook. The id’s prefix tells you the channel: lg_, wa_ or em_.
Chats and messages
list, start, send, InMail and Sales Navigator threads
People
profiles, invitations sent and received, connections
Posts
a member's posts, react, comment, publish
Search
people, Sales Navigator, companies, InMail balance
Link a number
QR code or pairing code, like WhatsApp Web
Check a number
is it on WhatsApp, before the first message
Chats and files
text, files, voice messages, replies
Groups and reactions
groups, reactions, edits, forwards
Connect a mailbox
IMAP and SMTP, or Gmail and Microsoft 365 with your OAuth app
Send once, thread right
Idempotency-Key, reply_to threading
Tracking
opens, clicks, bounces, complaints as events
Read
folders, newest first, bodies on request
Write safety, not hand-holding
One write at a time per account, a short gap between writes, and daily caps per kind that sit far above any sane pacing. When LinkedIn itself pushes back, the account rests before it tries again. Every refusal happens before anything leaves, so a retry never sends twice.
Every event, signed
New messages, accepted invitations, account status, WhatsApp delivered and read, mails sent, opened, clicked and bounced, each with an HMAC-SHA256 signature over the raw body. unless_replied_since skips a follow-up the lead already answered.
A sandbox, like test cards
- Any email and password: Connected at once, with fake people, chats and posts
- Password checkpoint: An OTP checkpoint; 123456 answers it
- Password wrong: Refused as bad credentials
- An email starting with restricted: Refused as a restricted account
LinkedIn and WhatsApp
$3.90 down to $2.50
Per account a month, proxy managed by us. Minimum 15 accounts: $58.50 a month.
$39 for 125,000 emails
Then per 1,000. Unlimited at $999 a month, whatever the volume.
Everything unlimited
$4,999 a month
Unlimited LinkedIn, WhatsApp and email on your own proxy, set up with sales.
Smart API vs Raw API
Same infrastructure. Two levels of control.
Both APIs run on the same accounts, proxies and sign-in layer. The difference is who owns the campaign logic: our engine, or your code. One Swarmhit login opens both, each with its own plan.
| Smart API | Raw APIEarly access | |
|---|---|---|
| What you call | One call per campaign: POST /campaigns carries the senders, the sequence and the schedule | One call per action: send, invite, react, search, read |
| Who decides when | Swarmhit: send windows, per-sender caps, warm-up, retries | Your code: pacing, daily limits, warm-up and schedules are yours |
| Replies | Matched to the lead, the sequence stops, a webhook tells you | Raw events by webhook; your code matches them |
| Channels | LinkedIn and email, WhatsApp in early access, in one sequence | LinkedIn, WhatsApp and email on the same paths and events |
| Account sign-in | Hosted connect page under your brand, 2FA, CAPTCHA live view | Credentials or cookie, 2FA by secret, checkpoints and a CAPTCHA live view over websocket |
| Extras | Inbox, leads and lists, B2B database, AI reply labels, JS SDK, MCP server | Sandbox keys with test credentials, plain HTTP |
| LinkedIn and WhatsApp price | $16.90 down to $6.90 per account a month, from 2 accounts | $3.90 down to $2.50 per account a month, from 15 accounts |
| Email price | $59 for the first 125,000 sends, then per 1,000 | $39 for the first 125,000, then per 1,000; unlimited at $999 a month |
| Start | Free trial: the playground, up to 2 senders | Early access, opened after a call; $4,999 a month for everything unlimited on your own proxy |
Which one fits you?
- Smart APIYou want campaigns running this week, without writing a sequencer
- Smart APIYour users connect their accounts inside your product, under your brand
- Smart APIAn AI agent decides who and what, and someone else should enforce the limits
- Raw APIYou already run your own sequencer, queue and pacing
- Raw APIYou need actions the campaign engine does not model, like publishing posts or running WhatsApp groups
- Raw APIYou run thousands of accounts and want the lowest price per account
Not sure yet?
Most teams start on the Smart API and move a few flows to the Raw API later, or the reverse. The accounts stay the same infrastructure either way.
- Same accounts and proxies
- Same sign-in and checkpoint handling
- One login, two plans
What an unofficial LinkedIn API is, and what it is not
LinkedIn’s official APIs are for sign-in, sharing content, advertising and approved partners. None of them lets a product send an invitation or a message from a member’s account. An unofficial LinkedIn API fills that gap by acting through the member’s own session. Some of them are open-source wrappers around LinkedIn’s internal endpoints, which our Voyager API guide explains, and you run the accounts, the IPs and the sign-ins yourself. The Raw API is the hosted version: the same direct actions, with the accounts layer run for you.
It is not a data or scraping API. Every call is an action of the account it runs on, through accounts your users own and connect. Swarmhit is not affiliated with LinkedIn, and no LinkedIn automation is free of risk: pacing stays your responsibility on the Raw API, and the LinkedIn connection limits guide is a good place to start.
A unified messaging API for LinkedIn, WhatsApp and email
Products that talk to people on several channels end up with three integrations, three auth flows and three event formats. On the Raw API the three share one base URL, one key, one error envelope and one webhook: a message_received event looks the same whether it came from a LinkedIn conversation or a WhatsApp chat. WhatsApp numbers link like WhatsApp Web and count as accounts at the same price as LinkedIn, and the WhatsApp playbook shows where they belong in a deal.
What changes when you leave another raw API
If you already run LinkedIn on another raw API, read Swarmhit vs Unipile, Swarmhit vs LinkupAPI, Swarmhit vs Linked API and Swarmhit vs Edges, or our list of Unipile alternatives. Per-account prices across the market are in our LinkedIn API pricing guide.
When the Raw API is the wrong choice
If you do not have a sequencer and do not want to write one, the Raw API means building the queue, the send windows, the per-account limits, the retries and the reply matching before your first campaign goes out. The Smart API runs all of that for you on the same accounts, with one call per campaign.
FAQ
The Raw API, answered.
- LinkedIn, WhatsApp and email
- CAPTCHA live view
- Sandbox keys
The Raw API is in early access.
Build against the sandbox first.
Book a call, we open the Raw API for your team, and you build against sandbox keys before you connect a real account.