Docs/APIs/Disposable Email Checker

Disposable Email Checker

Check if email is disposable

OperationalCredits 6 per callp50 178msData ValidationStar

Overview

Send a complete email address, or just a domain, to check it against a disposable email blocklist of over 100,000 throwaway and temp email domains, updated daily. The check tests both exact matches and parent domains, and separately flags privacy relay addresses such as Apple Hide My Email, DuckDuckGo and Firefox Relay, which forward to a real inbox. Paid plans also read the domain's MX records to name the relay service behind a custom domain and to catch new throwaway domains that receive mail through a known disposable service.

Live Test Disposable Email Checker API →

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

GEThttps://api.apiverve.com/v1/emaildisposablechecker
curl "https://api.apiverve.com/v1/emaildisposablechecker?email=support%40myspace.com&domain=mailinator.com" \
  -H "x-api-key: your_api_key_here"

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

401 is the only auth verdict

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.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

ParameterTypeDescription
emailOptionalstringThe email address to check (e.g., support@myspace.com). Send this or domain
email
domainOptionalstringA domain to check instead of a full address (e.g., mailinator.com). Send this or email
email

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

Sample response
{
  "status": "ok",
  "error": null,
  "data": {
    "isDisposable": false,
    "email": "support@myspace.com",
    "domain": "myspace.com",
    "isRelay": false,
    "relayService": null,
    "isDisposableMx": false
  }
}

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.

FieldTypeExampleDescription
isDisposablebooleanfalseWhether the email address is a disposable address (matched by exact domain or a parent domain of the sender)
emailstring"support@myspace.com"The email address that was checked; null when a domain was sent instead
domainstring"myspace.com"The domain that was checked, taken from the email address when one was sent
isRelaybooleanfalseThe domain belongs to an email relay or forwarding service (Apple Hide My Email, DuckDuckGo, Firefox Relay, SimpleLogin, Proton Pass, addy.io, 33mail). Relay addresses stay live and forward to a real mailbox the sender never sees, so they are reported separately from isDisposable
relayServicePremiumobjectnullWhich relay service handles the address. Also names the service when a custom domain routes its mail through SimpleLogin, addy.io, Apple or DuckDuckGo, which isRelay does not catch; null when no relay service is involved or the MX lookup failed
isDisposableMxPremiumbooleanfalseThe domain's mail servers belong to a known disposable email service. Catches newly registered throwaway domains that are not on the list yet, because they still receive mail through the same service; null if the MX lookup failed

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Use cases

User Registration Screening
To stop fake signups, SaaS apps check user email addresses at registration and reject submissions matching temporary domain lists.
Mailing List Cleaning
Filter out temporary inboxes from marketing contact databases before scheduling newsletter campaigns to protect sender reputation and delivery rates.
Gated Content Verification
When visitors request whitepapers or trial access, verify their email domain immediately to require a genuine corporate or personal inbox.
Promo Abuse Prevention
E-commerce stores evaluate customer emails during checkout to prevent shoppers from repeatedly claiming first-order discounts with burner accounts.

Other ways to use Disposable Email Checker

Set up Disposable Email Checker on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →

More in Data Validation:

Was this page helpful?