Lusha replaces its contact recommendations endpoint with Lookalikes V3

Lusha's February 26, 2026 changelog entry, v2.1.0, introduces Contact Lookalikes V3 at a new path and fully replaces the request and response schemas of the earlier contact recommendations endpoint. Results include name, social links, company, job title and location. The release also introduces signal rate control for the contacts and companies Signals API endpoints, capping the number of signal instances returned per type per entity from a start date. Lusha later made that parameter optional in v2.2.0 on March 10, 2026.

The details

• New endpoint: POST /v3/lookalike/contacts, replacing /api/recommendations/contacts.
• Seeds require 5 to 100 identifiers across LinkedIn URLs, emails, contact IDs and name plus company.
• Deduplication sessions persist for 30 days from last activity.
• The exclude parameter accepts up to 500 contacts.
• The change to the lookalikes endpoint is not backward compatible.

Context

Lusha's original Recommendations API from October 2025 offered contact and company recommendations; v2.1.0 retired the contact version. Company Lookalikes V3, using the same seed and deduplication pattern, followed on March 10, 2026. In October 2026, Lusha reused the Recommendations name for a separate API that ranks contacts and companies from Target Profiles, which ForgeX Research has covered.

Not disclosed

• Credit cost per lookalike result
• A deprecation timeline for customers still calling the old endpoint
• How lookalike similarity is calculated