Skip to main content
Lusha aggregates data from publicly available sources and contributions from trusted business partners. Data is not created or directly managed by Lusha. For full details, see the Privacy Policy.
Lusha’s data catalog spans roughly 290 million contacts and 29 million companies, across around 98 verified contact and company fields - split between “Data Points” (static verified attributes, such as job title, industry, or revenue) and “Signals” (real-time events, such as hiring surges, role changes, or funding news).
Most Data Points refresh on a regular cadence (commonly weekly). Signal-driven fields - like a contact’s current job - update as soon as the underlying signal (a job change, a company change) is detected. The updateDate field on any record shows when it was last verified. Signal lookback defaults to 6 months, configurable via signalsStartDate (REST API) or startDate (MCP signals tools).
The API returns a 200 OK with an error object inside the contact payload (e.g., "name": "EMPTY_DATA", "message": "Could not find requested data"). No credit is charged for records with no match.
A partial profile is a contact record that exists in Lusha’s database but has incomplete data - still potentially useful as a prospect. How you opt in depends on the endpoint:
  • Single-contact enrichment endpoints use a partialProfile: true parameter.
  • The prospecting search-and-enrich endpoint uses includePartialContact: true in the request body.
Lusha applies GDPR compliance automatically. For contacts in the EU, data is returned subject to applicable regulations. Requests that cannot be fulfilled due to legal reasons return 451 Unavailable for Legal Reasons.
Phone numbers marked doNotCall: true are on the Do Not Call registry. The excludeDnc parameter (Scale plan) filters out contacts whose phone numbers are all DNC, so only contacts with at least one callable number appear in results.
Waterfall Reveal is an enhancement to Enrich Contacts. When Lusha’s own data has no match for a field, it falls through to your enabled third-party providers to try to fill the gap - extra reach on hard-to-match contacts, on top of standard enrichment.How it works:
  • If Data Waterfall is enabled on your account, with specific providers turned on under Account > Waterfall in the Lusha dashboard, the waterfall runs automatically on every Enrich Contacts call - you don’t need to pass anything to trigger it.
  • Pass waterfallEnabled: false to opt a specific call out.
  • reveal still controls which fields come back; waterfallEnabled only controls whether the fallback runs for this call at all.
  • Requires Data Waterfall enabled on your account - if it’s off, or no providers are enabled, waterfallEnabled has no effect either way.
  • Lusha determines the provider query order - it isn’t caller-configurable.
  • Use of Data Waterfall is subject to Lusha’s Supplementary Terms.