id values around.
This is a single endpoint for one contact or a hundred. Send an array of 1 to 100 contacts in one call.
When to use this instead of the two-step flow
Use Search and Enrich Contacts when you already trust your match criteria and want the full record in one round trip - for example, syncing a CRM import where every row already has an email or LinkedIn URL you’re confident in. Use the two-step Search → Enrich flow instead when you want to inspectcanReveal and its credit cost before spending credits - for example, when a rep reviews a match before you enrich it.
Identifiers you can search by
Provide one of the following for each contact:- Lusha contact
id linkedinUrlemailfirstNameandlastNameand (companyNameorcompanyDomain)
Controlling what gets revealed
Use thereveal field to control what gets unlocked for each matched contact:
emails- work and personal email addressesphones- mobile and direct phone numbers
reveal entirely to get both by default.
If a contact can’t be found or enriched, its result contains an error with a code of NOT_FOUND, COMPLIANCE_RESTRICTED, or ENRICH_FAILED instead of profile data.
Billing
Two charges apply per successful contact: one for the search, via theapi_search action, and one per revealed field (email or phone), via per-datapoint pricing.
Related
- Search Contacts and Enrich Contacts - the two-step equivalent, useful when you want to review matches before revealing.