[{"data":1,"prerenderedAt":110},["ShallowReactive",2],{"docs:rendered-article:\u002Fdocs\u002Fpublic\u002Fguides\u002Fjuly-2026-platform-update":3},{"path":4,"slug":5,"title":8,"description":9,"category":6,"categoryLabel":10,"order":11,"status":12,"family":13,"subfamily":13,"content":14,"html":15,"examplesHtml":16,"excerpt":17,"readTimeMinutes":18,"headings":19,"examplesHeadings":100,"lastUpdated":13,"endpointId":13,"requiredFlag":13,"relatedArticlePaths":101,"badge":107},"\u002Fdocs\u002Fguides\u002Fjuly-2026-platform-update",[6,7],"guides","july-2026-platform-update","Platform update for July 1, 2026","Important changes coming to the platform on July 1, 2026, including the retirement of legacy endpoints, the focus on V2, and the new synchronous Enrichment that returns a match in a single request. Read this to prepare your integration.","Guides",1,"new",null,"\n## A note before you read\n\nOver the past months, we've worked hard to keep our legacy endpoints (the original `\u002Fenrichment` API and `\u002Fv1\u002F`) running alongside our newer V2 platform. That dual life has reached its limit, and maintaining both is now hurting the reliability you depend on.\n\nWe'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.\n\n> [!NOTE]\n> This page describes the July 1 transition. The Contact Email Finder was reactivated after that transition as an opt-in V2 capability at `POST \u002Fv2\u002Fcontact\u002Femail`. It requires the `contact_email_finder` workspace feature flag, runs asynchronously, and delivers results by webhook.\n\n> [!IMPORTANT]\n> If your integration relies on a legacy `\u002Fenrichment` or `\u002Fv1\u002F` endpoint, or on Activities endpoints, please plan your migration before **July 1, 2026**. We strongly recommend starting now to avoid any disruption.\n\n## The short version\n\nThree things are happening on July 1, 2026:\n\n1. All **legacy `\u002Fenrichment` endpoints** (the original RC API) will be permanently shut down.\n2. All **V1 endpoints** will be permanently shut down.\n3. **Activities** endpoints will be discontinued, even those currently exposed under V2. They will not be replaced, on V2 or anywhere else.\n\nEverything else in our [V2 documentation](\u002Fdocs) 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.\n\n## Why we're focusing on V2\n\nRunning 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.\n\nFocusing 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.\n\nWe 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.\n\n## What's new: synchronous enrichment\n\nThis 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.\n\n> [!TIP]\n> **Enrich Profile** and **Enrich Company** return a complete match **synchronously**, right in the API response. One request in, one answer back. No job to start, no polling loop, no webhook endpoint to host.\n\nWhy teams are moving to it:\n\n- **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.\n- **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.\n- **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.\n- **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.\n\nIt really is this small:\n\n```bash\ncurl -X POST https:\u002F\u002Fapi.reversecontact.com\u002Fv2\u002Fenrich\u002Fpersons \\\n  -H \"Authorization: Bearer YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"email\": \"jane.doe@acme.com\"}'\n```\n\nThe profile comes back in the same response, ready to use.\n\n> [!NOTE]\n> This is **not** the legacy `\u002Fenrichment` API. The original `\u002Fenrichment` endpoint is one of the legacy generations being shut down on July 1, 2026. The new V2 Enrichment is a different, modern endpoint family living at `\u002Fv2\u002Fenrich\u002Fpersons` and `\u002Fv2\u002Fenrich\u002Fcompanies`. Same familiar name, much stronger foundation.\n\nStart here: [Enrich profile](\u002Fdocs\u002Fendpoints\u002Fenrich-person) and [Enrich company](\u002Fdocs\u002Fendpoints\u002Fenrich-company). If you're coming from asynchronous Resolve, they accept the same inputs and return the same result in a single synchronous request.\n\n## The timeline\n\n| When | What happens |\n| ---- | ------------ |\n| **Now** | V2 is the recommended path for every new and existing integration. Migration guides and V2 alternatives are ready in the docs. |\n| **Until July 1, 2026** | Legacy `\u002Fenrichment` and `\u002Fv1\u002F` endpoints remain accessible. They may behave unevenly during this transition, so please plan your migration as early as possible. |\n| **July 1, 2026** | All legacy endpoints and Activities are permanently shut down. |\n| **August 13, 2026** | The Contact Email Finder is available again for opted-in workspaces. |\n\n> [!WARNING]\n> Legacy `\u002Fenrichment` and `\u002Fv1\u002F` endpoints may remain unstable during the transition window. They will not receive new fixes or improvements. Treat them as best-effort until shutdown, and prioritize moving critical workloads to V2.\n\n## What is being shut down\n\nThese are the endpoints affected on July 1, 2026:\n\n### Legacy generations\n\n- Every endpoint under `\u002Fenrichment...` (the original RC API)\n- Every endpoint under `\u002Fv1\u002F...`\n\n### Activities endpoints (under V2)\n\n- `POST \u002Fv2\u002Ffetch\u002Fpersons\u002Fposts\u002Flive`\n- `POST \u002Fv2\u002Ffetch\u002Fpersons\u002Fcomments\u002Flive`\n- `POST \u002Fv2\u002Ffetch\u002Fpersons\u002Freactions\u002Flive`\n- `POST \u002Fv2\u002Ffetch\u002Fcompanies\u002Fposts\u002Flive`\n- `POST \u002Fv2\u002Ffetch\u002Fpost\u002Flive`\n- `POST \u002Fv2\u002Ffetch\u002Fposts\u002Fcomments\u002Flive`\n\n### Contact Email Finder status\n\nThe Contact Email Finder is available at `POST \u002Fv2\u002Fcontact\u002Femail` 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.\n\n## What stays\n\nEverything visible in the current [V2 documentation](\u002Fdocs) sidebar stays. That includes:\n\n- Person and company **Enrichment** endpoints, the new synchronous way to resolve an identity in a single request.\n- Person and company **Fetch** endpoints, sync and live.\n- Person and company **Resolve** endpoints, still fully supported if you prefer the asynchronous flow.\n- Person and company **Search** endpoints.\n- The **Contact Email Finder**, when enabled for the workspace, for asynchronous email discovery by webhook.\n- Free **Check** endpoints for freshness and existence.\n- Usage, quotas, webhooks, and dashboard tooling.\n\nV2 is our long-term supported infrastructure.\n\n## Your migration plan\n\nYou don't need to rewrite everything at once. Here's a step by step path that works well in practice.\n\n### 1. Map your traffic\n\nOpen the [Logs page](\u002Flogs) 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.\n\n### 2. Generate a V2 API key\n\nCreate a new key (with the `rc_` prefix) from the [API Keys page](\u002Fapi-keys). Your existing legacy keys keep working until shutdown, so you can run both side by side during the transition.\n\n### 3. Switch endpoint by endpoint\n\nV2 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](\u002Fdocs\u002Fguides\u002Fmigrating-v1-to-v2#endpoint-mapping).\n\n### 4. Update your response parsing\n\nV2 standardizes data under `response.data`, errors under `response.error`, and quotas under `response.quotas`. The [Migration Guide](\u002Fdocs\u002Fguides\u002Fmigrating-v1-to-v2#response-format) shows side by side examples for every field.\n\n### 5. Validate, then cut over\n\nRun 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.\n\n## If you rely on Activities\n\nWe 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.\n\nIf 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:\n\n1. **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.\n2. **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.\n\nYou can contact us from the [Support page](\u002Fsupport) inside your dashboard. Mention that your request is about the July 2026 update so it reaches the right team.\n\n## Frequently asked questions\n\n### Do my legacy API keys stop working today?\n\nNo. Your legacy keys remain valid until July 1, 2026. After that date, calls to `\u002Fenrichment` and `\u002Fv1\u002F` 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.\n\n### Wait, isn't `\u002Fenrichment` being shut down? How can Enrichment be new?\n\nBoth are true, because these are two different things that happen to share a name. The legacy `\u002Fenrichment` API (one of the original generations) is being retired on July 1, 2026. The new V2 **Enrichment** is a separate, modern endpoint family at `\u002Fv2\u002Fenrich\u002Fpersons` and `\u002Fv2\u002Fenrich\u002Fcompanies`, and it is here to stay. If you're on legacy `\u002Fenrichment` today, moving to V2 Enrichment is the natural next step.\n\n### Will V2 credits be the same as V1 credits?\n\nYour 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](\u002Fdocs\u002Fguides\u002Frate-limits-credits) for the full breakdown per endpoint.\n\n### Can I migrate gradually?\n\nYes. 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.\n\n### What if I can't finish migrating by July 1, 2026?\n\nPlease 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](\u002Fsupport).\n\n### Where do I find the V2 equivalent of an endpoint I'm using today?\n\nThe full mapping is in the [Migration Guide](\u002Fdocs\u002Fguides\u002Fmigrating-v1-to-v2#endpoint-mapping). If your endpoint isn't listed, please contact us so we can confirm the best V2 path for your use case.\n\n### Will Activities get a replacement?\n\nNo. 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](\u002Fsupport) and we'll help you find the best path forward.\n\n## A final word\n\nWe 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.\n\nThe 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.\n\nIf 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](\u002Fsupport) at any time.\n","\u003Ch2 id=\"a-note-before-you-read\">A note before you read\u003C\u002Fh2>\n\u003Cp>Over the past months, we’ve worked hard to keep our legacy endpoints (the original \u003Ccode>\u002Fenrichment\u003C\u002Fcode> API and \u003Ccode>\u002Fv1\u002F\u003C\u002Fcode>) running alongside our newer V2 platform. That dual life has reached its limit, and maintaining both is now hurting the reliability you depend on.\u003C\u002Fp>\n\u003Cp>We’ve made the decision to focus the platform on a single, modern foundation: \u003Cstrong>V2\u003C\u002Fstrong>. This guide explains what’s changing on July 1, 2026, why we’re doing it, and how to prepare.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cp class=\"markdown-alert-title\">\u003Csvg class=\"octicon octicon-info mr-2\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\">\u003Cpath d=\"M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z\">\u003C\u002Fpath>\u003C\u002Fsvg>Note\u003C\u002Fp>\u003Cp>This page describes the July 1 transition. The Contact Email Finder was reactivated after that transition as an opt-in V2 capability at \u003Ccode>POST \u002Fv2\u002Fcontact\u002Femail\u003C\u002Fcode>. It requires the \u003Ccode>contact_email_finder\u003C\u002Fcode> workspace feature flag, runs asynchronously, and delivers results by webhook.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Cdiv class=\"markdown-alert markdown-alert-important\">\u003Cp class=\"markdown-alert-title\">\u003Csvg class=\"octicon octicon-report mr-2\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\">\u003Cpath d=\"M0 1.75C0 .784.784 0 1.75 0h12.5C15.216 0 16 .784 16 1.75v9.5A1.75 1.75 0 0 1 14.25 13H8.06l-2.573 2.573A1.458 1.458 0 0 1 3 14.543V13H1.75A1.75 1.75 0 0 1 0 11.25Zm1.75-.25a.25.25 0 0 0-.25.25v9.5c0 .138.112.25.25.25h2a.75.75 0 0 1 .75.75v2.19l2.72-2.72a.749.749 0 0 1 .53-.22h6.5a.25.25 0 0 0 .25-.25v-9.5a.25.25 0 0 0-.25-.25Zm7 2.25v2.5a.75.75 0 0 1-1.5 0v-2.5a.75.75 0 0 1 1.5 0ZM9 9a1 1 0 1 1-2 0 1 1 0 0 1 2 0Z\">\u003C\u002Fpath>\u003C\u002Fsvg>Important\u003C\u002Fp>\u003Cp>If your integration relies on a legacy \u003Ccode>\u002Fenrichment\u003C\u002Fcode> or \u003Ccode>\u002Fv1\u002F\u003C\u002Fcode> endpoint, or on Activities endpoints, please plan your migration before \u003Cstrong>July 1, 2026\u003C\u002Fstrong>. We strongly recommend starting now to avoid any disruption.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"the-short-version\">The short version\u003C\u002Fh2>\n\u003Cp>Three things are happening on July 1, 2026:\u003C\u002Fp>\n\u003Col>\n\u003Cli>All \u003Cstrong>legacy \u003Ccode>\u002Fenrichment\u003C\u002Fcode> endpoints\u003C\u002Fstrong> (the original RC API) will be permanently shut down.\u003C\u002Fli>\n\u003Cli>All \u003Cstrong>V1 endpoints\u003C\u002Fstrong> will be permanently shut down.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Activities\u003C\u002Fstrong> endpoints will be discontinued, even those currently exposed under V2. They will not be replaced, on V2 or anywhere else.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Everything else in our \u003Ca href=\"\u002Fdocs\">V2 documentation\u003C\u002Fa> is here to stay and remains our long-term supported infrastructure. And it isn’t all removals: V2 now ships a new \u003Cstrong>synchronous Enrichment\u003C\u002Fstrong> that returns a match in a single request, with no polling and no webhooks. More on that just below.\u003C\u002Fp>\n\u003Ch2 id=\"why-were-focusing-on-v2\">Why we’re focusing on V2\u003C\u002Fh2>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>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: \u003Cstrong>B2B identity resolution\u003C\u002Fstrong>. 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.\u003C\u002Fp>\n\u003Ch2 id=\"whats-new-synchronous-enrichment\">What’s new: synchronous enrichment\u003C\u002Fh2>\n\u003Cp>This update isn’t only about retiring old surfaces. The headline addition in V2 is \u003Cstrong>Enrichment\u003C\u002Fstrong>, the simplest way we’ve ever shipped to turn the details you already have into a full profile or company record.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-tip\">\u003Cp class=\"markdown-alert-title\">\u003Csvg class=\"octicon octicon-light-bulb mr-2\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\">\u003Cpath d=\"M8 1.5c-2.363 0-4 1.69-4 3.75 0 .984.424 1.625.984 2.304l.214.253c.223.264.47.556.673.848.284.411.537.896.621 1.49a.75.75 0 0 1-1.484.211c-.04-.282-.163-.547-.37-.847a8.456 8.456 0 0 0-.542-.68c-.084-.1-.173-.205-.268-.32C3.201 7.75 2.5 6.766 2.5 5.25 2.5 2.31 4.863 0 8 0s5.5 2.31 5.5 5.25c0 1.516-.701 2.5-1.328 3.259-.095.115-.184.22-.268.319-.207.245-.383.453-.541.681-.208.3-.33.565-.37.847a.751.751 0 0 1-1.485-.212c.084-.593.337-1.078.621-1.489.203-.292.45-.584.673-.848.075-.088.147-.173.213-.253.561-.679.985-1.32.985-2.304 0-2.06-1.637-3.75-4-3.75ZM5.75 12h4.5a.75.75 0 0 1 0 1.5h-4.5a.75.75 0 0 1 0-1.5ZM6 15.25a.75.75 0 0 1 .75-.75h2.5a.75.75 0 0 1 0 1.5h-2.5a.75.75 0 0 1-.75-.75Z\">\u003C\u002Fpath>\u003C\u002Fsvg>Tip\u003C\u002Fp>\u003Cp>\u003Cstrong>Enrich Profile\u003C\u002Fstrong> and \u003Cstrong>Enrich Company\u003C\u002Fstrong> return a complete match \u003Cstrong>synchronously\u003C\u002Fstrong>, right in the API response. One request in, one answer back. No job to start, no polling loop, no webhook endpoint to host.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Cp>Why teams are moving to it:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>One request, one response.\u003C\u002Fstrong> Send what you have (an email, a name, a company domain) and read the match straight from \u003Ccode>response.data\u003C\u002Fcode>. Nothing to wait on.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Any input works.\u003C\u002Fstrong> 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.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Far less to build.\u003C\u002Fstrong> If you resolve identities asynchronously today, you can drop the callback infrastructure entirely and delete a whole class of edge cases.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Same credits, same price.\u003C\u002Fstrong> Enrichment costs \u003Cstrong>2 credits\u003C\u002Fstrong>, billed \u003Cstrong>only when a match is found\u003C\u002Fstrong>. A not-found response (\u003Ccode>404\u003C\u002Fcode>) is free, and it draws from the same workspace credits as the rest of V2.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>It really is this small:\u003C\u002Fp>\n\u003Cpre class=\"shiki shiki-themes github-light github-dark\" style=\"--shiki-light:#24292e;--shiki-dark:#e1e4e8;--shiki-light-bg:#fff;--shiki-dark-bg:#24292e\" tabindex=\"0\" data-language=\"bash\">\u003Ccode class=\"language-bash\">\u003Cspan class=\"line\">\u003Cspan style=\"--shiki-light:#6F42C1;--shiki-dark:#B392F0\">curl\u003C\u002Fspan>\u003Cspan style=\"--shiki-light:#005CC5;--shiki-dark:#79B8FF\"> -X\u003C\u002Fspan>\u003Cspan style=\"--shiki-light:#032F62;--shiki-dark:#9ECBFF\"> POST\u003C\u002Fspan>\u003Cspan style=\"--shiki-light:#032F62;--shiki-dark:#9ECBFF\"> https:\u002F\u002Fapi.reversecontact.com\u002Fv2\u002Fenrich\u002Fpersons\u003C\u002Fspan>\u003Cspan style=\"--shiki-light:#005CC5;--shiki-dark:#79B8FF\"> \\\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"--shiki-light:#005CC5;--shiki-dark:#79B8FF\">  -H\u003C\u002Fspan>\u003Cspan style=\"--shiki-light:#032F62;--shiki-dark:#9ECBFF\"> \"Authorization: Bearer YOUR_API_KEY\"\u003C\u002Fspan>\u003Cspan style=\"--shiki-light:#005CC5;--shiki-dark:#79B8FF\"> \\\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"--shiki-light:#005CC5;--shiki-dark:#79B8FF\">  -H\u003C\u002Fspan>\u003Cspan style=\"--shiki-light:#032F62;--shiki-dark:#9ECBFF\"> \"Content-Type: application\u002Fjson\"\u003C\u002Fspan>\u003Cspan style=\"--shiki-light:#005CC5;--shiki-dark:#79B8FF\"> \\\u003C\u002Fspan>\u003C\u002Fspan>\n\u003Cspan class=\"line\">\u003Cspan style=\"--shiki-light:#005CC5;--shiki-dark:#79B8FF\">  -d\u003C\u002Fspan>\u003Cspan style=\"--shiki-light:#032F62;--shiki-dark:#9ECBFF\"> '{\"email\": \"jane.doe@acme.com\"}'\u003C\u002Fspan>\u003C\u002Fspan>\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The profile comes back in the same response, ready to use.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cp class=\"markdown-alert-title\">\u003Csvg class=\"octicon octicon-info mr-2\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\">\u003Cpath d=\"M0 8a8 8 0 1 1 16 0A8 8 0 0 1 0 8Zm8-6.5a6.5 6.5 0 1 0 0 13 6.5 6.5 0 0 0 0-13ZM6.5 7.75A.75.75 0 0 1 7.25 7h1a.75.75 0 0 1 .75.75v2.75h.25a.75.75 0 0 1 0 1.5h-2a.75.75 0 0 1 0-1.5h.25v-2h-.25a.75.75 0 0 1-.75-.75ZM8 6a1 1 0 1 1 0-2 1 1 0 0 1 0 2Z\">\u003C\u002Fpath>\u003C\u002Fsvg>Note\u003C\u002Fp>\u003Cp>This is \u003Cstrong>not\u003C\u002Fstrong> the legacy \u003Ccode>\u002Fenrichment\u003C\u002Fcode> API. The original \u003Ccode>\u002Fenrichment\u003C\u002Fcode> endpoint is one of the legacy generations being shut down on July 1, 2026. The new V2 Enrichment is a different, modern endpoint family living at \u003Ccode>\u002Fv2\u002Fenrich\u002Fpersons\u003C\u002Fcode> and \u003Ccode>\u002Fv2\u002Fenrich\u002Fcompanies\u003C\u002Fcode>. Same familiar name, much stronger foundation.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Cp>Start here: \u003Ca href=\"\u002Fdocs\u002Fendpoints\u002Fenrich-person\">Enrich profile\u003C\u002Fa> and \u003Ca href=\"\u002Fdocs\u002Fendpoints\u002Fenrich-company\">Enrich company\u003C\u002Fa>. If you’re coming from asynchronous Resolve, they accept the same inputs and return the same result in a single synchronous request.\u003C\u002Fp>\n\u003Ch2 id=\"the-timeline\">The timeline\u003C\u002Fh2>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>When\u003C\u002Fth>\n\u003Cth>What happens\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Now\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>V2 is the recommended path for every new and existing integration. Migration guides and V2 alternatives are ready in the docs.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Until July 1, 2026\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Legacy \u003Ccode>\u002Fenrichment\u003C\u002Fcode> and \u003Ccode>\u002Fv1\u002F\u003C\u002Fcode> endpoints remain accessible. They may behave unevenly during this transition, so please plan your migration as early as possible.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>July 1, 2026\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>All legacy endpoints and Activities are permanently shut down.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>August 13, 2026\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>The Contact Email Finder is available again for opted-in workspaces.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003Cdiv class=\"markdown-alert markdown-alert-warning\">\u003Cp class=\"markdown-alert-title\">\u003Csvg class=\"octicon octicon-alert mr-2\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\">\u003Cpath d=\"M6.457 1.047c.659-1.234 2.427-1.234 3.086 0l6.082 11.378A1.75 1.75 0 0 1 14.082 15H1.918a1.75 1.75 0 0 1-1.543-2.575Zm1.763.707a.25.25 0 0 0-.44 0L1.698 13.132a.25.25 0 0 0 .22.368h12.164a.25.25 0 0 0 .22-.368Zm.53 3.996v2.5a.75.75 0 0 1-1.5 0v-2.5a.75.75 0 0 1 1.5 0ZM9 11a1 1 0 1 1-2 0 1 1 0 0 1 2 0Z\">\u003C\u002Fpath>\u003C\u002Fsvg>Warning\u003C\u002Fp>\u003Cp>Legacy \u003Ccode>\u002Fenrichment\u003C\u002Fcode> and \u003Ccode>\u002Fv1\u002F\u003C\u002Fcode> endpoints may remain unstable during the transition window. They will not receive new fixes or improvements. Treat them as best-effort until shutdown, and prioritize moving critical workloads to V2.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"what-is-being-shut-down\">What is being shut down\u003C\u002Fh2>\n\u003Cp>These are the endpoints affected on July 1, 2026:\u003C\u002Fp>\n\u003Ch3 id=\"legacy-generations\">Legacy generations\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Every endpoint under \u003Ccode>\u002Fenrichment...\u003C\u002Fcode> (the original RC API)\u003C\u002Fli>\n\u003Cli>Every endpoint under \u003Ccode>\u002Fv1\u002F...\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3 id=\"activities-endpoints-under-v2\">Activities endpoints (under V2)\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ccode>POST \u002Fv2\u002Ffetch\u002Fpersons\u002Fposts\u002Flive\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>POST \u002Fv2\u002Ffetch\u002Fpersons\u002Fcomments\u002Flive\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>POST \u002Fv2\u002Ffetch\u002Fpersons\u002Freactions\u002Flive\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>POST \u002Fv2\u002Ffetch\u002Fcompanies\u002Fposts\u002Flive\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>POST \u002Fv2\u002Ffetch\u002Fpost\u002Flive\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>POST \u002Fv2\u002Ffetch\u002Fposts\u002Fcomments\u002Flive\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3 id=\"contact-email-finder-status\">Contact Email Finder status\u003C\u002Fh3>\n\u003Cp>The Contact Email Finder is available at \u003Ccode>POST \u002Fv2\u002Fcontact\u002Femail\u003C\u002Fcode> for workspaces with the \u003Ccode>contact_email_finder\u003C\u002Fcode> 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.\u003C\u002Fp>\n\u003Ch2 id=\"what-stays\">What stays\u003C\u002Fh2>\n\u003Cp>Everything visible in the current \u003Ca href=\"\u002Fdocs\">V2 documentation\u003C\u002Fa> sidebar stays. That includes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Person and company \u003Cstrong>Enrichment\u003C\u002Fstrong> endpoints, the new synchronous way to resolve an identity in a single request.\u003C\u002Fli>\n\u003Cli>Person and company \u003Cstrong>Fetch\u003C\u002Fstrong> endpoints, sync and live.\u003C\u002Fli>\n\u003Cli>Person and company \u003Cstrong>Resolve\u003C\u002Fstrong> endpoints, still fully supported if you prefer the asynchronous flow.\u003C\u002Fli>\n\u003Cli>Person and company \u003Cstrong>Search\u003C\u002Fstrong> endpoints.\u003C\u002Fli>\n\u003Cli>The \u003Cstrong>Contact Email Finder\u003C\u002Fstrong>, when enabled for the workspace, for asynchronous email discovery by webhook.\u003C\u002Fli>\n\u003Cli>Free \u003Cstrong>Check\u003C\u002Fstrong> endpoints for freshness and existence.\u003C\u002Fli>\n\u003Cli>Usage, quotas, webhooks, and dashboard tooling.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>V2 is our long-term supported infrastructure.\u003C\u002Fp>\n\u003Ch2 id=\"your-migration-plan\">Your migration plan\u003C\u002Fh2>\n\u003Cp>You don’t need to rewrite everything at once. Here’s a step by step path that works well in practice.\u003C\u002Fp>\n\u003Ch3 id=\"1-map-your-traffic\">1. Map your traffic\u003C\u002Fh3>\n\u003Cp>Open the \u003Ca href=\"\u002Flogs\" target=\"_blank\" rel=\"noopener\">Logs page\u003C\u002Fa> 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.\u003C\u002Fp>\n\u003Ch3 id=\"2-generate-a-v2-api-key\">2. Generate a V2 API key\u003C\u002Fh3>\n\u003Cp>Create a new key (with the \u003Ccode>rc_\u003C\u002Fcode> prefix) from the \u003Ca href=\"\u002Fapi-keys\" target=\"_blank\" rel=\"noopener\">API Keys page\u003C\u002Fa>. Your existing legacy keys keep working until shutdown, so you can run both side by side during the transition.\u003C\u002Fp>\n\u003Ch3 id=\"3-switch-endpoint-by-endpoint\">3. Switch endpoint by endpoint\u003C\u002Fh3>\n\u003Cp>V2 uses standard Bearer authentication, JSON request bodies, and a consistent response envelope. The full mapping (V1 to V2) is already documented in the \u003Ca href=\"\u002Fdocs\u002Fguides\u002Fmigrating-v1-to-v2#endpoint-mapping\" target=\"_blank\" rel=\"noopener\">Migration Guide\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3 id=\"4-update-your-response-parsing\">4. Update your response parsing\u003C\u002Fh3>\n\u003Cp>V2 standardizes data under \u003Ccode>response.data\u003C\u002Fcode>, errors under \u003Ccode>response.error\u003C\u002Fcode>, and quotas under \u003Ccode>response.quotas\u003C\u002Fcode>. The \u003Ca href=\"\u002Fdocs\u002Fguides\u002Fmigrating-v1-to-v2#response-format\" target=\"_blank\" rel=\"noopener\">Migration Guide\u003C\u002Fa> shows side by side examples for every field.\u003C\u002Fp>\n\u003Ch3 id=\"5-validate-then-cut-over\">5. Validate, then cut over\u003C\u002Fh3>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch2 id=\"if-you-rely-on-activities\">If you rely on Activities\u003C\u002Fh2>\n\u003Cp>We understand this is the harder part of this update, and we want to be fully transparent: there will be \u003Cstrong>no replacement\u003C\u002Fstrong> 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.\u003C\u002Fp>\n\u003Cp>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:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\u003Cstrong>Discuss alternatives.\u003C\u002Fstrong> 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.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Plan the timing.\u003C\u002Fstrong> 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.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>You can contact us from the \u003Ca href=\"\u002Fsupport\" target=\"_blank\" rel=\"noopener\">Support page\u003C\u002Fa> inside your dashboard. Mention that your request is about the July 2026 update so it reaches the right team.\u003C\u002Fp>\n\u003Ch2 id=\"frequently-asked-questions\">Frequently asked questions\u003C\u002Fh2>\n\u003Ch3 id=\"do-my-legacy-api-keys-stop-working-today\">Do my legacy API keys stop working today?\u003C\u002Fh3>\n\u003Cp>No. Your legacy keys remain valid until July 1, 2026. After that date, calls to \u003Ccode>\u002Fenrichment\u003C\u002Fcode> and \u003Ccode>\u002Fv1\u002F\u003C\u002Fcode> 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.\u003C\u002Fp>\n\u003Ch3 id=\"wait-isnt-enrichment-being-shut-down-how-can-enrichment-be-new\">Wait, isn’t \u003Ccode>\u002Fenrichment\u003C\u002Fcode> being shut down? How can Enrichment be new?\u003C\u002Fh3>\n\u003Cp>Both are true, because these are two different things that happen to share a name. The legacy \u003Ccode>\u002Fenrichment\u003C\u002Fcode> API (one of the original generations) is being retired on July 1, 2026. The new V2 \u003Cstrong>Enrichment\u003C\u002Fstrong> is a separate, modern endpoint family at \u003Ccode>\u002Fv2\u002Fenrich\u002Fpersons\u003C\u002Fcode> and \u003Ccode>\u002Fv2\u002Fenrich\u002Fcompanies\u003C\u002Fcode>, and it is here to stay. If you’re on legacy \u003Ccode>\u002Fenrichment\u003C\u002Fcode> today, moving to V2 Enrichment is the natural next step.\u003C\u002Fp>\n\u003Ch3 id=\"will-v2-credits-be-the-same-as-v1-credits\">Will V2 credits be the same as V1 credits?\u003C\u002Fh3>\n\u003Cp>Your workspace credit balance is shared across V1 and V2 today, and that remains the case during the transition. V2 uses contextual pricing, see \u003Ca href=\"\u002Fdocs\u002Fguides\u002Frate-limits-credits\">Rate limits & credits\u003C\u002Fa> for the full breakdown per endpoint.\u003C\u002Fp>\n\u003Ch3 id=\"can-i-migrate-gradually\">Can I migrate gradually?\u003C\u002Fh3>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch3 id=\"what-if-i-cant-finish-migrating-by-july-1-2026\">What if I can’t finish migrating by July 1, 2026?\u003C\u002Fh3>\n\u003Cp>Please contact our team \u003Cstrong>before\u003C\u002Fstrong> 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 \u003Ca href=\"\u002Fsupport\" target=\"_blank\" rel=\"noopener\">Support page\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3 id=\"where-do-i-find-the-v2-equivalent-of-an-endpoint-im-using-today\">Where do I find the V2 equivalent of an endpoint I’m using today?\u003C\u002Fh3>\n\u003Cp>The full mapping is in the \u003Ca href=\"\u002Fdocs\u002Fguides\u002Fmigrating-v1-to-v2#endpoint-mapping\" target=\"_blank\" rel=\"noopener\">Migration Guide\u003C\u002Fa>. If your endpoint isn’t listed, please contact us so we can confirm the best V2 path for your use case.\u003C\u002Fp>\n\u003Ch3 id=\"will-activities-get-a-replacement\">Will Activities get a replacement?\u003C\u002Fh3>\n\u003Cp>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 \u003Ca href=\"\u002Fsupport\" target=\"_blank\" rel=\"noopener\">Support page\u003C\u002Fa> and we’ll help you find the best path forward.\u003C\u002Fp>\n\u003Ch2 id=\"a-final-word\">A final word\u003C\u002Fh2>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>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 \u003Ca href=\"\u002Fsupport\" target=\"_blank\" rel=\"noopener\">Support page\u003C\u002Fa> at any time.\u003C\u002Fp>\n","","A note before you read Over the past months, we've worked hard to keep our legacy endpoints (the original \u002Fenrichment API and \u002Fv1\u002F) running alongside our newer V2 platform. That...",9,[20,24,27,30,33,36,39,43,46,49,52,55,58,61,64,67,70,73,76,79,82,85,88,91,94,97],{"id":21,"title":22,"level":23},"a-note-before-you-read","A note before you read",2,{"id":25,"title":26,"level":23},"the-short-version","The short version",{"id":28,"title":29,"level":23},"why-were-focusing-on-v2","Why we're focusing on V2",{"id":31,"title":32,"level":23},"whats-new-synchronous-enrichment","What's new: synchronous enrichment",{"id":34,"title":35,"level":23},"the-timeline","The timeline",{"id":37,"title":38,"level":23},"what-is-being-shut-down","What is being shut down",{"id":40,"title":41,"level":42},"legacy-generations","Legacy generations",3,{"id":44,"title":45,"level":42},"activities-endpoints-under-v2","Activities endpoints (under V2)",{"id":47,"title":48,"level":42},"contact-email-finder-status","Contact Email Finder status",{"id":50,"title":51,"level":23},"what-stays","What stays",{"id":53,"title":54,"level":23},"your-migration-plan","Your migration plan",{"id":56,"title":57,"level":42},"1-map-your-traffic","1. Map your traffic",{"id":59,"title":60,"level":42},"2-generate-a-v2-api-key","2. Generate a V2 API key",{"id":62,"title":63,"level":42},"3-switch-endpoint-by-endpoint","3. Switch endpoint by endpoint",{"id":65,"title":66,"level":42},"4-update-your-response-parsing","4. Update your response parsing",{"id":68,"title":69,"level":42},"5-validate-then-cut-over","5. Validate, then cut over",{"id":71,"title":72,"level":23},"if-you-rely-on-activities","If you rely on Activities",{"id":74,"title":75,"level":23},"frequently-asked-questions","Frequently asked questions",{"id":77,"title":78,"level":42},"do-my-legacy-api-keys-stop-working-today","Do my legacy API keys stop working today?",{"id":80,"title":81,"level":42},"wait-isnt-enrichment-being-shut-down-how-can-enrichment-be-new","Wait, isn't `\u002Fenrichment` being shut down? How can Enrichment be new?",{"id":83,"title":84,"level":42},"will-v2-credits-be-the-same-as-v1-credits","Will V2 credits be the same as V1 credits?",{"id":86,"title":87,"level":42},"can-i-migrate-gradually","Can I migrate gradually?",{"id":89,"title":90,"level":42},"what-if-i-cant-finish-migrating-by-july-1-2026","What if I can't finish migrating by July 1, 2026?",{"id":92,"title":93,"level":42},"where-do-i-find-the-v2-equivalent-of-an-endpoint-im-using-today","Where do I find the V2 equivalent of an endpoint I'm using today?",{"id":95,"title":96,"level":42},"will-activities-get-a-replacement","Will Activities get a replacement?",{"id":98,"title":99,"level":23},"a-final-word","A final word",[],[102,103,104,105,106],"\u002Fdocs\u002Fendpoints\u002Fenrich-person","\u002Fdocs\u002Fguides\u002Fmigrating-v1-to-v2","\u002Fdocs\u002Fguides\u002Fwhich-endpoint-should-i-use","\u002Fdocs\u002Fguides\u002Fproduction-checklist","\u002Fdocs\u002Fauthentication",{"label":108,"color":109},"Important","warning",1787151086726]