Platform update for July 1, 2026

A note before you read

Over the past months, we’ve worked hard to keep our legacy endpoints (the original /enrichment API and /v1/) running alongside our newer V2 platform. That dual life has reached its limit, and maintaining both is now hurting the reliability you depend on.

We’ve made the decision to focus the platform on a single, modern foundation: V2. This guide explains what’s changing on July 1, 2026, why we’re doing it, and how to prepare.

The short version

Three things are happening on July 1, 2026:

1. All legacy /enrichment endpoints (the original RC API) will be permanently shut down.
2. All V1 endpoints will be permanently shut down.
3. Activities endpoints will be discontinued, even those currently exposed under V2. They will not be replaced, on V2 or anywhere else.

Everything else in our V2 documentation is here to stay and remains our long-term supported infrastructure. And it isn’t all removals: V2 now ships a new synchronous Enrichment that returns a match in a single request, with no polling and no webhooks. More on that just below.

Why we’re focusing on V2

Running multiple generations of APIs at the same time has added complexity that touches every part of the platform: routing, caching, quotas, billing, monitoring, and support. Each layer carries assumptions from a different era, and reconciling them in real time has been a major source of instability.

Focusing fully on V2 lets us operate one consistent infrastructure end to end, which is what we need to give you the reliability you depend on.

We also looked honestly at our own scope. Spreading our attention across too many endpoint families slowed our ability to deliver the highest quality on what most customers actually rely on: B2B identity resolution. Activities remain outside that focus and were retired. Email Finder is now available again as a separately gated asynchronous capability for workspaces that need it.

What’s new: synchronous enrichment

This update isn’t only about retiring old surfaces. The headline addition in V2 is Enrichment, the simplest way we’ve ever shipped to turn the details you already have into a full profile or company record.

Why teams are moving to it:

• One request, one response. Send what you have (an email, a name, a company domain) and read the match straight from response.data. Nothing to wait on.
• Any input works. Every field is optional and independent, so an email on its own is enough to resolve a person. The more you provide, the more accurate the match.
• Far less to build. If you resolve identities asynchronously today, you can drop the callback infrastructure entirely and delete a whole class of edge cases.
• Same credits, same price. Enrichment costs 2 credits, billed only when a match is found. A not-found response (404) is free, and it draws from the same workspace credits as the rest of V2.

It really is this small:

curl -X POST https://api.reversecontact.com/v2/enrich/persons \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "[email protected]"}'

The profile comes back in the same response, ready to use.

Start here: Enrich profile and Enrich company. If you’re coming from asynchronous Resolve, they accept the same inputs and return the same result in a single synchronous request.

The timeline

What is being shut down

These are the endpoints affected on July 1, 2026:

Legacy generations

• Every endpoint under /enrichment... (the original RC API)
• Every endpoint under /v1/...

Activities endpoints (under V2)

• POST /v2/fetch/persons/posts/live
• POST /v2/fetch/persons/comments/live
• POST /v2/fetch/persons/reactions/live
• POST /v2/fetch/companies/posts/live
• POST /v2/fetch/post/live
• POST /v2/fetch/posts/comments/live

Contact Email Finder status

The Contact Email Finder is available at POST /v2/contact/email for workspaces with the contact_email_finder feature enabled. It accepts a LinkedIn profile URL or a person’s full name and company domain, and delivers the result asynchronously by webhook. The endpoint costs 3 credits only when an email is found.

What stays

Everything visible in the current V2 documentation sidebar stays. That includes:

• Person and company Enrichment endpoints, the new synchronous way to resolve an identity in a single request.
• Person and company Fetch endpoints, sync and live.
• Person and company Resolve endpoints, still fully supported if you prefer the asynchronous flow.
• Person and company Search endpoints.
• The Contact Email Finder, when enabled for the workspace, for asynchronous email discovery by webhook.
• Free Check endpoints for freshness and existence.
• Usage, quotas, webhooks, and dashboard tooling.

V2 is our long-term supported infrastructure.

