Reverse Contact V2: Rebuilt from the Ground Up
Reverse Contact is reinventing itself. Rebuilt from the ground up to match the reality of teams shipping serious B2B products and workflows.
Reverse Contact started with a straightforward problem: you have an email address, you need to know who is behind it. That simple promise quickly found its audience: thousands of sales, growth and marketing teams made it part of their daily workflow to qualify leads, enrich their products, pipelines and CRM workflows.
That original mission has not changed. But the product had to. Because our users did not just adopt Reverse Contact, they pushed it further. They came back with new use cases, new constraints, new ambitions. They needed more input types and more flexible delivery methods and rock-solid guarantees on freshness. Each conversation, each feature request, each integration pushed us to rethink what Reverse Contact could become. So we did it.

Reverse Contact V2 is our answer
The first thing we tackled was speed and trust. And we backed it with a real commitment: if the data we return is not fresh enough, you don't pay for it. It's fresh or free.
Then we looked at reliability. In V1, some requests could fail. With Reverse Contact V2, every request gets an answer. We built an entirely new system to make sure no call is left behind, whether the response comes in real time or asynchronously.
We also rebuilt the entire interface from scratch. The old dashboard had served its purpose, but it no longer matched how teams actually use the product today. The new experience is faster, cleaner and designed for the workflows that matter in 2026.
Beyond that, this article walks you through three new ways to consume data depending on your use case and the compliance certifications we have started pursuing: SOC 2 and ISO 27001, on top of the GDPR and CCPA compliance already in place.
Your data comes fresh or free
In data enrichment, freshness is everything. A job title from six months ago, a company someone already left: outdated data does not just waste credits, it leads to wrong decisions. So we made a simple rule: if the data we return is older than 90 days, you do not pay for it. No exceptions, no fine print.
This is fresh or free. Every credit you spend now corresponds to data that has been recently verified and is actually worth acting on. Stale results won't cost you anything.
And when the data you need is not immediately available, you no longer have to wait. Reverse Contact V2 delivers it to you as soon as it is ready, straight to your app, through our new webhook-based delivery.
A new method that makes every request get an answer
With Reverse Contact V2, every API call returns a response. If the data is available, you get it in real time. If it needs to be refreshed, the result is delivered via webhook as soon as it is ready. You send a request, we take care of the rest.
We made this possible by taking full ownership of what happens after your call. Retries are managed entirely on our side. Jobs are queued even during temporary unavailability. Errors are absorbed internally so they never reach your end. No retry logic to build, no edge cases to handle, no calls left unanswered.
A fully redesigned interface for a better experience
Reverse Contact V2 is not just about new data and new delivery methods. The frontend has been entirely rebuilt for 2026: cleaner onboarding, faster time-to-value and webhook and job management directly from the dashboard, without going through the API. Users discovering Reverse Contact today get an experience built to get them to what matters, fast.
Real-time and asynchronous data from 3 data consumption methods

Not every team consumes data the same way. Some need an instant response inside a product flow. Others enrich millions of rows overnight. Others plug enrichment into event-driven pipelines where timing is unpredictable. V1 offered an API and CSV upload. That covered the basics, but it forced teams to adapt their workflows to our constraints instead of the other way around.
With Reverse Contact V2, we formalized three distinct delivery methods, each built for a different reality. The V1 API continues to work as before, and V2 adds new options on top.
API, from our Database with fresh or free data
Same inputs as before, same integration. You send an email, domain, URL or name and we return the matching profile straight from our database, continuously updated through regular batch refreshes to guarantee the freshest data possible. If the result is older than 90 days, you do not pay for it. This is the go-to option for real-time integrations inside your products, CRM and prospecting tools.
Webhooks, for asynchronous delivery with most up-to-date data
Submit a job, receive the result when it is ready. No polling, no retry logic to maintain. This is the right fit for ETL pipelines, event-driven architectures and high-volume background processing.
Dataset, for bulk delivery
Complete snapshots delivered directly to your environment (S3, GCP, Snowflake) in Parquet or JSON formats, with schema versioning and 'snapshot_date'. We built this for teams running data science, modeling, BI dashboards and enriching millions of rows in batch, without having to manage continuous API calls.
A simplified credit system
The credit system is evolving with V2. Until now, some operations could cost a fraction of a credit. Going forward, every operation costs a round number of credits. No more half credits, no more decimal values.
To make this possible, all credits currently held in your account and any credits purchased going forward will be multiplied by two. There is no change in value or purchasing power: you keep the exact same capacity. It is simply a rebalancing designed to give you better visibility on the credits you consume.
Stronger compliance for Reverse Data

As more teams integrated Reverse Contact into their core workflows, the questions changed. It was no longer just about data quality. Security teams wanted to know how we source, store and process data. Legal teams needed guarantees they could rely on during audits. Compliance went from a checkbox to a prerequisite.
The V1 was already GDPR and CCPA compliant, with no static database. But for V2, we wanted to go further. We rebuilt with compliance at the core: transparent sourcing, respect for data subject rights and a clear priority on accuracy over maximum coverage.
As part of this months-long rebuild, we also initiated the certification processes for SOC 2 and ISO 27001. The goal is simple: give security and compliance teams the certified guarantees they need to approve Reverse Contact without hesitation.
A product shaped by its users
Reverse Contact V2 is not a rebrand or a minor update. It is the result of thousands of conversations with the teams who use Reverse Contact every day. Every feature described in this article exists because someone asked for it, tested it and pushed us to make it better. The product we are shipping today was shaped by the people who rely on it. That is how we intend to keep building.
What this means for you
If you use Reverse Contact today, your existing integrations (API, CRM, Zapier, Make) keep working exactly as before. But you gain:
- More flexible input types (domain, URL, name in addition to email
- Webhook and dataset delivery for your most demanding pipelines
- A confidence score on every resolution to control your fallback logic
- Change detection to trigger automations on real signals
- SOC 2 and ISO 27001 certifications in progress, for soon-to-be certified reliability


