Expandi API review
Best for webhook-driven LinkedIn campaigns
POST https://<your-campaign-webhook-url> Content-Type: application/json { "profile_link": "https://www.linkedin.com/in/some-slug" } # the URL is the credential. There is no auth header
Expandi is cloud-based LinkedIn automation with the simplest rate card in this directory: one plan, $99 a month per seat, or $79 billed annually, with every feature in it. There are no tiers to compare and nothing is held back for an upgrade, which is unusual enough to be the main reason to consider it. Above ten teams, or for white label, there is an Agency arrangement priced by conversation.
The safety machinery is what Expandi sells on. Each account gets a dedicated country-based IP, profiles are warmed up automatically, and the daily action ranges are enforced rather than advisory: Expandi will not let you exceed the limits you set. It also sells specific campaign types that work around LinkedIn's ceilings, the Mobile Connector campaign adding another 100 connection requests a week.
The integration story needs stating carefully, because Expandi is not really an API product. There is a REST reference, it covers accounts, campaign analytics and lead actions, and it sits behind a Django login at api.liaufa.com, so it cannot be read without an account. What is publicly documented, and what nearly every Expandi integration actually uses, is webhooks in both directions.
The rest of the category is in the Sending APIs listing.
What the webhooks carry
Outbound webhooks are configured per LinkedIn account and fire on a chosen event. Expandi documents 22 of them, which is a wider event vocabulary than most senders publish.
| Event group | Events | What you would use it for |
|---|---|---|
| Replies | Contact replied, replied to campaign message, replied first time since start | Routing a hot reply to a rep or a Slack channel. |
| Connections | Request sent, accepted, accepted in active campaign, contact revoked, contact disconnected | Measuring acceptance rate and pruning dead paths. |
| Email steps | Email sent, opened, clicked, bounced | Scoring engagement across the email half of a sequence. |
| Engagement actions | Visit sent, follow sent, company follow sent, post liked, endorsement sent | Confirming the warm-up actions actually ran. |
| Campaign state | Campaign finished, contact tagged | Writing the outcome back to a CRM. |
| Capacity | No connection requests scheduled, no messages scheduled, nothing scheduled | Alerting when an account runs dry mid-week. |
The last group is the one worth noticing. Three separate events tell you that an account has nothing left queued, which is the failure mode that quietly wastes a week of outreach: nobody checks a campaign that has silently run out of people. Most tools in this category make you poll for that.
Expandi calls it a reversed webhook, and it is a per-campaign URL copied from that campaign's Integrations tab. POST JSON to it with a profile_link and the lead joins the campaign; optional company_name and custom_placeholder fields arrive as personalization variables. The same mechanism pauses and resumes a lead. There is no API key and no signature: the URL itself is the whole credential, so treat it like a password, keep it out of client-side code, and rotate the campaign if it leaks.
Expandi API pricing, plan by plan
Expandi API pricing does not exist as a concept, because there are no tiers and nothing is metered: one price buys the whole product including every integration surface.
Business, annual
- Every feature, with nothing gated
- Dedicated country-based IP and auto warm-up
- 20% off, billed as a year upfront
Business, monthly
- The same plan, month to month
- Unlimited campaigns and templates
- 22 webhook events and the reversed webhook
Agency
- For 10 or more teams, or white label
- Priced by conversation
- Larger seat discounts
There is a 7-day free trial and no free tier. Two personalization features cost extra on top: image and GIF personalization is an additional charge Expandi does not publish, and video personalization runs through a paid Senspark integration. Everything else, including the webhooks and the API, is in the $99.
Every other tool in this category gates something. Dripify holds back the API, webhooks and Zapier until Pro. QuickMail puts webhooks on a $299 plan. Smartlead keeps the API off its entry tier.
Expandi has one plan, so the comparison question is never which tier you need, only how many seats. That makes it easy to price and it makes seat count the only lever you have: there is no cheaper version to start on and no premium version to grow into.
Not published, and LinkedIn is the real ceiling
Expandi API rate limits are not published, and for most of what you would build that is the wrong thing to worry about. The binding constraint on Expandi is not requests a minute, it is how many actions LinkedIn will tolerate from one account in a day.
| Constraint | What Expandi says | What it means for a build |
|---|---|---|
| API rate limit | Not published | Assume modest, back off on any error, and do not poll. |
| Daily action ranges | You set them; Expandi enforces the cap | Throughput is a setting on the account, not a request budget. |
| Warm-up | Automatic, ramping from a low volume | A new account cannot run at full volume on day one. |
| Limit bypass | Specific campaign types, such as Mobile Connector | Another 100 connection requests a week, by a different route. |
| Reference access | Behind a Django login | You cannot evaluate the API surface before buying. |
Why the ceiling is the account, not the API
True of every tool here.
- LinkedIn restricts actions per profile per day regardless of which tool sends them.
- Expandi refuses to exceed the ranges you configure, which is a feature not a bug.
- So scaling means more connected LinkedIn accounts, which means more seats.
- An integration that queues 5,000 profiles still delivers at the account's daily rate.
What to build instead of polling
The webhook pair is the design.
- Push leads in with the reversed webhook when your signal fires.
- Receive replies and acceptances on outbound webhooks rather than asking.
- Subscribe to the three "nothing scheduled" events to catch a dry campaign.
- Keep the campaign URL server-side, since it carries no separate credential.
Expandi's own help center points at api.liaufa.com for the endpoint list, and that page asks for a Django login. That is a defensible choice and it has a consequence worth naming: you cannot assess whether the API does what you need before you are a customer. Every competitor in this batch publishes its reference openly, and Dripify publishes a downloadable OpenAPI spec. If the integration is the reason you are buying, that asymmetry matters more than the $20 a month between them.
How to create an Expandi API key
Expandi issues an API key and an API secret from Account Settings, and the webhooks use no credential at all.
The API credentials
Two values, regenerable.
- Open Account Settings and find the API section to view or copy the key.
- A Generate button issues a new key, which invalidates the old one.
- Expandi states plainly that the API is for users who already know how to use one.
- The endpoint list is at api.liaufa.com and needs a login to read.
The webhook credentials
There are none.
- An outbound webhook is a URL you supply, so you can verify the source yourself.
- A reversed webhook is a URL Expandi supplies, per campaign, with no key or signature.
- Anyone holding that URL can add leads to that campaign.
- Rotate by recreating the campaign, since the URL is tied to it.
Where the Expandi API documentation lives
Expandi documents the webhook surface thoroughly on its own blog and help center, and the REST reference separately and privately. The useful pages are worth bookmarking because the obvious URLs do not resolve: both the blog path for the API and the help article the directory listings point at return a 404.
| Surface | Where | What it answers |
|---|---|---|
| Webhook guide | Expandi's docs, from the app's help center | All 22 events and the reversed webhook walkthrough. |
| API credentials | Help center, "Account Settings" | Where the key and secret live, and how to regenerate. |
| REST reference | api.liaufa.com/open-swagger/ | The endpoint list, behind a login. |
| Webhook setup | In app, LinkedIn Settings then Webhooks | Adding a webhook and choosing its event. |
| Reversed webhook URL | In app, the campaign's Integrations tab | The per-campaign URL to POST leads to. |
| Pricing | expandi.io/pricing/ | The single plan and the annual discount. |
Expandi also ships native integrations to Zapier, Make, Google Sheets, HubSpot and Smartlead, and the Smartlead one is worth knowing about: it is the documented route to running LinkedIn in Expandi and email in a dedicated sender rather than using Expandi's own email steps.
Expandi also ships an MCP server, and it is on the MCP page with the others in this directory.
Expandi's own product demo
Expandi publishes this on its own channel, so it is Expandi's account of Expandi, not ours. It is here because a rate card cannot show you the thing moving, and a few minutes of the product is faster than any paragraph on this page at telling you whether the shape of it fits yours.
YouTube · Expandi How to overcome LinkedIn connection request weekly limit | Expandi Tips 4:53 · Published August 2021Not a walkthrough, and that is why it is here: five ways to work around LinkedIn's weekly invitation limit. The binding constraint on this platform is LinkedIn's limits rather than Expandi's own, which is the thing to understand before you build against it. From 2021, so the numbers in it are not current.
Published 2 August 2021 on Expandi, the channel Expandi's own pages link to, and read on 13 October 2026. Nothing in it is a source for a price or a limit on this page: every figure in the tables above comes from an Expandi page.
Strengths and limits
Expandi is the easiest tool here to price and the hardest to evaluate before you buy.
What it does well
- One plan at $99 a month, or $79 annually, with nothing gated behind a tier.
- 22 documented webhook events, a wider vocabulary than most senders publish.
- Three separate events fire when an account has nothing left queued.
- A reversed webhook per campaign adds, pauses or resumes a lead with one POST.
- Dedicated country-based IP per account and automatic profile warm-up.
- Daily action ranges are enforced, so the tool refuses to overrun them.
- Named campaign types that add capacity inside LinkedIn's rules.
- Native Smartlead integration for running email in a dedicated sender.
Where it falls short
- The REST reference is behind a login, so you cannot assess it before buying.
- No published API rate limit of any kind.
- The reversed webhook URL is the only credential: no key, no signature.
- The MCP server drafts campaigns but cannot activate one or edit a running one, so every launch stays a manual step.
- Image, GIF and video personalization cost extra on top of the plan.
- No free tier, and a 7-day trial is short for a warm-up based product.
- Both the blog and help URLs that vendor listings cite return 404.
- Agency pricing is quote only above ten teams.
Where Expandi data comes from, and what you may do with it
The question that arrives late and expensively is not how good the data is, it is who is allowed to hold it. These are the fields each one returns, the coverage it claims and the compliance it publishes.
| Provider | Fields returned | Coverage | Compliance | Redistribution |
|---|---|---|---|---|
| Expandi | LinkedIn profile, Work email | Global | GDPR DPA | Not stated |
None of these states a redistribution position on its pricing or docs pages. Internally that never matters. Put the rows in something your customers can see and it becomes the question your legal team asks first.
Two practical notes that apply to every provider on this page. A compliance badge describes the vendor, not your use of it, so a GDPR DPA does not give you a lawful basis for the outreach you send. And every one of these vendors runs its own opt-out, which means a person who asks you to delete their record has to be removed from your copy as well as from theirs.
If Expandi is not the answer
Four providers in the Sending APIs listing that solve the same problem differently. Each one is a trade, and the trade is named.
Dripify
$39/user/mo annualThe direct swap, $20 a seat cheaper at Pro. A downloadable OpenAPI spec, published rate limits, honest statements about what the Basic plan excludes.
HeyReach
$79/sender/moPriced per LinkedIn sender at $79 with the API, webhooks and an MCP server on that plan, and a $999 tier that changes the arithmetic past about 13 senders.
Reply.io
$49/user/moIf you want the email half to be serious rather than a step inside a LinkedIn tool. Multichannel sequences with the API on every plan.
Smartlead
$39/moNot a LinkedIn tool. Named because Expandi documents a native Smartlead integration, so the sensible split is often both rather than either.
The full set, organized by the reason people leave, is on the Expandi alternatives page.
Expandi against the obvious rival
Same rate cards, read side by side, with the arithmetic done on a worked volume rather than left to you: Dripify vs Expandi and Expandi vs HeyReach. Every pairing in the directory is on the compare hub.
Before you build against it
Four things to settle first, each one read off Expandi's own pages. The ticks are remembered in this browser, so you can come back to a half-finished integration.
Who should actually buy this
Buy Expandi if you want LinkedIn automation wired into something else through webhooks, and you value not having to think about tiers. The event list is the best part: 22 triggers including three that tell you an account has run dry, which is the failure nobody notices until a week is gone. Paired with the reversed webhook, you can drive campaigns entirely from your own signal source without touching the REST API at all, and that is how most teams should use it.
Look elsewhere if the API itself is the purchase. Dripify is $20 a month a seat cheaper at Pro, publishes a downloadable OpenAPI specification and states its rate limits, and you can read all of it before paying anything. Expandi asks you to buy an account before you can see the endpoint list, which is a reasonable thing for a vendor to do and an unreasonable thing for a buyer to accept when the alternative is open.
Whichever way you go, handle the reversed webhook URL as a secret. It accepts leads into a live campaign with no key and no signature, so it belongs on a server, never in a browser or a shared automation anybody can open, and the only way to revoke it is to recreate the campaign. That is the one genuine security decision this product asks you to make, and it is easy to get wrong by pasting the URL into a no-code tool with loose sharing.
Webhooks are only as good as the signal behind them.
Expandi will run the connection requests. Frontal builds the signal that decides who is worth one and what the first message says, inside your own stack.
Worked with 300+ companies. A senior operator runs your account.
What Expandi users say, in their own words
The one part of this page that is not a vendor claim. Quotes are transcribed as written and linked to the thread.
The pressure is on the category, not on one vendor
linkedin has been tightening the screws on all automation tools lately..... expandi, dripify, and pretty much every other player is feeling it... the thing is, linkedin doesn't want automation on their platform and eventually everyone running it at scale gets flagged...many tools have also received written warnings.. what's worked well for us is a co-piloted approach: instead of automating actions, we queue them up in a task manager [...]. this keeps things organized and under linkedin's daily limits.... no restrictions so far.
r/LeadGeneration · April 2025 · 2 points
Worth reading before any comparison on this page persuades you that one vendor is safer than another. The platform risk sits with the category, and a thread titled for two named tools concludes that every player in it is in the same position.
The practical takeaway is the one Expandi's own product already encodes: enforced daily action ranges per account and a dedicated country-based IP. A queue that stays under the platform's limits is the mechanism, and whether a vendor enforces that for you or leaves it to a slider is a real difference between the tools on this page. Nothing here is a claim about LinkedIn's policy, which LinkedIn does not publish in a form this directory could cite.
14 threads read on 13 October 2026, searched by vendor name. Scores and dates are the comment's own. Nothing here is the only source for a price or a limit on this site: every figure in the tables above comes from a vendor's own page.
Expandi API, answered
Is the Expandi API free?
No. No free tier. 7-day trial.
How much does the Expandi API cost?
Expandi starts at $79/user/mo annual. Billing is subscription and per seat. Read from Expandi's own pricing page on 8 October 2026.
What are the Expandi API rate limits?
Not published. LinkedIn action ceilings are the binding constraint.
How do I get an Expandi API key?
API key and secret from Account Settings. The current steps are in Expandi's own documentation, which is authoritative on anything that has changed since 8 October 2026.
Does Expandi have an MCP server?
Yes, at https://api.liaufa.com/mcp. It is listed with the others on the MCP page.