When to use email lookup
- Contact enrichment — you’ve collected a name and company from a form, LinkedIn, or a CSV and need a reachable email to act on it.
- Lead research — you know who you want to contact and where they work, but not the exact address.
- Reconnecting with known contacts — after a company moves off a free email provider to a custom domain.
Making a request
To look up an email, send aPOST request to /v1/email-lookup with the person’s first name, last name, and company domain in the JSON body. Include your API key in the X-API-Key header.
Get your API key
Sign in to the OrbiSearch dashboard and copy your API key.
Read the response
When a deliverable address is found, the response includes the discovered
email and the same enrichment fields as single verification.Interpreting the response
The top-levelstatus uses the same vocabulary as /v1/verify:
status | substatus | What it means |
|---|---|---|
safe | deliverable | We found a deliverable address for this person. The email field contains it. |
unknown | no_address_found | We couldn’t confirm a deliverable address for this person at this domain. The email field is null. |
unknown | timeout | The lookup hit the per-request time budget before completing. You can retry with a higher timeout value. |
first_name, last_name, and domain you sent (with casing and whitespace cleaned up), and includes credits_consumed. When a deliverable address is found, the full set of verification fields (email_provider, mx_record, enrichment flags) is populated — see Single Verification: Response Fields for their meaning.
When email is null, don’t send to that person at that domain — we couldn’t find a deliverable address for them.
Pricing
Each lookup costs 1 credit. You are charged on a hit (safe), on a clean miss (no_address_found), and on a timeout. You are not charged, and the credit is refunded automatically, if our lookup service is temporarily unavailable (502).
Results are cached for 24 hours. Looking up the same person (same first name, last name, and domain, ignoring casing and whitespace) within that window returns the cached result at no credit cost.
Rate limits
This endpoint shares the 20 requests per second per API key limit with/v1/verify and /v1/bulk.
The timeout parameter
By default, OrbiSearch waits up to 90 seconds for the lookup to complete. You can override this with the timeout field in the request body (minimum 3, maximum 120, in seconds).
status: unknown / substatus: timeout response. The credit is charged — the lookup was attempted — but you can retry with a larger timeout for more headroom.