Disposable Email Checker API Reference

Overview

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.

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" \
  -H "x-api-key: your_api_key_here"

const res = await fetch('https://api.apiverve.com/v1/emaildisposablechecker?email=support%40myspace.com', {
  headers: { 'x-api-key': 'your_api_key_here' },
});

if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);

const { data } = await res.json();
console.log(data);

import requests

res = requests.get(
    "https://api.apiverve.com/v1/emaildisposablechecker?email=support%40myspace.com",
    headers={"x-api-key": "your_api_key_here"},
    timeout=15,
)
res.raise_for_status()

print(res.json()["data"])

package main

import (
	"fmt"
	"io"
	"net/http"
)

func main() {
	req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/emaildisposablechecker?email=support%40myspace.com", nil)
	req.Header.Set("x-api-key", "your_api_key_here")

	res, err := http.DefaultClient.Do(req)
	if err != nil {
		panic(err)
	}
	defer res.Body.Close()

	out, _ := io.ReadAll(res.Body)
	fmt.Println(string(out))
}

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.

Parameter	Type	Description
`email`Required	string	The email address to check (e.g., [email protected]) 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": "[email protected]",
    "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	`"[email protected]"`	The email address that was checked
`domain`	string	`"myspace.com"`	The domain portion of the email address

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.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted	A key restriction or IP allow-list; see key scoping.
`429`	Rate limited, or out of credits	Read `error` to tell them apart; see rate limits.

Use cases

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

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 →

Use it in 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 →

Disposable Email Checker