Skip to main content
find work email
The assistant tool is find_work_email. Use a canonical person_id or an exact public LinkedIn /in/ URL on explicit contact-research intent. This runs actual discovery for the identified person’s observed employer and strictly verifies at most one employer-domain candidate. On the published plan for new signups, 2 credits are settled only for status: valid, a non-catch-all business address with a current check and an employer-domain association. Discovery includes verification, with no validation surcharge or implicit profile charge. no_data, unverified, catch_all, unknown and unavailable cost zero. An explicitly requested employer-associated business candidate may be returned as status: unverified, with a clear UNVERIFIED label. Email assessment, verification status, catch-all uncertainty and assessment dates remain separate. Never treat an unknown catch-all verdict as false. Known-invalid, personal, disposable and unrelated-domain candidates are withheld. This does not prove ownership or delivery. The 24-hour discovery receipt is shared with get_person_profile including work_email. Use dry_run: true for a maximum estimate with no data lookup, and max_credits to bound a real request. See email outcomes and safe retries.

Authorizations

Authorization
string
header
required

Send Authorization: Bearer dl_live_<64 lowercase hexadecimal characters>. Signed-in users can create account-scoped, revocable keys in the Datalayer dashboard. A key does not grant credits. Dashboard session cookies are not API credentials.

Headers

Idempotency-Key
string

Recommended for every paid operation. Account-scoped and bound to normalized operation/input. Retry exactly the same key after transport loss: a committed credit result is replayed from persisted normalized bytes without a data lookup or another debit. Changed input, key expiry or paid-anchor expiry returns 409. In-flight requests return request_in_progress. Network delivery and D1 commit are not atomic. If omitted a request ID is created.

Required string length: 1 - 128
Pattern: ^[A-Za-z0-9_-]{1,128}$

Body

application/json
person_id
string
required
Pattern: ^[1-9][0-9]{0,19}$
profile_url
string<uri>
Maximum string length: 2000
max_credits
integer

Advanced: highest number of credits this call may spend. The call is refused before any lookup when the estimate is higher.

Required range: 0 <= x <= 3
dry_run
boolean

Advanced: return the maximum credit estimate without looking up data.

Response

A settled result or a maximum estimate with no data lookup.

data
object
required
meta
object
required