Smartlead and Reverse Contact

Featured

The API key rides in the query string, which decides where this runs.

What you have to buy first

A Reverse Contact API key and a Smartlead API key, used server side

What moves

Contacts, Companies, one way, in.

Smartlead is the most API-complete sequencer at its price, and the enrichment build is the standard shape: enrich the row, then upload it, rather than uploading and fixing afterwards. Two details set it apart. The key travels in the query string rather than a header, which is a real operational constraint on where the calls can run. And the hourly limit of 1,000 on Standard, rather than the per-minute figure, is what caps a bulk pass.

What actually syncs

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.

WhatDirectionWhat that means in practice
The list, before upload One way, out Enrich each row with /v2/enrich/persons from its email. 2 credits on a match, nothing on a miss or a check.
Lead upload One way, in POST the enriched leads with their custom fields, so personalisation has values to render from.
Reply and event webhooks One way, out Smartlead fires events back out, which is how a reply reaches a CRM or a Slack channel.
Anything back to Reverse Contact One way, out Nothing. This is a read layer, and your pipeline decides which custom fields get 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.

Which field lands where

Everything happens outside Smartlead: enrich the row, then upload it. What is worth laying out is which enriched value becomes which custom field, and which parts of the response should stop a row being uploaded at all.

In SmartleadIn Reverse ContactWhat to know about the match
An email on the row POST /v2/enrich/persons, 2 credits Identity, the current role, history, education, skills and location on one schema. A confident null costs nothing, because Reverse Contact charges 0 credits on every 4xx and 5xx.
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, which is both cheaper and more consistent across a campaign.
A profile URL already on the row POST /v2/fetch/persons, 1 credit Half the credits, and unmetered from the $249 plan rather than the $699 one. Lists sourced from profiles rather than forms often already carry one.
currentPosition.title A custom field, named to match the sequence The value most openers reference. The key has to match the merge variable exactly, because a near-miss renders the fallback rather than erroring.
company.name and employeeCount Custom fields on the lead The two values that carry most first-line personalisation. Headcount is a number in the response and a string in a merge field, so decide the formatting before the upload rather than per row.
Add lead to campaign The campaign has to exist first Smartlead campaigns are built in Smartlead. The sequence, the mailboxes and the schedule are decisions taken before any of this runs, and the campaign id is what the upload is pointed at.
The api_key parameter In the query string, not a header Documented, and the reason this route is server side. URLs are logged by things you do not control, so treat the key as something that will end up in a log and rotate it accordingly.
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 fields that should stop an upload rather than improve one

The rest of this directory treats an enrichment response as values to write. On a sender it is also a list of reasons not to send, and that half is almost never built. Each row is a documented field, and each is a row to drop rather than a row to personalise better.

In the responseWhy it is a reason not to send
isInRemembranceThe 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 recordThey have changed job, so a campaign written for the old role is about to reach the new one. Re-qualify rather than refresh
isOpenToWorkThey 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 scoreNothing matched confidently. Sending the fallback text is a decision, and on a cold list it is usually the wrong one
metadata.updatedAt, from long agoStale rather than wrong, which is the one case where a 2-credit live refresh earns its money
followersCount and hasVerificationBadgeNot suppression at all. Listed because they are the fields teams reach for as a seniority proxy, and neither is one

What does not cross

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.

  • An app inside Smartlead. There is none, which is consistent with Reverse Contact maintaining apps on Clay, Zapier and Make and nothing inside any CRM or sequencer.
  • A business email or a direct phone number from Reverse Contact. Both are separate endpoints at 3 and 20 credits, charged only when one is found, and the email finder is asynchronous.
  • Anything that repairs an email already sent. Personalisation renders at send time, so enrichment after the upload improves later steps and nothing before them.
  • Campaign creation. Every upload is pointed at a campaign that already exists, built in Smartlead with its own sequence, mailboxes and schedule.

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 seven 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.

Field map

The suppression table is worth more here than on the CRM pages, because the output of this pipeline is an email somebody receives rather than a field somebody reads. A wrong value in a CRM is untidy; a wrong value in a cold email is sent, with your domain on it, and the recipient is the one who finds the mistake.

What the Smartlead limits let you move in an hour

Smartlead meters per API key across every endpoint combined, and publishes three figures for each plan: a per-second burst, a per-minute limit and a per-hour limit. The hourly one is what caps a bulk pass, and it is the figure people do not look at until a pass stops halfway. Pick one on each side and the grid marks the answer.

Pick one on each side.

