Change Log

Lusha's API release v2.17.0 made Data Waterfall enrichment asynchronous, so when a slower outside provider is still working, the enrich call returns what is known plus a job to check later. Every email and phone number now carries a field naming its source, Lusha or the outside provider, and responses add waterfall status fields and a list of missing data points.

Buyers can now see which provider supplied each email or number, which matters for data quality checks and for knowing whose terms cover the data. It builds on the waterfall that reached all paid plans in September.

Lusha moved Data Waterfall, which falls through to enabled third party providers when Lusha's own data has no email or phone match, from Pro plans and above to every paid plan. The change is packaging only: there is no API change and admins still turn it on per account under Account Settings, Waterfall.

Lower tier paid customers can now reach third party provider data for hard to match contacts without upgrading to Pro, which changes the plan math and means more records may come from sources other than Lusha's own database.

Lusha API release 2.14.0 adds column catalogs for contact and company tables and endpoints that add up to 10 columns per call. Adding a column starts asynchronous enrichment across every row, with each result reported separately, and the operations currently consume no credits. Release 2.15.0 followed on 17 September, adding Instagram, YouTube and TikTok URLs to company enrichment on all plans.

Teams can now define and enrich a table from code, which removes the manual setup at the start of a data workflow. The no credit pricing on these calls is described as current, so it is worth confirming before building volume on it.

Lusha released API version 2.13.0, introducing a dedicated Conversations tag for conversational intelligence. The update adds stricter validation, where a pageSize above 100 or an invalid date format now returns a 400 error, and it unifies the response for missing or still processing transcripts under a single 404.

Teams integrating Lusha's conversational intelligence need to update pagination and error handling, since requests that previously succeeded will now fail validation. The unified 404 also removes the ability to distinguish a transcript that does not exist from one that is still processing, so retry logic has to assume both.

Lusha released API version 2.12.0, adding a maxContactsPerCompany parameter to the Prospecting Contacts endpoint and a required maxResultsPerSignal parameter to the Signals API. The Contact Lookalikes endpoint moved to a v3 path with fully replaced request and response schemas that are not backwards compatible.

This is a breaking change. Any integration calling Contact Lookalikes has to be rewritten against the v3 schema, and calls to the Signals API now fail without the new required parameter. The per company cap is the useful addition, giving operations teams direct control over credit consumption during prospecting.