Lusha makes Data Waterfall contact enrichment asynchronous in API v2.17.0

Lusha released version 2.17.0 of its API on October 5, 2026, changing how its Data Waterfall feature returns contact enrichment results. According to the changelog, fast providers still answer inside the enrich call, while a slower provider no longer holds the request open. POST /v3/contacts/enrich can now return a job object, and a new GET /v3/contacts/jobs/{jobId} endpoint lets developers poll for the remaining data, merging returned contacts by ID. The job returns only the contacts it was still working on. Lusha also added waterfall status fields and provenance on each email and phone number.

The details

• Developers poll every retryAfter seconds while status is processing and stop on complete, expired or failed.
• Polling does not charge credits, and each data point is billed once by whichever call delivered it.
• Each email and phone carries a dataSource value of lusha or a provider ID, such as wiza.
• New status values include completed, partial, halted, OUT_OF_CREDITS and PARTIAL_OUT_OF_CREDITS, and missingDataPoints lists unresolved fields.
• POST /v3/contacts/search-and-enrich returns the new status and provenance fields but never a job.

Context

This is the third Lusha API update in our coverage on enrichment data delivery, after waterfall enrichment with third-party fallback in July 2026 and the Buying Group, Signal Score and Conversations APIs in September. A September 23 changelog entry made Data Waterfall available on all paid plans. Lusha followed this release with ICP Fit Score, intent topic and Recommendations APIs on October 20.

Not disclosed

• Per-provider credit rates for waterfall data
• Job expiry duration
• Full list of third-party waterfall providers