Email Validation
Syntax, domain, mailbox and catch-all checks with disposable and role detection.
curl -X POST https://api.1lookup.dev/v1/email-validation \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"email":"jane.doe@example.com"}'{
"success": true,
"data": {
"email": "jane.doe@example.com",
"status": "deliverable",
"sub_status": "mailbox_exists",
"checks": {
"syntax": true,
"domain": true,
"mx": true,
"smtp": true
},
"flags": {
"catch_all": false,
"disposable": false,
"role": false,
"free_provider": false
},
"mx_host": "mx1.example.com"
},
"meta": {
"credits_used": 1,
"credits_remaining": 999,
"cached": false,
"request_id": "req_8f3a2c1e9b7d"
}
}Authorization
Authorizationstring<bearer>requiredYour API key as a Bearer token. Live keys start with 1lk_live_. Test keys start with 1lk_test_ and return this endpoint's sample response without spending credits. See authentication.
Body
Send the fields as a JSON object with Content-Type: application/json.
emailstring<email>requiredEmail address. Example: jane.doe@example.com
freshbooleanSkip the 7-day cache and run a new lookup. Charged as a normal lookup.
referencestringYour own identifier, echoed back in meta and shown in lookup history.
Response
A 200 response carries the result in data and the cost of the call in meta. These are the fields most integrations read.
successbooleantrue when the lookup ran.
data.statusstringdeliverable, undeliverable, risky or unknown. The one field most rules are built on.
data.sub_statusstringWhy the status was assigned, for example mailbox_exists, mailbox_not_found or greylisted.
data.checks.mxbooleanWhether the domain publishes mail servers that can receive email.
data.checks.smtpbooleanWhether the receiving server confirmed the mailbox over SMTP.
data.flags.catch_allbooleantrue when the domain accepts mail for every address, so the mailbox cannot be confirmed.
data.flags.disposablebooleantrue when the domain belongs to a temporary inbox service.
data.flags.rolebooleantrue for shared addresses such as info@ or support@ that are not one person.
data.flags.free_providerbooleantrue when the address is on a free webmail service instead of a company domain.
meta.credits_usednumberCredits charged for this call.
meta.credits_remainingnumberYour balance after the call.
meta.cachedbooleantrue when the result came from the 7-day cache.
meta.request_idstringQuote this when you contact support.
Errors
A failed request returns success: false with an error object, and is never charged. The full list is on the errors page.
| HTTP | Code | Meaning |
|---|---|---|
| 401 | unauthorized | The key is missing, malformed or revoked. |
| 402 | insufficient_credits | Your credits are used up and pay as you go is off or at its limit. |
| 422 | invalid_input | A field is missing or malformed. The field property names it. |
| 429 | rate_limited | Too many requests for this key. Wait for the Retry-After interval. |
| 500 | internal_error | Something failed on our side. Safe to retry. |
| 503 | source_unavailable | An upstream source did not answer in time. Safe to retry. |
Billing
1 credit. Charged when the lookup runs and returns a result. Errors are never charged, and repeating the same input within 7 days is served from cache at no charge.
Product overview and use cases