Basic auth with a leading colon, and a sequencer that sells enrichment of its own.
A Reverse Contact API key and a lemlist API key, sent as HTTP Basic
Contacts, Companies, one way, in.
lemlist is the easiest of the sequencers to connect and the most interesting to reason about, because it sells enrichment itself. The connection is a few lines once you get past the Basic auth with its leading colon, and the limits are comfortable at 20 requests per 2 seconds. The real question is not how to add a second provider but how to order two, which is a waterfall question and the only honest answer involves running both over 500 of your own rows and counting.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| The list, before the campaign | One way, out | Enrich each lead from its email with /v2/enrich/persons. 2 credits on a match. |
| Lead creation | One way, in | POST the lead to the campaign with the enriched values as custom variables. |
| Activity webhooks | One way, out | lemlist fires events on opens, replies and other activity, which is how a reply reaches a CRM. |
| Anything back to Reverse Contact | One way, out | Nothing. This is a read layer, and your pipeline decides which lemlist variables are written. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
The mapping here is simple and the interesting column is cost, because lemlist sells enrichment too. Every row below can in principle be filled by either provider, which makes the order they run in the only decision that changes the bill.
| In lemlist | In Reverse Contact | What to know about the match |
|---|---|---|
| An email on the lead | POST /v2/enrich/persons, 2 credits | Identity, the current role, history, education, skills and location on one schema. A confident null costs nothing, because every 4xx and 5xx is free, which is what makes it safe to put second in a waterfall. |
| A company domain | POST /v2/enrich/companies, 2 credits | Firmographics from a domain or a company name. Once per company rather than once per lead at it. |
| A profile URL already on the lead | POST /v2/fetch/persons, 1 credit | Half the credits, and unmetered from the $249 plan rather than the $699 one. A multichannel sender often already holds one, because the channel needs it. |
| The free freshness check | POST /v2/fetch/persons/check, 0 credits | Whether a profile is cached and when it was last updated. The cheapest possible tiebreak between two providers on a per-row basis. |
| currentPosition.title and company.name | lemlist custom variables | The two values most openers reference. A missing variable renders the fallback text rather than stopping the send, which is why the resolved rate has to be counted rather than inferred. |
| The lemlist API key | HTTP Basic, with a leading colon | Username always empty, password the key, and the encoded string starts with a colon. Not Bearer, and the error for getting it wrong reads like a bad credential. |
| Its own enrichment, including a bulk endpoint | The other provider in the waterfall | This is the fact that shapes the page. Two sources that overlap need an order rather than a toggle: cheapest high-coverage first, the second only on what came back null. |
| Anything outbound to Reverse Contact | Only what your pipeline sends | This is a read layer. No lead, campaign or reply is sent anywhere, and there is nothing in the product to send it to. |
The rest of this directory treats an enrichment response as values to write. On a multichannel sender it is also a list of reasons not to contact somebody at all, and a wrong row here is an email and a connection request rather than only an email.
| In the response | Why it is a reason not to send |
|---|---|
| isInRemembrance | The person has died. No amount of personalisation makes the email acceptable, and it is the one outbound failure that cannot be apologised for afterwards |
| currentPosition.companyName disagrees with your record | They have changed job, so a campaign written for the old role is about to reach the new one. Re-qualify rather than refresh |
| isOpenToWork | They are looking to leave. A reason for a human to read the opener once, rather than an automatic stop |
| data is null, with a confidence score | Nothing matched confidently. Sending the fallback text is a decision, and on a cold list it is usually the wrong one |
| metadata.updatedAt, from long ago | Stale rather than wrong, which is the one case where a 2-credit live refresh earns its money |
| followersCount and hasVerificationBadge | Not suppression at all. Listed because they are the fields teams reach for as a seniority proxy, and neither is one |
A few things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: eight field mappings, six in the response rows and four documented exclusions, each one's note, and the six vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The seventh row is the one that makes this pair different from the other four senders here. Everywhere else the question is how to add enrichment; here it is which of two overlapping providers runs first, and that is answered by counting rows rather than by reading documentation.
lemlist sells enrichment and so does Reverse Contact, so the real decision on this pair is sequencing rather than connection. The grid walks the four kinds of row a list contains and asks what each arrangement pays for them. Only the conditional orderings pay once per row. Pick one on each side and the grid marks the answer.
Pick one on each side.
| How you arrange the two | Resolved by both providers | Resolved only by lemlist | Resolved only by Reverse Contact | Resolved by neither |
|---|---|---|---|---|
| Both, unconditionally | Two lookups | Two lookups | Two lookups | Two lookups |
| lemlist first, Reverse Contact on the nulls | One lookup | One lookup | Two lookups | Two lookups |
| Reverse Contact first, lemlist on the nulls | One lookup | Two lookups | One lookup | Two lookups |
| Reverse Contact only | One lookup | One lookup and an empty row | One lookup | One lookup |
Counted off that grid, of sixteen pairings: seven give you one lookup, eight give you two lookups, one gives you one lookup and an empty row. The bottom two rows are the honest shortlist and the difference between them is a measurement rather than an argument: run both over 500 of your own rows and count how many each resolves alone. One detail tips it when the counts are close, which is that a Reverse Contact miss costs nothing at all, because every 4xx and 5xx is free, so putting it second is cheaper than putting a metered provider there.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
A spreadsheet, not a settings screen
lemlist sells enrichment itself, so this is not a question of adding a provider but of ordering two. Running both unconditionally means paying twice on every row they can both resolve. The only honest way to settle it is to run both over 500 of your own rows and count, and that measurement is the irreversible-feeling decision on this page.
Your own pipeline
A missing variable renders the fallback text rather than stopping the send, which is the behaviour you want and the reason an unenriched row is easy to miss. Nothing later repairs the email that has gone, so the ordering is the design.
lemlist: Settings, Integrations, Generate a new API key
lemlist uses HTTP Basic rather than Bearer. The username is always empty, the password is the key, and the string you encode is a colon followed by the key. Their documentation shouts about this because people get it wrong, and a Bearer header returns an auth error that looks exactly like a bad key.
lemlist: the key generation screen
lemlist states that you will not be able to see the key again. That is one sentence and it costs a regeneration and every integration using the old key if you skip it.
Any lemlist API response
The limit is 20 requests per 2 seconds on all routes, metered per API key. Retry-After is an integer count of seconds, and X-RateLimit-Reset is a human-readable date string, which lemlist calls out specifically. Code that assumes an integer either crashes or parses it to zero and retries immediately.
POST /v2/fetch/persons/check
The free check says whether a profile is cached and how fresh it is, which also happens to be the cheapest way to decide between two providers on a per-row basis rather than a per-list one.
Your pipeline
A current employer that disagrees with your record, an isInRemembrance flag, a confident null: each is a row to drop. On a sender that runs multichannel, a wrong row is an email and a connection request rather than just an email.
Your own data
Because a fallback renders rather than failing, a campaign with a third of its rows unenriched looks exactly like a campaign that is working. Count how many rows carry the field before you send, and the reply rate stops being the thing that tells you.
The first and last steps are both about measurement rather than configuration, which is unusual in this set and is the consequence of the other vendor selling the same thing you are adding. Smartlead sells no enrichment of its own, and the same build there is a straight line.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/lemlist-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/lemlist-reverse-contact.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
Whylemlist uses HTTP Basic rather than Bearer. The username is always empty, the password is the key, and the encoded string must start with a colon.
Encode a colon followed by the key. lemlist shouts about this in its own documentation because it is the most common mistake on the API, and the error message does not point at it.
WhyX-RateLimit-Reset is a human-readable date string rather than a Unix timestamp, so code that parses it as an integer gets zero and retries at once.
Use Retry-After, which is an integer count of seconds. lemlist calls the date format out specifically, which is a fair warning that it has caught people.
WhyThe limit is 20 requests per 2 seconds, applied to all routes and metered per API key rather than pooled across a team.
Serialise or pace at about ten a second. At that rate a thousand rows takes under two minutes, so there is rarely a reason to parallelise this at all.
Whylemlist states that you will not be able to see the key again after generating it.
Generate a new one, and expect every integration holding the old key to stop at the same moment. Worth knowing which those are before you click.
WhyA missing variable renders the fallback rather than stopping the send, which is the behaviour you want and makes an unenriched row invisible.
Count the resolved rate on the list before sending rather than waiting for the reply rate to tell you. A campaign with a third of its rows unenriched looks exactly like one that is working.
WhyTwo overlapping providers running unconditionally both charge for every row they can resolve, and most rows resolve on both.
Make the second one conditional on the first returning null. A Reverse Contact miss costs nothing, which makes it the cheaper of the two to put second.
WhyNothing compared the returned current employer against the company on the row, and a multichannel campaign acts on more than one channel per row.
Compare currentPosition.companyName with your own value and drop the row. The cost of a wrong row is higher here than on an email-only sender because it is wrong in two places.
WhyBelow 2 Reverse Contact credits the free Check endpoints are paused too and answer 402 NO_CREDITS, because the fetch a check precedes can itself cost 2.
Branch on quotas.workspace.credits.left, which rides on every response. GET /v2/usage keeps answering whatever the balance, so a balance check never fails for the same reason the lookup did.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2024 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
I've played with Lemlist db and the waterfall enrichment works ok but not life changing. Data is mostly same commodity stuff you get from Apollo or Clay etc, hit rate is fine in US, more spotty elsewhere. Pricing also ramps fast once you add seats so for a low volume client I wouldnt buy it just for the 600M claims.
r/EmailProspecting·March 2026·1 points
One person's experience rather than a benchmark, and it is the most directly useful comment in the harvest for this pair. Fine in the US and spottier elsewhere is a geography question, and it is the one that decides the ordering: whichever provider covers your actual list best goes first, and that is a measurement over 500 rows rather than an opinion.
Imo those databases are never worth it. You're paying for the same scraped lists as everyone else, which means low deliverability and high spam complaints. We build our own lists from Sales Nav and then use the waterfall enrichment in la growth machine to find verified emails. Itss more work upfront but the reply rates are 3x better for our clients
r/EmailProspecting·April 2026·1 points
The 3x figure is this person's own and nothing here corroborates it, so read it as a claim about their clients rather than a result. The architecture underneath it is the one this page recommends: source the list yourself, resolve it with a waterfall, and treat the bundled database as one source in that waterfall rather than as the list.
We're after people's information and that changes minute-to-minute. Still, if Lemlist is roughly comparable to Clay in terms of both found emails and email quality, I'd be satisfied... though I still plan to run whatever it returns through my normal scrubbing process to try and weed out as much of the bad data as possible.
r/EmailProspecting·February 2026·1 points
From somebody evaluating lemlist for a client with no budget, and the first clause is the honest frame for every provider on this page. It is also what the free freshness check exists for: an update date on a cached record turns changes minute-to-minute from an anxiety into a decision about whether to spend 2 credits refreshing it.
honestly before shopping for another all-in-one, i'd do a ruthless "what tab does the SDR actually live in?" audit. pick 1 system of record and 1 operator dashboard. everything else has to be background plumbing or it gets cut. if apollo/clay/lemlist/warmbox all need human attention, you don't have 6 tools, you have 6 jobs.
r/Coldemailing·April 2026·1 points
Answering a head of growth spending twelve hours a week keeping six tools running. Background plumbing or it gets cut is the right test for this pair: an API call inside a pipeline nobody opens passes it, and a second enrichment tool with its own dashboard and its own credit balance does not.
Most of the context-switching pain comes from treating the whole stack as one workflow when it's actually three: enrichment, sending, and reply handling.
r/Coldemailing·April 2026·1 points
One sentence, and it is the division of labour every page in this directory assumes. On this pair it resolves the ordering question too: enrichment is its own job with its own meter, so two providers in it need a sequence, and the sending tool owning one of them is a billing arrangement rather than an architecture.
Nobody discusses this pair by name, so the search was for the job, and the job here has an unusual shape: lemlist sells enrichment itself, so the question is which of two overlapping providers runs first. Two people who have actually used lemlist's own database report it as competent and commodity, which is the most useful possible input to that decision. The other thread worth reading is somebody drowning in a six-tool stack, which is the cost of getting the ordering wrong.
Three of the five are from one thread about whether lemlist's own 600M database is worth buying, which is the right thread to read before deciding what runs second. None of them answers it for your list, and nothing can: the grid above shows what each ordering costs and the only input it needs is four numbers you get by running both over 500 of your own rows.
This is the one sequencer pairing in the directory where the two products overlap, and pretending otherwise would be dishonest on a page published by one of them. lemlist sells enrichment, including a bulk endpoint, and Reverse Contact sells enrichment. There is no integration between two data sources in the ordinary sense; what exists is a waterfall, and the only question is which one runs first on which kind of row.
The way to answer it is the same way you should answer it for any provider, which is to stop reading marketing numbers. Reverse Contact publishes a global identity match rate of 70% or better, and that is a figure about everyone's data rather than a promise about yours. Take 500 rows of your own list, run both, and count the resolves and the disagreements. That number predicts your coverage and your bill, and nobody publishes it because nobody can.
Once the order is decided the plumbing is small. A Clay table runs a waterfall natively, branching on a null, and pushes the result into lemlist. For a script, the lemlist API is pleasant once the Basic auth is right. And if the campaigns are fed from a CRM rather than a list, enriching at that end instead means every tool downstream gets the same record, which is the argument the Smartlead page and the Instantly page both end up making too.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under lemlist, Reverse Contact and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
Not as an app. lemlist has an API, Reverse Contact has an API, and the connection is a few lines once you are past the Basic auth with its leading colon. What makes this pair worth thinking about is not the connection but the overlap: lemlist sells enrichment itself, so the real question is which of two providers runs first and what you pay on the rows both can resolve.
HTTP Basic, not Bearer, and lemlist's own documentation puts that in red. The username is empty and the password is your API key, so you base64-encode the string :YourApiKey, leading colon included, and send it as Authorization: Basic. Sending the key as a Bearer token fails, and it is the single most common first mistake against this API.
Twenty requests per 2 seconds, on all routes, per API key. Responses carry Retry-After, X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. The reset header is a human-readable date rather than a Unix timestamp, which lemlist flags and which breaks naive parsing.
Because coverage is never one provider's whole answer, and because a waterfall is the normal shape for this. Run the cheaper or bundled source first, send what it could not resolve to the second, and measure both on your own list. The honest reason to compare is that neither vendor publishes a match rate you can hold them to on your data.
Before the lead enters a campaign, same as every sequencer here. lemlist renders variables from the lead record at send time, and a missing variable falls back rather than waits.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.