[{"data":1,"prerenderedAt":40},["ShallowReactive",2],{"docs:rendered-article:\u002Fdocs\u002Fpublic\u002Fguides\u002Fendpoint-transition-october-2026":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":29,"lastUpdated":13,"endpointId":13,"requiredFlag":13,"relatedArticlePaths":30,"badge":37},"\u002Fdocs\u002Fguides\u002Fendpoint-transition-october-2026",[6,7],"guides","endpoint-transition-october-2026","Endpoint transition on October 13, 2026","\u002Fv2\u002Fsearch\u002Fpersons is succeeded by \u002Fv2\u002Fsearch\u002Fpeople, and \u002Fv2\u002Fresolve by \u002Fv2\u002Fenrich. Both old endpoints stay live until October 13, 2026.","Guides",1,"new",null,"\nWe're replacing two of the endpoints your integration might use.\n\n`\u002Fv2\u002Fsearch\u002Fpersons` is succeeded by `\u002Fv2\u002Fsearch\u002Fpeople`, and `\u002Fv2\u002Fresolve\u002F` is succeeded by `\u002Fv2\u002Fenrich\u002F`. Both old endpoints stay live until **October 13, 2026**, so nothing breaks on your side today.\n\n> [!IMPORTANT]\n> After October 13, 2026, calls to `\u002Fv2\u002Fsearch\u002Fpersons` and to the `\u002Fv2\u002Fresolve\u002F` endpoints will no longer be processed. Plan your migration before that date.\n\n## What changes on search\n\n- Search returns the full profile directly, so the separate fetch call after each search disappears.\n- Search with no result costs nothing.\n- A free endpoint, `\u002Fv2\u002Fsearch\u002Fpeople\u002Fcount`, tells you how many matches a query has before you spend anything.\n- Billing moves from per page to per profile delivered, and you control how many profiles come back with `perPage`, from 1 to 100. One profile returned costs 1 credit.\n- Pagination moves to a cursor, there's no page number anymore.\n\nStep by step: [Migrating people search from persons to people](\u002Fdocs\u002Fguides\u002Fmigrating-search-persons-to-people).\n\n## What changes on resolve\n\n- `\u002Fv2\u002Fresolve\u002F` is succeeded by `\u002Fv2\u002Fenrich\u002F`. Same input, same cost, 2 credits, only when a profile is found.\n- Enrich answers synchronously, faster end to end than the current webhook round trip, so you can retire the callback endpoint you maintain on your side for us.\n- You have one endpoint for persons and one for companies: `\u002Fv2\u002Fenrich\u002Fpersons` and `\u002Fv2\u002Fenrich\u002Fcompanies`.\n- Enrich returns the full profile for the same price, with no additional fetch needed: on the matched person, on every alternative candidate, and on companies.\n\nStep by step: [Migrating from Resolve to Enrich](\u002Fdocs\u002Fguides\u002Fmigrating-resolve-to-enrich).\n\n## Documentation for the new endpoints\n\n- [Search people](\u002Fdocs\u002Fendpoints\u002Fsearch-people)\n- [Search people count](\u002Fdocs\u002Fendpoints\u002Fsearch-people-count)\n- [Enrich profile](\u002Fdocs\u002Fendpoints\u002Fenrich-person)\n- [Enrich company](\u002Fdocs\u002Fendpoints\u002Fenrich-company)\n\nIf you have any questions, please contact [support@reversecontact.com](mailto:support@reversecontact.com).\n","\u003Cp>We’re replacing two of the endpoints your integration might use.\u003C\u002Fp>\n\u003Cp>\u003Ccode>\u002Fv2\u002Fsearch\u002Fpersons\u003C\u002Fcode> is succeeded by \u003Ccode>\u002Fv2\u002Fsearch\u002Fpeople\u003C\u002Fcode>, and \u003Ccode>\u002Fv2\u002Fresolve\u002F\u003C\u002Fcode> is succeeded by \u003Ccode>\u002Fv2\u002Fenrich\u002F\u003C\u002Fcode>. Both old endpoints stay live until \u003Cstrong>October 13, 2026\u003C\u002Fstrong>, so nothing breaks on your side today.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-important\">\u003Cp class=\"markdown-alert-title\">\u003Cspan class=\"iconify i-ph-warning-circle docs-icon docs-markdown-icon\" aria-hidden=\"true\">\u003C\u002Fspan>Important\u003C\u002Fp>\u003Cp>After October 13, 2026, calls to \u003Ccode>\u002Fv2\u002Fsearch\u002Fpersons\u003C\u002Fcode> and to the \u003Ccode>\u002Fv2\u002Fresolve\u002F\u003C\u002Fcode> endpoints will no longer be processed. Plan your migration before that date.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"what-changes-on-search\">What changes on search\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Search returns the full profile directly, so the separate fetch call after each search disappears.\u003C\u002Fli>\n\u003Cli>Search with no result costs nothing.\u003C\u002Fli>\n\u003Cli>A free endpoint, \u003Ccode>\u002Fv2\u002Fsearch\u002Fpeople\u002Fcount\u003C\u002Fcode>, tells you how many matches a query has before you spend anything.\u003C\u002Fli>\n\u003Cli>Billing moves from per page to per profile delivered, and you control how many profiles come back with \u003Ccode>perPage\u003C\u002Fcode>, from 1 to 100. One profile returned costs 1 credit.\u003C\u002Fli>\n\u003Cli>Pagination moves to a cursor, there’s no page number anymore.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Step by step: \u003Ca href=\"\u002Fdocs\u002Fguides\u002Fmigrating-search-persons-to-people\">Migrating people search from persons to people\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"what-changes-on-resolve\">What changes on resolve\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ccode>\u002Fv2\u002Fresolve\u002F\u003C\u002Fcode> is succeeded by \u003Ccode>\u002Fv2\u002Fenrich\u002F\u003C\u002Fcode>. Same input, same cost, 2 credits, only when a profile is found.\u003C\u002Fli>\n\u003Cli>Enrich answers synchronously, faster end to end than the current webhook round trip, so you can retire the callback endpoint you maintain on your side for us.\u003C\u002Fli>\n\u003Cli>You have one endpoint for persons and one for companies: \u003Ccode>\u002Fv2\u002Fenrich\u002Fpersons\u003C\u002Fcode> and \u003Ccode>\u002Fv2\u002Fenrich\u002Fcompanies\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Enrich returns the full profile for the same price, with no additional fetch needed: on the matched person, on every alternative candidate, and on companies.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Step by step: \u003Ca href=\"\u002Fdocs\u002Fguides\u002Fmigrating-resolve-to-enrich\">Migrating from Resolve to Enrich\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"documentation-for-the-new-endpoints\">Documentation for the new endpoints\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"\u002Fdocs\u002Fendpoints\u002Fsearch-people\">Search people\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fdocs\u002Fendpoints\u002Fsearch-people-count\">Search people count\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fdocs\u002Fendpoints\u002Fenrich-person\">Enrich profile\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fdocs\u002Fendpoints\u002Fenrich-company\">Enrich company\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you have any questions, please contact \u003Ca href=\"mailto:support@reversecontact.com\">support@reversecontact.com\u003C\u002Fa>.\u003C\u002Fp>\n","","We're replacing two of the endpoints your integration might use. \u002Fv2\u002Fsearch\u002Fpersons is succeeded by \u002Fv2\u002Fsearch\u002Fpeople, and \u002Fv2\u002Fresolve\u002F is succeeded by \u002Fv2\u002Fenrich\u002F. Both old end...",2,[20,23,26],{"id":21,"title":22,"level":18},"what-changes-on-search","What changes on search",{"id":24,"title":25,"level":18},"what-changes-on-resolve","What changes on resolve",{"id":27,"title":28,"level":18},"documentation-for-the-new-endpoints","Documentation for the new endpoints",[],[31,32,33,34,35,36],"\u002Fdocs\u002Fguides\u002Fmigrating-search-persons-to-people","\u002Fdocs\u002Fguides\u002Fmigrating-resolve-to-enrich","\u002Fdocs\u002Fendpoints\u002Fsearch-people","\u002Fdocs\u002Fendpoints\u002Fsearch-people-count","\u002Fdocs\u002Fendpoints\u002Fenrich-person","\u002Fdocs\u002Fendpoints\u002Fenrich-company",{"label":38,"color":39},"Important","warning",1790692476877]