Smartlead planUpload a few hundred enriched leadsUpload two thousand in one sittingLoop over the three tight endpointsPoll campaign state while uploading
Standard: 10 a second, 60 a minute, 1,000 an hour Fits No No Tight
Pro: 20 a second, 120 a minute, 3,000 an hour Fits Fits No Fits
Enterprise: custom on all three Fits Fits No Fits
Fits
Inside the documented ceilings with room to spare. A few hundred uploads is well under even the Standard hourly figure of 1,000, and Pro triples that to 3,000 an hour alongside 120 a minute.
Tight
Possible and crowded. On Standard the whole budget is 1,000 an hour across every endpoint combined, so polling campaign state during an upload is spending the same allowance twice.
No
Over the ceiling. Two thousand uploads cannot fit in a Standard hour at all, and the third column is no on every plan: leads statistics by campaign, all-leads activities and domain-wise mailbox health metrics each carry their own limit of 10 requests per 60 seconds per account, independent of the plan.

Counted off that grid, of twelve pairings: seven give you fits, one gives you tight, four give you no. The third column is the one that does not move, and that is the finding: three endpoints are capped at 10 requests a minute per account whatever you pay, so no upgrade makes them loopable. Everything else here is an hourly arithmetic problem, which an upgrade does solve, and and which Instantly answers with 6,000 requests a minute on every workspace.

How to connect Smartlead to Reverse Contact

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.

Who has to do it
Whoever can generate a Smartlead API key and whoever runs the server side of this, because the key cannot safely live in a browser. Plus a Reverse Contact key.
How long it takes
An afternoon. Deciding to enrich before the upload rather than after it takes no time and saves all of it.
Setup checklist 0 of 8 done

Your own pipeline

Smartlead renders personalisation at send time, so a lead uploaded without the fields a sequence references gets the fallback text and nothing later repairs the email that went. Enriching first is also cheaper, because you can drop the rows that did not resolve instead of sending to them.

Not a browser, not a client app

Smartlead documents authentication as api_key in the query string rather than in a header. Request lines get logged by proxies, error trackers and anything that records a URL, so this route belongs server side and the key belongs on the ordinary rotation schedule rather than treated as a secret that stays secret.

Smartlead: your plan

Per API key the limits are 60 a minute and 1,000 an hour on Standard with a 10 a second burst, and 120 a minute and 3,000 an hour on Pro with a 20 a second burst. The hourly figure is what caps a bulk pass, and it is plan-wide across every endpoint combined rather than per endpoint.

POST /v2/fetch/persons/check

The free check says whether a profile is cached and when it was last updated, so a pass over a list spends 2 credits only where it needs to. Doing it in this order is what Reverse Contact recommends and it is the main lever on this bill.

Your pipeline

The response carries more reasons not to send than reasons to send. A current employer that disagrees with your record, an isInRemembrance flag, a confident null: each one is a row to drop rather than a row to personalise better.

Smartlead: the campaign sequence

Custom fields are key-value pairs and the key has to match the merge variable in the sequence character for character. A near-miss renders the fallback, which looks like a sending problem and is a naming problem.

Smartlead: the add-leads endpoint

Three endpoints carry their own limit of 10 requests per 60 seconds per account, independent of the plan-wide figure: leads statistics by campaign, all-leads activities, and domain-wise mailbox health metrics. None of them belongs in a loop.

Smartlead: a campaign with one mailbox

The rendered first email is the only artefact that tells you whether the mapping worked. The API reporting success means the lead was accepted, which is a different claim entirely.

Two of those eight exist because of one documented detail, which is that the key rides in the URL. That decides where the code runs and how the key is handled, and it is the single biggest operational difference between this pair and the lemlist one, where the same key goes in a Basic auth header.

Hand it to an agent instead

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/smartlead-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/smartlead-reverse-contact.md

What breaks, and what nobody tells you

Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.

The key is a query parameter, not a header
Smartlead documents authentication as api_key in the query string. URLs get logged, by proxies, by error trackers, by anything that records a request line, so this route should run server side and the key should be rotated on the normal schedule rather than treated as a secret that stays secret.
1,000 requests an hour on Standard
Per API key: 60 a minute and 1,000 an hour on Standard with a 10 a second burst, 120 a minute and 3,000 an hour on Pro with a 20 a second burst. The hourly ceiling is the one that bites on a bulk pass, and it is plan-wide across every endpoint rather than per endpoint.
A few endpoints carry their own limit
Smartlead notes that some endpoints are expensive enough to have a dedicated limit independent of the plan-wide one. Check the endpoint you intend to hammer before designing a loop around the headline figure.
Personalisation renders at send time
A lead uploaded without the fields a sequence references gets the fallback text, and nothing later repairs the email that already went. Enrichment belongs before the upload, which is also where it is cheapest, because you can drop the rows that did not resolve instead of sending to them.
Credit packs expire after 3 months
Reverse Contact credit packs run 5K to 1M and are valid 3 months. A sender that runs in campaign bursts can reach the end of a quarter holding credits it paid for and cannot use, which is the case their Unlimited plans are priced for.

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.

