Skip to main content
POST
/
leads
/
{leadId}
/
enrich
Enrich Lead
curl --request POST \
  --url https://api.lemlist.com/api/leads/{leadId}/enrich \
  --header 'Authorization: Basic <encoded-value>'
{ "id": "enr_Ohbs0mEsWmDjTnxTi" }
You can enrich a leadwith additional data.
Check enrich data for details on the enrichment result structure.

Authorizations

Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Path Parameters

leadId
string
required

Unique lead ID

Query Parameters

findEmail
boolean

Search email address in another campaign

verifyEmail
boolean

Find verified email

linkedinEnrichment
boolean

Run LinkedIn enrichment

findPhone
boolean

Find phone number

webhookUrl
string

Webhook URL for enrichment events

force
boolean

Re-run an enrichment that would otherwise be skipped. Bypasses skips caused by data already present on the contact: existing email, existing phone, LinkedIn enrichment already done for the same linkedinUrl / linkedinUrlSalesNav, or email already having a deliverability status.

Does not bypass:

  • Enrichment currently in progress — if another enrichment is already running for this contact, the request is still skipped (no parallel enrichments, no double billing).
  • Previously returned not-found — for findEmail and findPhone, if a prior enrichment with the same inputs (linkedinUrl, linkedinUrlSalesNav, first / last name, company name / domain / LinkedIn URL) already returned not-found, the request is still skipped. Changing any of those inputs on the lead lifts the block without needing force.

Response

Success

id
string

Enrichment ID