Enrich existing leads, spending credits to research them.
Each type is a separate piece of research, and each costs credits per lead. Ask for only what the pages actually use.
- linkedin_profile_url — scrape the lead's LinkedIn profile
- company_domain — AI analysis of the company
- person_analysis — AI analysis of the person
- linkedin_posts_person — the person's recent posts
- linkedin_posts_company — the company page's recent posts
A lead missing the inputs a type needs (no LinkedIn URL, no domain) is skipped rather than failing the batch — compare leads_to_enrich against what you sent, and check skipped_leads. Results land on the leads themselves; poll job_id with get-status, then read them back with get-lead.
Request body
Example request
{
"workspace_id": 55,
"lead_ids": [
56789,
56790
],
"enrichment_types": [
"company_domain"
]
}Response
Example response
{
"job_id": "9f1c8b2e-...",
"message": "Enrichment job started",
"leads_to_enrich": 2,
"skipped_leads": 0
}Changes
Changed in 2 of the 3 revisions of this API.211
- ▲
added
subschema #1subschema #2to the response bodyoneOflist for the response status400response-body-one-of-added
- ▲
the response's body type/format changed from
object/to/for status400response-body-type-changed
- ●
removed the optional property
messagefrom the response with the400statusresponse-optional-property-removed
- ▲
- ○
endpoint added
endpoint-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○