LinkedIn, email and WhatsApp in one API. The whole logic, handled.
The Smart API is Swarmhit’s outreach engine behind a REST API. One call creates a campaign that mixes LinkedIn, email and WhatsApp steps. Everything after that is handled: send windows, per-sender limits, warm-up, retries, sender rotation, replies matched on every channel, and the sign-in of every account, 2FA and CAPTCHA included. You decide who and what. We handle when, how fast and what happens next.
Free trial in the playground, up to 2 senders · Cancel anytime
1 call
Sets up a campaign
Senders, sequence and schedule in one POST /campaigns.
3 channels
In one sequence
LinkedIn and email steps, WhatsApp in early access.
250+
Safeguards, monitored 24/7
Caps, warm-up and health per sender, enforced on our side.
0
Passwords in your product
Users connect on a hosted page under your brand.
What the engine owns
The part of outreach nobody wants to rebuild.
Sending one message through an API is easy. Running thousands of leads across dozens of accounts without getting one of them restricted is the hard part. On the Smart API, that part is ours.
Send windows
Each campaign has a timezone, active hours and active days. Nothing goes out at 3 a.m. in the lead's week.
Caps per sender
Daily and weekly limits live on each sender, not on the campaign. A large enrollment starts at the pace each sender can hold.
Warm-up
New LinkedIn accounts can start slowly and ramp up on their own. Mailboxes bought through Swarmhit arrive already warming.
Sender pools
Leads spread evenly across the campaign's healthy senders. Once a lead is contacted, it stays with that sender for the whole sequence.
One sender, one person
Two campaigns sharing a sender never work the same person at once: the second waits instead of opening a parallel thread.
Reply detection
A reply on any channel ends that lead's sequence and reaches your webhook, with an optional AI label: interested, not interested, neutral, out of office.
Company rules
Cap how many new people per company you contact in a day or a week, and pause a company's other leads when one of them replies.
Out of office
An automatic away reply holds the lead's next step until the day they are back, instead of following up into their vacation.
Provider matching
Optional: Gmail leads get mail from your Google mailboxes and Outlook leads from your Microsoft ones.
How it works
A campaign in one call.
The sender pool, the mailbox pool, the schedule and the sequence go in one request. Steps are wired to their parent, conditions split into a “yes” and a “no” branch, and delays sit on the steps. The campaign is created paused; add leads, set it active, and the engine runs it.
- 01
POST /accounts/hosted-link
Each user connects their LinkedIn on a page under your brand.
- 02
POST /campaigns
Senders, sequence and schedule. Created paused.
- 03
POST /campaigns/{id}/leads
Up to 1,000 leads per call, by LinkedIn URL or email.
- 04
POST /webhooks
Replies, accepts, sends and bounces, signed.
Visit, invite, message, or email if not accepted
api/v1POST https://app.swarmhit.com/api/v1/campaigns
Authorization: Bearer swh_live_…
{
"name": "Q4 founders",
"linkedinAccountIds": ["aCc123", "aCc456"],
"emailAccountIds": ["mBx789"],
"schedule": {
"timezone": "Europe/Paris",
"activeHours": { "from": "09:00", "to": "18:00" },
"activeDays": [1, 2, 3, 4, 5]
},
"sequence": { "steps": [
{ "id": "v", "type": "visit_profile", "parent": null,
"nextDelayHours": 24 },
{ "id": "i", "type": "invite", "parent": "v",
"branchDelays": { "no": 336 } },
{ "id": "m", "type": "message", "parent": "i", "branch": "yes",
"config": { "text": "Thanks for connecting, {{firstName}}…" } },
{ "id": "e", "type": "if_has_email", "parent": "i", "branch": "no" },
{ "id": "x", "type": "email", "parent": "e", "branch": "yes",
"config": { "subject": "Quick one", "text": "Hi {{firstName}}…" } }
] }
}The step library
Every step a sequence can take, across three channels.
Mix them in one sequence, with A/B variants, {{variables}} with fallbacks, and a voice per sender.
- visit_profileview the profile
- follow_profilefollow the lead
- like_postlike the latest post
- comment_postAI comment from your prompt
- inviteconnection request, optional note
- messagea reply ends the sequence
- inmailyou choose what happens without credits
- voice_noterecorded, per sender
- ai_voice_notea script in an AI or cloned voice
Email and WhatsApp
- emailfrom the campaign's mailboxes
- whatsapp_messagetext or a file, early access
Conditions
- if_connectedalready connected?
- if_open_profileopen profile?
- if_has_emailusable email address?
- if_has_linkedinroute email-only leads
- if_email_openedopened the last email?
- if_email_clickedclicked a link?
- if_has_phonephone for WhatsApp?
Data and people
- find_emaillook up a work email
- find_phonelook up a mobile number
- calla call task for your team
Each LinkedIn action is also callable on its own, outside campaigns: see every LinkedIn API endpoint.
Sign-in that holds
2FA, checkpoints and CAPTCHAs, handled in the flow.
Most LinkedIn integrations break at sign-in, not at sending. LinkedIn asks for a code, an app approval, a phone number or a puzzle, and an API that only returns “checkpoint required” leaves your user stuck. The Smart API carries the whole sign-in.
- A hosted connect page under your brand.A one-time link, your organization’s name and picture, a return URL. The password never touches your product.
- CAPTCHAs in a live view.When LinkedIn shows a puzzle only its own page can show, the hosted page streams the real sign-in browser, and the person solves it right there. No screenshots, no “try again later”.
- Hands-free login with 2FA. Connect an account with its authenticator secret and every later sign-in completes on its own. A broken session retries by itself before anyone is asked.
- No false alarms.LinkedIn refreshes sessions now and then. A sender that briefly answers “disconnected” mid-campaign is retried quietly, and your webhook only hears about it if it stays down.
Every checkpoint LinkedIn raises
- 2FA
- Answered on its own when the account was connected with its authenticator secret.
- OTP
- The code LinkedIn emailed or texted, typed on the hosted page or sent through the API.
- IN_APP_VALIDATION
- The member approves in the LinkedIn app; the sender comes up on its own.
- PHONE_REGISTER
- A phone number to register, with its dialling code.
- CAPTCHA
- The real sign-in browser streams to the hosted page, so the person solves the puzzle there.
When LinkedIn offers another method, the flow can ask for it. A reconnect keeps the sender’s id, campaigns and seat. Each sender signs in from a dedicated proxy in its own country.
Built to sit inside a product
Your customers, your brand, our engine.
Workspaces per customer
One organization key acts on every client workspace with a single header, each with its own senders, seats and data.
Embedded components
Show the Swarmhit inbox, tasks and campaigns inside your product, each user seeing only the accounts you give them.
Inbox API
Every LinkedIn and email conversation, its history, and replies with attachments or voice notes.
Webhooks, SDK and MCP
Signed events with a replayable log, an official JavaScript SDK, and an MCP server for AI agents.
See what teams build: sales teams, agencies, recruiting tools and AI agents.
LinkedIn and WhatsApp
$16.90 down to $6.90
Per connected account a month, from 2 accounts. A WhatsApp number costs the same as a LinkedIn sender.
Cold email
$59 for 125,000 sends
Then per 1,000 emails sent, unlimited mailboxes, warmup pool free.
Each channel is priced on its own, on one invoice. Every band is public.
See the full pricingSmart 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 outreach API should do for you
An outreach API lets your product run prospecting on LinkedIn, email and WhatsApp without a person clicking through it: connect the accounts, send the invitations, messages and emails, read the replies. Most APIs on the market stop at the actions, one endpoint per send, and leave the rest to your engineers: the queue, the send windows, each account’s limits, retries, and knowing when a lead answered on another channel. That layer is where accounts get restricted and where teams lose months. Our comparison of outreach APIs lays out the three kinds on the market and what each one leaves to you.
An outreach automation API for LinkedIn, email and WhatsApp
The Smart API is the same engine on three channels. LinkedIn steps cover profile visits, invitations, messages, InMail, voice notes and post engagement. Email steps send from your own Google, Microsoft or IMAP mailboxes, or from mailboxes bought through Swarmhit, in the same thread as earlier emails. WhatsApp steps, in early access, carry the short follow-up around a deal. Read the details per channel: LinkedIn, cold email and WhatsApp.
A sender is a person, not an account
A sender groups one LinkedIn account, several mailboxes and several WhatsApp numbers under one name. A lead assigned to a sender hears from that person on every channel, so the email after an unanswered invitation comes from the same name the lead just saw on LinkedIn.
Why limits belong on the server
When an AI agent or your own code decides what to send, the safest place for limits is outside that code. On the Smart API, daily and weekly caps, the pending-invitation ceiling and warm-up live on each sender and are enforced by Swarmhit. An action over its limit answers 429 with the limit, the count used and when it resets, so your product can queue it instead of guessing. The LinkedIn connection limits guide explains the limits LinkedIn itself applies.
Comparing LinkedIn APIs?
If you are weighing the Smart API against a raw LinkedIn API, read Swarmhit vs Unipile, Swarmhit vs LinkupAPI and Swarmhit vs Linked API, or our guide to LinkedIn API pricing. For direct access to the same accounts, see the Raw API.
FAQ
The Smart API, answered.
- One call per campaign
- 250+ safeguards
- REST API, webhooks, SDK
Ship outreach this week.
Let the engine run it.
Open the playground with up to 2 senders, call the API, and watch a campaign run before you write your own integration.