Dripify API review
Best documented LinkedIn automation API
GET https://api.dripify.com/v1/open-api/leads?limit=100 X-Api-Key: $DRIPIFY_API_KEY # 60 req/min and 5,000 a day, per API key # 403 means the plan does not include the Open API # 404 never means empty: that comes back as 200 and []
Dripify automates LinkedIn, and the thing to understand about it before the price is that LinkedIn is the constraint, not the software. Every tool in this category has to stay inside what LinkedIn tolerates, so the plan you pick does not buy you more volume in any general sense: it buys you a higher daily action ceiling. Basic allows up to 20 connection requests and 30 messages a day. Pro and Advanced go to 75 and 100 or more.
That also explains the seat model. One Dripify seat connects one LinkedIn account, because a LinkedIn account is the unit of capacity. A team of five reps needs five seats, at $39 each a month billed annually on Basic, $59 on Pro and $79 on Advanced, or $59, $79 and $99 paying monthly.
What makes Dripify worth a page in an API directory is the documentation. The Dripify API is published as an OpenAPI specification you can download, with every response code explained, published rate limits and cursor pagination, and there is an MCP server alongside it using the same key. Both arrive at Pro. Basic has no API, no MCP, no webhooks and no Zapier.
The rest of the category is in the Sending APIs listing.
What a call can actually do
The Dripify API sits under /v1/open-api/ and covers leads, campaigns and tags. The overview describes it as read-only, which the endpoint list does not quite bear out.
| Endpoint | Method | What it does |
|---|---|---|
| /leads | GET | List leads, up to 100 a page, cursor paginated. |
| /leads/search | POST | Look a lead up by email or LinkedIn URL, value in the body. |
| /leads/{id}/activity | GET | The lead's activity log. |
| /leads/{id}/conversation | GET | The LinkedIn conversation so far. |
| /leads/{leadId}/messages | POST | Send a message into an existing conversation. |
| /leads/tags | POST and DELETE | Apply or remove tags across a batch of leads. |
| /campaigns | GET | List campaigns and their status. |
| /campaigns/{id}/statistics | GET | Campaign statistics. |
The lookup endpoint is a POST rather than a GET for a deliberate reason Dripify states: the email or profile URL travels in the body so it never reaches an access log or a browser history. That is a better default than most vendors ship, and worth copying. Custom lead field values can also be set and unset, and leads can be uploaded into a campaign.
The front page of the Dripify API reference calls it a "read-only public API for your Dripify campaigns and leads". The endpoint list underneath it includes sending a message into an existing LinkedIn conversation, uploading leads into a campaign, applying and removing tags in batches, and setting custom field values. Those are writes. Build against the endpoint list rather than the summary sentence, and treat the message endpoint with the care a write to somebody's LinkedIn inbox deserves.
Dripify API pricing, plan by plan
Dripify API pricing is a plan gate rather than a meter: the API costs nothing per call, and it is simply absent below Pro.
Basic
- 20 connection requests and 30 messages a day
- One campaign at a time
- No API, no MCP, no webhooks, no Zapier
Pro
- Full daily quotas, 75 requests and up
- Open API and MCP server
- Webhooks, HubSpot, dedicated inbox, CSV export
Advanced
- Everything in Pro plus evergreen campaigns
- Adaptive activity control and team management
- Advanced LinkedIn protection
Enterprise
- Premium onboarding and dedicated support
- A customer success manager
- Priced on seat count
Those are the annual figures. Paying monthly costs $59, $79 and $99. Every plan includes 100 email finder credits a month, valid for 30 days and not rolled over, and a credit is only spent when Dripify finds and verifies an address, so failed lookups are free. Extra credits come in packs: $29 for 1,000, $49 for 2,000, $69 for 5,000 and $99 for 10,000, which is where the cheapest rate lives at just under a cent each.
This is the number that decides the bill, and it is not a volume question. Dripify charges per connected LinkedIn account, so an agency running outreach from ten client profiles needs ten seats, which is $590 a month on Pro billed annually whatever the sending volume. Tools priced per sender rather than per user, HeyReach at $79 a sender being the obvious comparison, work out similarly at small numbers and differently at scale. Count the LinkedIn accounts first, because nothing else in the rate card moves as much.
Published, headered, and plan gated
Dripify API rate limits are 60 requests a minute and 5,000 a day, counted per API key rather than per account, which means a second key is a second budget. Authenticated responses carry the usual three headers and a 429 tells you how long to wait.
| Limit or code | Figure | What it means |
|---|---|---|
| Per minute | 60 | Per API key, so extra keys add allowance. |
| Per day | 5,000 | The ceiling a backfill has to fit inside. |
| Headers | X-RateLimit-* | Limit, Remaining and Reset on authenticated responses. |
| 429 | Retry-After | Seconds to wait, as a number. |
| 401 | No headers | A rejected key is answered before the limiter runs. |
| 403 | Plan gate | The account's plan does not include the Open API. |
The 404 that is not empty
The most useful line in the docs.
- An empty result is a 200 with an empty list, never a 404.
- A 404 means the request could not be served for this account at all.
- Most commonly that is the Open API being switched off for it.
- So treat 404 as a configuration error, not as "no matching records".
Designing to 5,000 a day
The daily cap binds before the minute one.
- 5,000 calls a day against 60 a minute means you cannot run flat out for two hours.
- List leads at the maximum 100 a page and follow nextCursor rather than offsetting.
- A 10,000 lead sync is 100 paged calls, so the daily cap is not the problem; polling is.
- Per-key counting means splitting a sync and a webhook consumer across two keys.
Dripify separates three failures that most APIs collapse into one. A 401 is a bad key. A 403 is a good key on an account whose plan does not include the Open API, which happens the moment somebody downgrades from Pro to Basic. And a 404 is the API being switched off for the account.
If an integration that worked yesterday starts failing, the status code tells you whether to look at your credentials, your subscription or your settings, which is a small piece of design that saves a real afternoon.
How to create a Dripify API key
One API key serves both the Dripify API and the MCP server, which keeps the setup short and means a rotation affects both at once.
Getting the Dripify API key
Pro or Advanced only.
- Open Settings, then Integrations, then API Key, and generate one.
- Send it as an X-Api-Key header on every request.
- The same key authenticates the MCP server at app.dripify.com/api/v1/mcp.
- Rate limits are per key, so issue one per integration rather than sharing.
The MCP server
Four tools, one of them a write.
- View campaigns, view campaign lead lists and search leads are read-only.
- Upload leads adds up to 1,000 LinkedIn profiles as a new lead list, and is a write.
- Every upload creates a new list; adding to an existing one is not supported yet.
- Standard profile URLs only. Sales Navigator and Recruiter URLs are rejected.
Where the Dripify API documentation lives
The Dripify API documentation is at api.dripify.com, rendered with Redoc from an OpenAPI specification you can download and generate a client from. That is the most useful thing on this page: a machine-readable contract rather than a help-center article, which is what most of this category offers.
| Surface | Where | What it answers |
|---|---|---|
| API reference | api.dripify.com | Every endpoint, with the OpenAPI spec to download. |
| API base | api.dripify.com/v1/open-api/ | Where the requests go. |
| MCP server | app.dripify.com/api/v1/mcp | The four tools, and the API key they use. |
| MCP setup | Help center, "connect Dripify to AI assistants" | Claude and Cursor configuration, tool permissions. |
| Open API guide | Help center, "Open API" | Turning it on and generating a key. |
| Pricing | dripify.com/pricing | The plan gate, daily quotas and credit packs. |
Note the domain: the product now lives at dripify.com, and older dripify.io URLs including the one the pricing page itself links return a styled 404 rather than redirecting. The help center says OAuth authentication for MCP is planned, with API keys continuing to work alongside it.
Dripify also ships an MCP server, and it is on the MCP page with the others in this directory.
Dripify's own integration walkthrough
Dripify publishes this on its own channel, so it is Dripify's account of Dripify, 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 · Dripify Dripify Integrations through Zapier 9:01 · Published March 2025Not the API, but the nearest thing Dripify publishes: a step by step Zapier build wiring campaigns into a CRM. If what you want is the data out of Dripify rather than a custom client, this is the route most teams take and it needs no code.
Published 8 March 2025 on Dripify, the channel Dripify'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 a Dripify page.
Strengths and limits
Dripify documents its API better than anything else in LinkedIn automation, and prices it like a seat rather than a meter.
What it does well
- A downloadable OpenAPI specification, so you can generate a client.
- Published rate limits with the three standard headers and a Retry-After.
- An MCP server on the same key, with four tools and sensible read and write split.
- 401, 403 and 404 mean three different things, each documented.
- Lead lookup is a POST so the email never reaches a log or a browser history.
- Cursor pagination at up to 100 records a page.
- Email finder credits are only spent on a successful verified find.
- 7-day trial on Advanced features with no card.
Where it falls short
- No API, MCP, webhooks or Zapier on the Basic plan.
- The reference still calls itself read-only while documenting several writes.
- One seat is one LinkedIn account, so team costs scale with profiles.
- 100 email credits a month expire in 30 days and do not roll over.
- MCP uploads always create a new lead list, never append to one.
- Sales Navigator and Recruiter URLs are not accepted.
- Daily action ceilings are set by plan, so Basic is capped at 20 requests a day.
- No free tier.
Where Dripify 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 |
|---|---|---|---|---|
| Dripify | Work email, LinkedIn profile | 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 Dripify 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.
Expandi
$79/user/mo annualThe closest like-for-like. One plan at $99 with nothing gated, 22 webhook events and a per-campaign URL that adds leads with a POST.
HeyReach
$79/sender/moPriced per LinkedIn sender at $79, with the API, webhooks and an MCP server on that entry plan. Past about 13 senders the agency tier changes the arithmetic.
Reply.io
$49/user/moIf you want LinkedIn and email in one sequence rather than two tools. LinkedIn is a $69 an account add-on on top of the plan.
Instantly
$47/moNot a LinkedIn tool. Named because teams buying Dripify for the email half will get far more sending for the money elsewhere.
The full set, organized by the reason people leave, is on the Dripify alternatives page.
Dripify 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 Dripify 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 Dripify'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 Dripify at Pro if you want LinkedIn automation you can actually build against. The $20 a month a seat between Basic and Pro buys the full daily quota, the API, webhooks and an MCP server, and the quality of the documentation is the real differentiator: a downloadable OpenAPI spec, honest status codes and published rate limits put it ahead of every competitor in this category on integration work, Expandi included, whose full reference sits behind a login.
Do not buy Basic. At $39 a seat it has a 20 connection request daily ceiling and no integration surface at all, which makes it a manual tool at an automation price. If budget is the constraint, one Pro seat beats two Basic ones for almost every use, because the binding limit is LinkedIn's tolerance and Pro is the tier that lets you reach it.
The number to check before anything else is how many LinkedIn accounts you intend to run. Dripify charges per account, so an agency with ten client profiles pays ten seats regardless of volume, and at that size a per-sender tool is worth pricing against it. Then design to 5,000 calls a day rather than 60 a minute, page at 100 with the cursor, and use webhooks instead of polling, because the daily cap is generous and a polling loop is the only realistic way to exhaust it.
LinkedIn automation works until everybody is doing it.
The sequence is the easy part. Frontal builds the signal that decides who is worth a connection request and what the first message says, inside your own stack.
Worked with 300+ companies. A senior operator runs your account.
What Dripify 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. Where a comment makes its point in crude words, we summarize it in our own words instead of quoting it.
The tool is not what gets the account restricted
Solid breakdown. The only thing I'd add is that tool choice matters less than behavior - most restrictions happen because people crank volume too fast or send obviously templated messages. Honestly, hyper-personalization + low daily limits beats any "smart automation" feature long term. LinkedIn punishes spam patterns way more aggressively now.
r/socialmedia · February 2026 · 2 points
The same correction this directory records for cold email, pointed at LinkedIn. The sending tool does not decide deliverability and the automation tool does not decide whether an account survives; the volume curve and the message do. That is worth knowing before a comparison page persuades you the feature list is the risk.
It also explains why Dripify's daily action ceilings are set by plan rather than left open: 20 requests a day on Basic and 75 and up on Pro. A ceiling you cannot raise is a product deciding the thing most likely to get you restricted, which is a feature rather than a limitation.
Restrictions cluster around account hygiene, not campaign volume alone
In our words: Someone who has run hundreds of LinkedIn accounts through Dripify and its rivals says the restricted ones are the accounts with safety features off and every action maxed, several accounts per person, a new account making a purchase, or an assistant logging in from another country.
r/LinkedInTips · April 2026 · summarized rather than quoted
Every item on that list is about the account rather than the software: safety features switched off, action ceilings maxed, several accounts from one person, a brand new account making a purchase, and a login from a different country than the profile. None of those is the automation tool.
Treat the specifics as a signal rather than as policy. LinkedIn publishes no automation rules this directory can cite, so nothing here is a figure the site stands behind, and the operational point stands on its own: the account is the asset you cannot replace, and the cheapest protection is leaving the safety defaults alone.
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.
Dripify API, answered
Is the Dripify API free?
No. No free tier. 7-day trial on Advanced features, no card.
How much does the Dripify API cost?
Dripify starts at $39/user/mo annual. Billing is subscription, per seat and credit packs. Read from Dripify's own pricing page on 8 October 2026.
What are the Dripify API rate limits?
60 req/min and 5,000 a day, per API key. 429 carries Retry-After.
How do I get a Dripify API key?
API key in an X-Api-Key header, from Settings then API and Integrations. The current steps are in Dripify's own documentation, which is authoritative on anything that has changed since 8 October 2026.
Does Dripify have an MCP server?
Yes, at https://app.dripify.com/api/v1/mcp. It is listed with the others on the MCP page.