Email Disposable Checker is a simple tool for checking if an email address is disposable. It returns if the email address is disposable or not.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Disposable Email Checker response payload
}
}
About the Disposable Email Checker API
Email Disposable Checker works by querying a large database of disposable email domains to check if the email address provided is disposable, matching both exact domains and subdomains of known disposable providers. The database is updated regularly to ensure accurate and up-to-date information.
What people use it for
- Email Verification
- Use the Email Disposable Checker API to verify email addresses. Use the data to check for disposable emails, prevent fraud, and maintain data quality
- Lead Generation
- Check if email is disposable by using the Email Disposable Checker API for lead generation. Use the data to filter out disposable emails, improve deliverability, and optimize marketing campaigns
- User Registration
- Use the Email Disposable Checker API to check if email is disposable for user registration. Use the data to prevent fake accounts, verify users, and enhance security
- Data Quality
- Check if email is disposable by using the Email Disposable Checker API for data quality. Use the data to clean databases, remove disposable emails, and ensure accuracy
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Disposable Email Checker
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Disposable Email Checker API do?
How do I authenticate Disposable Email Checker API requests?
How much does the Disposable Email Checker API cost?
How fast is the Disposable Email Checker API?
What response formats does the Disposable Email Checker API support?
What HTTP method does the Disposable Email Checker API use?
Request parameters — GET /v1/emaildisposablechecker
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
emailRequired | string | support@myspace.com | The email address to check (e.g., support@myspace.com) email |
curl "https://api.apiverve.com/v1/emaildisposablechecker?email=support%40myspace.com" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/emaildisposablechecker
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"isDisposable": false,
"email": "support@myspace.com",
"domain": "myspace.com"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
isDisposable | boolean | false | Whether the email address is a disposable address (matched by exact domain or a parent domain of the sender) |
email | string | "support@myspace.com" | The email address that was checked |
domain | string | "myspace.com" | The domain portion of the email address |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 6 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Disposable Email Checker calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 33 | Free |
| Starter | $29.99 | 200,000 | 33,333 | $0.90 |
| Pro | $99.99 | 1,000,000 | 166,666 | $0.60 |
| Mega | $299.99 | 4,000,000 | 666,666 | $0.45 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/emaildisposablechecker
No SDK to install — this is a plain HTTPS call to /v1/emaildisposablechecker with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/emaildisposablechecker" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/emaildisposablechecker
Install the Node.js SDK, then call the Disposable Email Checker API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/emaildisposablecheckerconst res = await fetch("https://api.apiverve.com/v1/emaildisposablechecker", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/emaildisposablechecker
Install the Python SDK, then call the Disposable Email Checker API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-emaildisposablecheckerimport requests
res = requests.get(
"https://api.apiverve.com/v1/emaildisposablechecker",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/emaildisposablechecker
Install the C# / .NET SDK, then call the Disposable Email Checker API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.DisposableEmailCheckerusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/emaildisposablechecker");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/emaildisposablechecker
No SDK to install — this is a plain HTTPS call to /v1/emaildisposablechecker with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/emaildisposablechecker", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/emaildisposablechecker
No SDK to install — this is a plain HTTPS call to /v1/emaildisposablechecker with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/emaildisposablechecker");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/emaildisposablechecker
No SDK to install — this is a plain HTTPS call to /v1/emaildisposablechecker with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/emaildisposablechecker")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Disposable Email Checker form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Disposable Email Checker API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Disposable Email Checker API.
Data Validation
- Card Validator
- Disposable Email Checker
- Disposable Phone Number Checker
- Email Validator
- Password Strength
- Phone Number Validator
- SEO Quick Validator
- Spam Detector
- Username Profanity
Related articles
All articles →
Preventing Fake Signups: Registration Fraud GuideLearn how to stop bots and fraudsters while maintaining conversion rates for legitimate users.Read
Email Validation Best Practices: Beyond Simple RegexEmail validation beyond regex. Learn how to verify deliverability without rejecting legitimate users.Read
Email Validation That Actually WorksThat regex you found on Stack Overflow is wrong. Here's how to validate emails properly—and why it matters more than you think.Read