Email verification API
Email verification API (email validation API)
The EasyMailVerify email verification API lets your servers check addresses with a simple HTTPS request: verify one email in real time while a user signs up, or submit lists of up to 50,000 addresses. Every response includes a status, a result code, a plain-language reason and risk flags.
By Steve Smith, EasyMailVerify team
Last updated · Editorial standards
No monthly subscription · Credits never expire · Unknown results use no credits
What can you build with an email verification API?
- Block invalid and disposable addresses on sign-up forms
- Suggest corrections for typos like gmial.com before an account is created
- Verify contacts as they sync into your CRM or marketing tool
- Clean lists automatically in your own data pipeline
Email verification API or email validation API?
They're two names for the same thing. Some providers say email validation API, others email verification API; both check that an address is well formed, that its domain can receive mail, and that the mailbox exists. The EasyMailVerify email validation API returns Passed, Failed or Unknown with a result code and reason, so your code can act on each answer.
Endpoints
| Endpoint | What it does |
|---|---|
| POST /api/v1/verify | Verify one email address in real time |
| GET /api/v1/verify/{id} | Get the result of a single check that took longer |
| POST /api/v1/lists | Submit a list of up to 50,000 addresses |
| GET /api/v1/lists/{id} | Check a list's progress and totals |
| GET /api/v1/lists/{id}/results | Page through a list's results |
| GET /api/v1/balance | Check your remaining credits |
How do you authenticate API requests?
Create API keys on the API page of your dashboard and send them as a bearer token: Authorization: Bearer emv_live_…. Keys are shown once, stored only as a secure hash, can be revoked at any time, and each account can have up to 10 active keys, for example one per app or environment.
Example request and response
POST /api/v1/verify
curl -X POST https://easymailverify.com/api/v1/verify \
-H "Authorization: Bearer $EMV_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: 6f1c2b8e-3d4a-4f5b-9c7d-1e2f3a4b5c6d" \
-d '{"email": "jane@acme.com", "label": "Sign-up form"}'
{
"email": "jane@acme.com",
"status": "passed",
"result_code": "deliverable",
"reason": "The mail server confirmed this mailbox exists and accepts mail.",
"credits_used": 1,
"suggested_email": null,
"disposable": false,
"role_account": false,
"catch_all": false,
"checked_at": "2026-10-05T09:00:00Z",
"duration_ms": 640
}Response fields you'll use most
| Field | Meaning |
|---|---|
| status | passed, failed or unknown |
| result_code | The specific reason, such as deliverable, mailbox_not_found or catch_all |
| reason | A plain-language explanation of result_code |
| credits_used | 1 for passed or failed, 0 for unknown |
| suggested_email | A corrected address when a likely typo is detected |
| disposable / role_account / free_provider / catch_all | Risk flags you can act on |
| mail_server | Hostname, IP, organization and location of the mail server, when available |
How fast is the email verification API?
Most single checks return a full result with HTTP 200 within seconds. If a mail server needs longer, you get HTTP 202 with an ID and status queued; poll GET /api/v1/verify/{id} until the result is ready. Lists return 202 immediately and process in the background.
How do retries and errors work?
Send an Idempotency-Key header and retry freely: the same key never charges twice. Errors come back as JSON with a code and message.
| HTTP | Code | When |
|---|---|---|
| 400 | invalid_email / invalid_list | The request body isn't valid |
| 401 | unauthorized | The API key is missing, invalid or revoked |
| 402 | insufficient_credits | Not enough credits for the request |
| 404 | not_found | The check or list doesn't exist on your account |
| 409 | idempotency_conflict | The key was already used for a different request |
How much does the email verification API cost?
API checks use your regular credits: one per Passed or Failed result, none for Unknown results or duplicates in a list. Credits are one-time purchases that never expire, so spiky traffic never needs a plan upgrade.
Keep your keys secure
- Call the API from your server, never from browser or mobile app code
- Use a separate key per app or environment so you can revoke one without the others
- Store keys in environment variables or a secrets manager
Frequently asked questions
Is the email verification API free?
The API is included with every account. Checks use the same pay-as-you-go credits as the dashboard, and Unknown results never use credits.
How fast is the API?
Most single checks return within seconds. When a check needs longer, the API returns an ID you can poll.
Can I verify a whole list through the API?
Yes. Submit up to 50,000 addresses to POST /api/v1/lists, then page through the results.
Can I call the API from a browser or mobile app?
Keep API keys on your server. Call EasyMailVerify from your backend, then show the result in your app.
Will retries charge me twice?
Not if you send an Idempotency-Key header. A retry with the same key returns the original result.
How long are API results kept?
Checked addresses and their detailed results are permanently deleted 7 days after verification.
Sources
Related
Ready to check your list?
Pay only for Passed and Failed results. Credits never expire.
Create account