Your migration plan

You don’t need to rewrite everything at once. Here’s a step by step path that works well in practice.

1. Map your traffic

Open the Logs page in your dashboard and look at which endpoints your integration is actually using. You may be surprised: in most accounts, a small number of endpoints carry the majority of the volume. Migrate those first.

2. Generate a V2 API key

Create a new key (with the rc_ prefix) from the API Keys page. Your existing legacy keys keep working until shutdown, so you can run both side by side during the transition.

3. Switch endpoint by endpoint

V2 uses standard Bearer authentication, JSON request bodies, and a consistent response envelope. The full mapping (V1 to V2) is already documented in the Migration Guide.

4. Update your response parsing

V2 standardizes data under response.data, errors under response.error, and quotas under response.quotas. The Migration Guide shows side by side examples for every field.

5. Validate, then cut over

Run your new V2 integration in parallel for a few days, compare results, and only then point production traffic to the V2 key. Once you’re confident, you can retire the legacy key entirely.

If you rely on Activities

We understand this is the harder part of this update, and we want to be fully transparent: there will be no replacement for Activities, neither on V2 nor anywhere else. Once these endpoints are shut down on July 1, 2026, the capability is retired for good, not moved to a new home. We’ve chosen to concentrate the platform on stable B2B identity resolution infrastructure.

If your workflow depends on Activities, please reach out to our team as early as possible. Depending on your use case, we can help you in two ways:

1. Discuss alternatives. Some workflows that use Activities today can be reshaped around our identity resolution endpoints. We’re happy to walk through your specific case with you.
2. Plan the timing. If you need more lead time to adapt your product, the earlier you tell us, the more we can do to make the transition smooth on your side.

You can contact us from the Support page inside your dashboard. Mention that your request is about the July 2026 update so it reaches the right team.

Frequently asked questions

Do my legacy API keys stop working today?

No. Your legacy keys remain valid until July 1, 2026. After that date, calls to /enrichment and /v1/ endpoints, and to the Activities routes listed above, will no longer be processed. The Contact Email Finder is a separate V2 capability available to opted-in workspaces.

Wait, isn’t /enrichment being shut down? How can Enrichment be new?

Both are true, because these are two different things that happen to share a name. The legacy /enrichment API (one of the original generations) is being retired on July 1, 2026. The new V2 Enrichment is a separate, modern endpoint family at /v2/enrich/persons and /v2/enrich/companies, and it is here to stay. If you’re on legacy /enrichment today, moving to V2 Enrichment is the natural next step.

Will V2 credits be the same as V1 credits?

Your workspace credit balance is shared across V1 and V2 today, and that remains the case during the transition. V2 uses contextual pricing, see Rate limits & credits for the full breakdown per endpoint.

Can I migrate gradually?

Yes. V1 and V2 coexist until July 1, 2026, so you can move endpoint by endpoint at your own pace. The earlier you start, the more time you have to validate each step in production.

What if I can’t finish migrating by July 1, 2026?

Please contact our team before July, not after. We’d rather hear about constraints early and help you plan, than discover blockers on the day of shutdown. Reach out from the Support page.

Where do I find the V2 equivalent of an endpoint I’m using today?

The full mapping is in the Migration Guide. If your endpoint isn’t listed, please contact us so we can confirm the best V2 path for your use case.

Will Activities get a replacement?

No. Activities (person and company posts, comments, and reactions) are retired with no replacement, on V2 or anywhere else. This is a deliberate choice to focus the platform on B2B identity resolution. If these endpoints are part of your workflow, contact us early from the Support page and we’ll help you find the best path forward.

A final word

We don’t take this decision lightly. We know that any migration costs your team time, and we appreciate the trust you place in us by going through it with us.

The reason is simple: we want the platform you rely on to be the most stable, predictable, and accurate B2B identity resolution infrastructure available. Focusing on V2 is how we get there.

If anything in this update is unclear, or if you’d like guidance on your specific integration, our team is here to help. Reach out from the Support page at any time.