/emails/find

POST /api/emails/find

Price: 100 credits

Find a working email for a person by LinkedIn profile URL or name + company domain.

How to use it

Find a working (deliverable) email for a person. Provide either a LinkedIn profile URL (with vanity alias) or a full name together with the company domain. Personal-inbox addresses (gmail, outlook, etc.) are returned with is_personal=true. A person resolved before is answered from the result already established for them, up to a year old, so email_status and is_personal are as of that resolution, not re-verified now.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• linkedin_url string nullable — LinkedIn profile URL with vanity alias. Example: https://www.linkedin.com/in/satyanadella/ (examples: "https://www.linkedin.com/in/satyanadella/")
• name string nullable — Person's full name (used together with company_domain)
• company_domain string nullable — Company domain, e.g. stripe.com (used together with name)

Response

• @type string (default: "EmailFindResult")
• email string required
• email_status string required (one of: "valid", "risky")
• is_personal boolean (default: false)
• linkedin_url string nullable
• full_name string nullable
• company_name string nullable
• company_domain string nullable
• job_title string nullable
• resolved_by string required
• confidence number required

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.