The 8 failures people actually hit

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.

01

The email went out with the fallback text instead of the enriched value

WhyCustom fields are key-value pairs and the key has to match the merge variable in the sequence exactly. A near-miss renders the fallback rather than failing.

Compare the field names character for character, then send one lead to a test campaign and read the rendered email. The rendered email is the only place this is visible.

02

The upload reported success and the lead is not in the campaign

WhyAdd lead to campaign requires a campaign that already exists and is active. Campaigns are built in Smartlead, not through this pipeline.

Confirm the campaign id against the account rather than against your own config. A campaign renamed or archived in Smartlead breaks the upload without the id changing.

03

429 after about a thousand requests

WhyThe hourly ceiling is 1,000 on Standard and 3,000 on Pro, per API key and plan-wide across every endpoint combined, with per-minute limits of 60 and 120 underneath it.

Pace against the hourly figure rather than the per-minute one, and count every endpoint toward it. The per-minute limit is the one people test and the hourly one is the one that stops a bulk pass.

04

429 from one specific endpoint while everything else works

WhyThree endpoints carry their own limit of 10 requests per 60 seconds per account, independent of the plan-wide figure: leads statistics by campaign, all-leads activities, and domain-wise mailbox health metrics.

Take them out of the loop entirely and call them on a schedule instead. No plan raises these three, so there is no upgrade that fixes it.

05

The API key turned up in a log

WhySmartlead documents authentication as api_key in the query string, and request lines are logged by proxies, error trackers and anything that records a URL.

Run this server side, keep the key out of any client, and rotate it on a schedule rather than only after an incident. This is a property of the API rather than a mistake you made.

06

A campaign reached somebody who left the company

WhyThe enrichment wrote a title and nothing compared the returned current employer against the company on the row.

Compare currentPosition.companyName with your own value and drop the row rather than uploading it. On a sender this check is worth more than any personalisation it would have enabled.

07

Everything stopped, including the calls that were free

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 reason the lookup did.

08

Credits expired before a campaign used them

WhyReverse Contact credit packs run from 5K to 1M and are valid 3 months, and a sender that works in campaign bursts does not spend evenly.

Size the pack to a quarter of real volume rather than to a discount, or move to an Unlimited plan, where the cached endpoints the plan names stop being metered at all.

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.

When this is the right integration

Set it up when

  • Enriching a list before it is uploaded to a campaign
  • Dropping unresolved rows rather than sending to them
  • A team comfortable running the calls server side

Do not bother when

  • Anything that would put the key in a browser or a client
  • A sweep bigger than the hourly ceiling allows on Standard
  • The list already carries the fields the sequence uses

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.

What practitioners say about it

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.

The sender is not the variable, and a bounce rate proves it

Your data is the problem, not smartlead. no such user and invalid recipient are dead addresses, switching the sending tool fixes none of that. verify before you send, others already covered that part. the thing people skip is the accept-all bucket. most verifiers dump those into unknown or flag them all as risky, so you toss real inboxes out with the junk.

r/Coldemailing·July 2026·2 points

Answering somebody whose campaign bounced at over 60% in its second week. Verify before you send is the same instruction as enrich before you upload, for the same reason: nothing downstream of the send can repair it. The accept-all point is a separate problem from identity resolution and worth knowing before you blame a provider for a thin list.

The sending tools assume you already have the list

yeah the data piece is what kills the comparison for me too, smartlead and instantly both assume you already have lists and prospeo's been our fix for that part

r/EmailOutreach·May 2026·3 points

From a pricing comparison between the three senders, and it is the reason a pricing comparison between them does not settle anything. The assumption named here is the gap this pair fills, and it is an assumption rather than a limitation: a sender that also sold you the data would be a different product with a different bill.

What the sending tools actually are, said plainly

To be clear, instantly Apollo and smartleads are all just front end management tools for campaign, lead list, and sending triggering through any API/SMTP servers (like Gmail, M365, sendgrid, SES, etc.) and they shouldn't have a direct effect on deliverability. Your email copy, leads, and sending patterns/volume are what matters the most

r/Emailmarketing·June 2024·5 points

