How a lookup runs
Work email lookups are asynchronous. The submit call answers202 at once with a job id and a status_check_url. Poll that URL until status is completed or failed, or pass a webhook_url and Forager POSTs the result to it when the job finishes. Polling is free.
Step through one single lookup, from the 202 to a terminal status (illustrative payloads):
- Single lookup:
statusmoves throughqueued,runningandawaiting_providertocompletedorfailed. A completed job hasresultset tofoundornot_found; a failed one has anerror_code. - Bulk lookup: the submit returns a
batch_id. The batchstatusisqueued,running,completedorfailed, andresultsstays empty until the batch iscompleted, then holds one result per submitted lookup in the order you sent them.
Endpoints
- POST /api/v2/{account_id}/datastorage/person_contacts_lookup/work_emails/: Single work email lookup
- GET /api/v2/{account_id}/datastorage/person_contacts_lookup/work_emails/{job_id}/: Single work email lookup result
- POST /api/v2/{account_id}/datastorage/person_contacts_lookup/work_emails/bulk/: Bulk work email lookup
- GET /api/v2/{account_id}/datastorage/person_contacts_lookup/work_emails/bulk/{batch_id}/: Bulk work email lookup status and results
Build a single lookup
Identify the person by name and company domain, or by LinkedIn public identifier, and copy the submit request. Nothing is sent from this page.Read a result
Polling thestatus_check_url returns the job. status says how far it got and result what it concluded. Click a field to see its type. The values are illustrative.