The only route on this hub that needs no Sales Navigator edition, and the one the User Agreement addresses by name.
A Reverse Contact API key. No LinkedIn edition, no LinkedIn API access and no browser extension
Contacts, Companies, one way, out.
Every other page on this hub answers what you are allowed to connect. This one does not connect to LinkedIn at all, which is both its appeal and the thing to be clear-eyed about. A profile URL resolves to a record for 1 credit without any Sales Navigator edition, any API approval or anything running in a rep's browser, and section 8.2 of the User Agreement still addresses information obtained from the Services through third parties such as data aggregators. The mechanical risk and the contractual question come apart here, and a reader deserves both rather than whichever one suits the publisher.
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 |
|---|---|---|
| A profile URL | One way, out | Copied, exported or already on the record. Nothing reads it from LinkedIn on your behalf. |
| The lookup | One way, out | POST /v2/fetch/persons for a profile URL at 1 credit, or /v2/enrich/persons from an email at 2. |
| The record | One way, out | Identity, current role, history and the company, on the same schema whichever identifier went in. |
| Nothing at all | One way, out | No data is written to LinkedIn, no connection is made and no message is sent. There is no inbound direction on this page. |
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.
There is nothing to map in LinkedIn, because nothing is written to it. The map that matters here is the one between the identifier you happen to hold and what it costs, which is the only part of this page that varies by more than a rounding error.
| In LinkedIn | In Reverse Contact | What to know about the match |
|---|---|---|
| A LinkedIn profile URL | POST /v2/fetch/persons, 1 credit | The cheap direction, and unmetered from the $249 plan. A list exported from a profile source usually already carries this column. |
| An email address | POST /v2/enrich/persons, 2 credits | The reverse direction, and unmetered only from the $699 plan. This is the route for an old CRM record that has an address and no profile. |
| A first name, last name and company | POST /v2/enrich/persons, 2 credits | Same price as an email and a thinner identifier, so the confidence score matters more. Raise the precision threshold rather than accepting what comes back. |
| A company domain | POST /v2/enrich/companies, 2 credits | Firmographics from a domain, on the same schema. The enrich_company MCP tool takes a domain as well since November 2026, so an agent no longer has to search first. |
| currentPosition.title and companyName | Your CRM, on fields it owns | The two values a list sourced from profiles is most likely to have wrong, because a profile export is a snapshot and people move. |
| The position history | Context, not a field | Useful for a human writing a first line and poor as a filter. Store it if you will read it and skip it if you will not. |
| The confidence score | A branch, decided in advance | Returning null rather than a guess only helps if something downstream acts on it: another provider, a review queue, or writing nothing. |
| Anything at all | Not LinkedIn | No write, no connection request, no message, no activity. There is no inbound direction in this integration and no product surface that would take one. |
Reverse Contact publishes which plan stops metering which family of calls, and the families are divided by the identifier rather than by volume. Each row below is a starting point somebody actually has, with what it costs and the plan at which it stops being counted.
| What you already hold | The cost, and where the metering stops |
|---|---|
| A LinkedIn profile URL | 1 credit as a cached lookup, and unmetered on Go at $249 a month. The cheapest identifier there is, and the one a profile-sourced list already has |
| An email, a name or a domain | 2 credits as a reverse lookup, and unmetered only on Max at $699 a month. The same build costs almost three times as much to run from here |
| A search, rather than an identifier | People and company search is 1 credit per profile delivered and unmetered on Plus at $449. The count endpoint that tells you how big a result set is costs nothing at all |
| Nothing, and you want to check freshness | Free on every plan, including the search count. This is what a sweep should run first, and it is paused below 2 credits along with everything else |
| A record that needs a live refresh | 2 credits, charged when the job is created and kept even if it finds nothing. The one endpoint here where a miss is billed, on every plan including Platform |
| A need for a phone number or a business email | 20 and 3 credits, charged only when one is found, on credits on every plan. Both are asynchronous and return a task id to poll |
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 what you already hold rows and four documented exclusions, each one's note, and the nine 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 gap between the first two rows of the second table is the whole economics of this page: the same record, resolved from a profile URL or from an email, is 1 credit or 2 and stops being metered at $249 or at $699. Audit which column your list already has before anybody prices a plan, because on a list sourced from profiles the answer is usually the cheap one and almost nobody checks.
This hub's rule is that every page says which category an integration is in before it says what it does, and this page is a category the hub did not originally have. The columns are the four things that decide whether a route is usable, and reading down the first two is more informative than reading across any row. Pick one on each side and the grid marks the answer.
Pick one on each side.
| The category | A Sales Navigator edition | Risk to a rep's own account | Addressed by section 8.2 as written | Somebody to escalate to |
|---|---|---|---|---|
| CRM Sync, through an approved partner | An Advanced Plus upgrade | No rep in the path | An authorised route | Both vendors |
| An embedded tile in a partner product | An Advanced Plus upgrade | No rep in the path | An authorised route | Both vendors |
| A browser extension over linkedin.com | No edition at all | Risk to a rep | Reached by the clause | Nobody |
| A third-party database, from a profile URL | No edition at all | No rep in the path | Reached by the clause | One vendor only |
Counted off that grid, of sixteen pairings: two give you an Advanced Plus upgrade, two give you no edition at all, one gives you risk to a rep, three give you no rep in the path, two give you reached by the clause, two give you an authorised route, two give you both vendors, one gives you one vendor only, one gives you nobody. The first two rows are identical, which says that the two authorised categories behave the same way and both cost an edition upgrade. The sharper reading is how the first and third columns cross: the two routes that need no edition are the two the agreement addresses, and the two covered by an agreement are the two you have to pay Advanced Plus for. There is no row that is free of all four costs, and a page that implied otherwise would be selling something.
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.
LinkedIn: the User Agreement, and your own counsel
The clause covers information obtained from the Services directly or through third parties such as data aggregators or brokers, without the content owner's consent. This page states the clause and does not interpret it for you, and this is the step that cannot be undone after a list has been built on it.
Your CRM or your list
A profile URL is a 1-credit cached lookup and unmetered from the $249 plan. An email, a name or a domain is a 2-credit reverse lookup and unmetered only from $699. This single question changes the cost of a backfill by more than any other decision on the page.
Reverse Contact: Workspace > API Keys
The trial takes no card and a new account starts with 500 credits, which is 500 profile-URL lookups or 250 reverse ones, and it runs until those credits are spent rather than for a number of days. The published 70%+ identity match rate is a global figure and Reverse Contact says to measure your own, so spend the trial on that rather than on a demo list.
The request, as a parameter
Reverse Contact returns null with a confidence score rather than a guess, and the threshold can be raised on the request. Setting it after seeing the results is how a team talks itself into accepting thin matches, which on a list sourced from profiles is the main way this goes wrong.
POST /v2/fetch/persons/check
The free check says whether a profile is cached and when it was last updated. On a list you have enriched before, this is the difference between re-resolving everything and paying only for what has actually moved.
Your middle layer or your Clay table
A list built from profiles six months ago is a list of people some of whom have moved, and a disagreement between the returned current position and the account on your record is the most valuable thing in the response. It is also the only thing on this page that no LinkedIn integration will tell you, because CRM Sync moves data forward rather than auditing what is there.
Your CRM, your sequencer or your warehouse
Nothing in this build writes to LinkedIn, makes a connection or sends a message, and there is no product surface in LinkedIn that would accept it. Treat the output as a record for your own systems and the page's shape follows from that.
Clay, a sheet, or a script
On [the Clay route](pair:clay+reverse-contact) this costs Clay credits and no Reverse Contact account at all, which makes it the cheapest measurement available. Your own match rate on your own list is the number that decides everything downstream, and it is never the published one.
The first step is the only irreversible one and it is not technical. Everything after it is a single API call wrapped in whatever you already use, which is why the effort on this page is minutes rather than the days most of this hub requires.
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/linkedin-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/linkedin-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.
WhyA profile export is a snapshot, and LinkedIn data ages faster than most because the field that matters most is the one people change.
Re-resolve from the profile URL rather than re-exporting, which costs 1 credit a row and is unmetered from the $249 plan. Run the free check first so you only pay for the rows that have actually moved.
WhyThe estimate assumed a cached lookup from a profile URL at 1 credit and the list actually held email addresses, which is a reverse lookup at 2 and unmetered only from the $699 plan.
Audit which identifier the list carries before pricing anything. Where both are present, send the profile URL, because the record that comes back is the same either way.
WhyThe covered calls are unmetered up to 100,000 profiles per workspace per UTC day, after which they are refused until midnight UTC.
Spread the job across days and watch the clock, which is UTC rather than local. The minute limit is 100 on all three Unlimited tiers, so paying more buys unmetered families rather than throughput.
WhyA thin identifier such as a name and a company was accepted without a precision threshold, so low-confidence matches were written as facts.
Raise the threshold on the request and decide in advance what a null should do. Reverse Contact returns null with a confidence score rather than a guess, which is only useful if something branches on it.
WhyThe build was treated as a technical choice. Section 8.2 addresses information obtained from the Services through third parties such as data aggregators or brokers, and that is a question for counsel rather than for an engineer.
Have the conversation first, which is step one of the checklist for this reason. A list already built on an unanswered question is the expensive version of this problem.
WhyNot this build. LinkedIn restricts accounts over tools that scrape, modify the appearance of, or automate activity on its website in a member's own session.
Find the extension. If a step in your process asks a rep to log in to LinkedIn, that part is in a different category from the rest of this page and carries a different risk.
WhyBelow 2 Reverse Contact credits the free Check endpoints are paused as well and answer 402 NO_CREDITS.
Watch quotas.workspace.credits.left on every response, and check GET /v2/usage on a schedule because it keeps answering whatever the balance.
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 2025 to 2026 were read in full on 28 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.
Most people scrape Sales Navigator with tools like Evaboot or PhantomBuster to get the CSV, then clean it up and import. Thats the standard workflow and it works fine for small teams. [...] our customers use either the tools mentioned above or Findymail and ScrapeLi but this is a very grey software haha
r/CRMSoftware·August 2026·1 points
Written by somebody who runs a CRM and whose own customers use these tools, which makes the last five words the most honest sentence in the harvest. The hub's position is that plenty of competent teams work this way and should do it knowingly, and this is what knowing sounds like. Note also that it describes the whole market this page sits in: the common route is an extension and a CSV, not an API.
If you're pulling from Sales Nav, Evaboot + Apollo is one of the cleanest workflows I've used. Evaboot cleans your exports (names, titles, etc.), then you run the list through Apollo for verified emails and sometimes phones. [...] Just make sure you're not enriching stale lists...LinkedIn data gets old fast.
r/LeadGeneration·July 2025·2 points
The last clause is the argument for re-resolving rather than re-exporting, and it is the one thing on this page that a profile URL makes cheap: 1 credit a row, unmetered from the $249 plan, with a free check first so you pay only for what moved. The rest of the comment is a two-step pipeline where the clean-up and the enrichment are separate vendors, which is how most of these lists are actually built.
Apollo [...] Clay (waterfall) [...] Clay (neverbounce) This is the most cost-effective workflow I've found for getting high-quality and verified emails. Basically, I use apollo to scrape leads, export to csv, then upload to clay and run their waterfall thing to grab emails from like every provider out there. [...] Then run everything through NeverBounce to verify. I usually get around 85% verification which is pretty decent
r/LeadGeneration·July 2025·3 points
One person's figure on one list rather than a benchmark, and the shape is the useful part: source, waterfall, verify. It is the same architecture the two competitor pages in this directory describe, assembled by somebody who was not thinking about architecture, and the verification step at the end is the admission that no single provider is trusted on its own.
The thing that caught us a few times was assuming the contact info was good just because the lead itself looked right. We started running the emails through clearout email verifier before importing the final list. It's a pretty small step, but it saved us from reps finding bad email addresses only after they'd already started working the list.
r/CRMSoftware·August 2026·1 points
Two different confidences being conflated, which is exactly what a confidence score on the match is for. The person was identified correctly and the address attached to them was wrong, and the only way anybody found out was a rep working the list. A threshold set in advance and a null that branches are the cheap version of the lesson this team paid for.
note profile changes from those personas in contacts in your connected Salesforce system, and sync the changes back to Salesforce, while downloading a list for manual review. In my experience, it rarely gets a job change wrong. [...] But if you're running a really big org with dozens (hundreds?) of changes a day the manual review could be too much.
r/SalesforceDeveloper·June 2026·1 points
Written about a competitor and the operational point transfers whoever supplies the data: detecting the change is the easy half and deciding who looks at it is the half that fails. The second sentence is the real warning, because a signal arriving faster than anybody can act on it becomes a queue nobody reads. Decide the volume you can review before you decide the frequency you sweep at.
Nobody discusses this pair by name, so the search was for the job: turning a LinkedIn list into records with contact details on them. This is the most candid harvest of the seven, because the question is asked constantly and the honest answer is uncomfortable. One commenter who sells a CRM describes the standard workflow and then calls the category what it is, which is more use than any vendor page on the subject.
The candour in the first quote is why this harvest is worth reading twice: the category is widely used and widely understood to be grey, and no vendor page on the subject says so. Taken together the five describe a market that sources from LinkedIn, resolves somewhere else and verifies at the end, which is a sequence rather than an integration and is the honest shape of everything on this hub.
This hub exists because LinkedIn restricts integration as a matter of policy rather than of pricing, and the three categories it describes are an approved API partnership, an embedded tile inside a partner product, and a browser extension drawing over LinkedIn in somebody's own session. This page is a fourth thing, and the hub would be incomplete without it: a third-party database of public professional profiles, queried by URL, with no LinkedIn account in the loop at all.
The reason that matters commercially is the edition. CRM Sync with HubSpot and the Salesforce version both need Sales Navigator Advanced Plus, which is quoted rather than listed and has to be priced across every seat. A lookup that resolves a profile URL needs no edition, no partner approval and no seat, which changes who can do it from enterprises with a procurement cycle to anybody with an API key.
The reason it matters contractually is that the User Agreement anticipated it. The clause LinkedIn's own help centre quotes reaches information obtained from the Services through third parties such as search tools, data aggregators or brokers, so a reader who concludes that using a database instead of a scraper settles the question has not read it. What genuinely differs is the mechanism and therefore the exposure: no rep account can be restricted for a lookup nobody made from a browser. Both of those are true at once and this page would be worthless if it printed only the convenient one.
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 LinkedIn, 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.
No, and there could not be one in the usual sense. Sales permissions on the LinkedIn API need approval as a Sales Navigator Application Platform partner, and LinkedIn's documentation says it is not currently accepting new partners. Reverse Contact does not use the LinkedIn API at all: it holds its own database of public professional profiles, so a profile URL goes in and a record comes back without anything touching linkedin.com.
None. That is the distinctive thing about this route and the reason this page exists on a hub where CRM Sync, activity writeback, record matching and the partner tiles all need Advanced Plus. Nothing here authenticates against LinkedIn, so no edition gates it and no seat count changes the price.
That is a question for your own counsel and the page will not pretend otherwise, but you should read the clause before deciding. Section 8.2 prohibits copying, using, displaying or distributing information obtained from the Services, in LinkedIn's words "whether directly or through third parties (such as search tools or data aggregators or brokers), without the consent of the content owner". A separate clause names crawlers, browser plugins and add-ons. The second describes an extension and the first reaches a third-party database, so this route is addressed by the agreement even though nothing runs against LinkedIn.
Mechanically, completely. An extension runs in a rep's own authenticated session against LinkedIn's website, and LinkedIn's help centre says members using such tools risk having their accounts restricted or shut down and that the tools may stop working without notice. This route involves no rep session, no plugin and no traffic to linkedin.com, so the specific risk of losing somebody's account is not present. The terms question above is a separate one and is not resolved by that.
A profile URL, by half. A cached lookup from a profile URL is 1 credit and stops being metered on the $249 plan; a reverse lookup from an email, a name or a domain is 2 credits and stops being metered only on the $699 one. So a list that already carries profile URLs is on the cheap path and a list of bare email addresses is not, which is the most consequential line on this page for anybody pricing a backfill.
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.