A clear-eyed description of the layer, and the last clause lists three variables of which exactly one is addressable from this page. Leads is the one, which is why the enrichment belongs before the upload and why the suppression rules above matter more than any personalisation they enable.

The dissenting view, and it is the right question to ask first

If you only need 2 to 3 solid wins per quarter I would focus less on stack and more on signal quality. Apollo is fine as a base but it gets messy when you rely on job titles alone. Clay makes sense if you are actually enriching around specific buying triggers not just adding more data for the sake of it. The real upgrade is tighter ICP definition and better research driven emails not necessarily more tools.

r/agency·February 2026·2 points

Answering somebody about to add two tools to fix a targeting problem, and the challenge lands. Adding more data for the sake of it is the failure mode this page is most likely to cause, and the honest filter is whether a field changes who gets contacted. At two or three wins a quarter the answer is usually no.

The research that qualifies somebody is the research that writes the email

The issue is that most people treat lead sourcing and writing as two separate steps. They pull a list and then try to force a template onto it. In high-level consulting, the research that proves someone is a fit is the exact same research that should write the email.

r/agency·February 2026·1 points

The best argument for enriching before the upload rather than after it, and it is not about cost. If the same lookup decides whether somebody qualifies and supplies the line that opens the email, then it has to happen before either decision, and a row that did not resolve is a row with nothing to say rather than a row with a gap.

What the threads add up to

Nobody discusses this pair by name, so the search was for the job: getting a cold list good enough to send. The threads are unusually blunt because the feedback loop is a bounce rate, and the consensus is stated in one sentence by somebody answering a 60% bounce: the data is the problem and switching the sending tool fixes none of it. The dissenting view, that most teams should fix their targeting rather than their stack, is worth reading too.

The first and the fourth quotes disagree about whether to build this at all, and both are right about different teams. What they share is where the decision is made, which is upstream of the sender: a list that resolves and qualifies before the upload is the only thing either of them would call an improvement, and that is one credit for a check and two for a lookup rather than a change of platform.

The longer answer

The right mental model for a cold email tool is that the sequence is a template and the list is the content. Everything that makes a first touch worth reading comes out of the row: the title that proves you know who they are, the company detail that proves you looked. A list of bare email addresses produces a sequence that reads like a list of bare email addresses, and no amount of copywriting fixes it after the send.

That is why enrichment belongs before the upload rather than after it, and why the honest version of this build drops rows rather than sending to them. Reverse Contact returns null with a confidence score instead of a guess, so an unresolved row is a decision you can make rather than a wrong title you will send. The Instantly build reaches the same conclusion with far more generous limits, and the lemlist one has to account for lemlist shipping enrichment of its own.

For doing the work there are two shapes and they suit different teams. A Clay table enriches the list, lets you look at the raw responses beside the rows, and pushes to Smartlead with a native integration, which is the version a non-engineer can own. A script that enriches and then uploads is cheaper per row and needs somebody to maintain it. Both are better than uploading first.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every tier requirement, sync direction and limit on this page was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

One fact about the publisher, stated here rather than in the page above it: Reverse Contact has no CRM marketplace app and no app inside a sequencer. Its three native apps are on Clay, Zapier and Make, and every other route is its API, its CLI or its MCP server. That is a deliberate shape for a data layer rather than a missing release, and it is what the routes on this page are describing.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-10-11
Sources
7 vendor documents
Paid placement
None

The integration moves the record. Something has to fill it.

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 Smartlead, 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.

Smartlead and Reverse Contact, asked and answered

How does Smartlead authenticate?

With the API key as a query parameter, api_key=YOUR_API_KEY, rather than in a header. Everything works, and it means the key appears in request URLs, which tend to be logged by proxies, error trackers and anything that records a URL. Keep the calls server side and keep the key out of anything that writes URLs to disk.

What are the rate limits?

Per API key: 60 requests a minute and 1,000 an hour on Standard, with a burst of 10 a second; 120 a minute and 3,000 an hour on Pro, with a burst of 20 a second; custom on Enterprise. The limit is plan-wide across all endpoints, so campaign, lead and analytics calls all draw on the same budget.

Where does the enrichment belong?

Before the lead is added to a campaign. Smartlead renders personalisation from the lead's custom fields at send time, so a lead uploaded with an email and nothing else gets the fallback version of every variable. Enrich first, upload second, and the sequence has something to say.

Can I enrich leads already in a campaign?

You can update them through the API, and it helps the later steps rather than the ones already sent. The useful version of this is a sweep over paused or not-yet-started campaigns, where nothing has gone out and the whole sequence still benefits.

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.

Ask an assistant