Block bad addresses at signup
Call the validate endpoint from your form handler to reject typos and disposable domains before the account is created.
POST /api/v1/email/validate
Email Validation API
Check whether an address is well-formed, disposable or deliverable. Validate one email, a batch, or run an async job over thousands.
4 endpoints · 1 credit = $0.001. Each endpoint has its own credit cost, listed below. Calls that fail because of a service error are refunded.
API workspace and documentation
AxioAPI Studio · Email Validation
Free Trial: 10 of 10 left
Select API to test:
Validate email
Mẫu thử nhanh:
Ready
?
?
No request yet. Run a test to see the actual response.
What you can build with the email validation API
The email validation API checks whether an address is well formed, uses a disposable domain and has MX records before you store it or send to it. Validate one address in real time, a small batch in one call, or a larger list as an async job.
Clean a list before a campaign
Submit up to 50 addresses per batch call, or create a validation job for a bigger list and fetch results when it finishes.
POST /api/v1/email/validate-batch
Cross-check with several providers
Turn on consensus for a job when you want the result confirmed by more than one provider.
POST /api/v1/email/validation-jobs
Try it free, no account needed: Email validator
How the email validation API works
-
1
Validate one address
POST /api/v1/email/validate returns separate signals for syntax, disposable domain and MX.
-
2
Validate in bulk
POST /api/v1/email/validate-batch takes an array of emails, up to 50 per call.
-
3
Run a job for large lists
POST /api/v1/email/validation-jobs returns a job ID; GET /api/v1/email/validation-jobs/{job} returns progress and item results.
Try the Email Validation API with your own account
New accounts receive 200 credits after verification, enough for about 333 calls to "Batch validate emails".
Using Email Validation
Check a single address or submit an array for a batch. Invalid format, disposable domain and MX are separate signals.
For a validation job, keep the returned job ID and fetch its progress and item results.
MX records and syntax checks are not proof of delivery. Missing evidence is shown as unavailable, not a passing check.
Email validation API endpoints and pricing
OpenAPI 3.1 JSONSelect an operation above and open API & Docs for parameters and cURL, JavaScript, Python or PHP examples. The web tool uses your signed-in session; external integrations use a Bearer API key.
| Method | Endpoint | Cost |
|---|---|---|
| POST |
Validate email
/api/v1/email/validate
Helpful?
|
1 credit / email≈ $0.001 |
| POST |
Batch validate emails
/api/v1/email/validate-batch
Helpful?
|
0.6 credit / email≈ $0.0006 |
| POST |
Create validation job
/api/v1/email/validation-jobs
Helpful?
|
0.6 credit / email≈ $0.0006 |
| GET |
Get validation job
/api/v1/email/validation-jobs/{job}
Helpful?
|
0 credit / request |
Email validation API: frequently asked questions
What does an email validation API check?
Format, whether the domain is a known disposable domain, and whether the domain has MX records. These are reported as separate signals. Together they cover email verification API use cases: disposable email detection, MX record checks and bulk email verification through batch calls and jobs.
Does a passing result mean the email will be delivered?
No. Valid syntax and MX records do not prove that a mailbox exists or that delivery will succeed. Missing evidence is shown as unavailable, not as a pass.
How many emails can I send at once?
Up to 50 in a batch call. For more, create a validation job.
How is it billed?
Per email, with a lower price for batch and job validation. Fetching a job is free. See the endpoint table below. New accounts receive 200 credits after verification.
Before integrating
Live and example data
Check the Live or Sandbox label before running. Examples demonstrate the response structure and do not guarantee live service status.
Credits and limits
Pricing depends on the endpoint and billable units. Failed live requests are not replaced with billable examples. Check your account limits before running repeated requests.
View pricingHandling errors
Keep the request ID for troubleshooting. For 429, respect Retry-After when provided. If a create or delete request loses its connection, check the resource state before retrying.
Related APIs
All APIs-
Temporary Email
6 endpointsCreate disposable inboxes, read incoming messages, rotate addresses and delete inboxes when you are done. Available through the AxioAPI REST API.
View Temporary Email API → -
Verify
1 endpointsWait for a verification code to arrive and get it back in a single call, with polling and timeouts handled by AxioAPI.
View Verify API → -
Utility
3 endpointsBIN lookup for card issuers, DNS resolution over DNS-over-HTTPS, and technology profiling for any domain.
View Utility API →
Often used together: Temp Mail API · OTP API · DNS Lookup API, BIN Lookup & Tech Stack
Ready to integrate the Email Validation API? Create an account and get your API key in minutes.