API Overview

Welcome to the Valid Email Checker API! 🚀

Our REST API lets you integrate email verification directly into your applications, websites, and workflows. Whether you're validating emails at signup, cleaning lists programmatically, or building custom integrations, the API has you covered.

---

What Can You Do With the API?

The Valid Email Checker API enables you to:

• Verify single emails in real-time - Perfect for registration forms and lead capture
• Verify emails in bulk - Submit lists programmatically and retrieve results
• Automate your workflows - Integrate with your CRM, marketing tools, or custom applications
• Build custom solutions - Create your own verification interfaces and dashboards

---

Base URL

All API requests are made to:

https://app.validemailchecker.com/api/

---

Available Endpoints

Method	Endpoint	Description
POST	/verify-single	Verify a single email address
POST	/verify-bulk	Create a bulk verification task
GET	/get-results/{task_id}	Retrieve bulk verification results

---

Authentication

All API requests require authentication using your API key.

Include your API key in the Authorization header as a Bearer token:

Authorization: Bearer YOUR_API_KEY

warning

Never share your API key or commit it to public repositories. Treat it like a password.

Example Request

curl -X POST https://app.validemailchecker.com/api/verify-single \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "user@example.com"}'

---

Before You Start

1. Purchase Credits

API access is available to users who have purchased credits. This helps us prevent abuse and ensure service quality for legitimate users.

info

The API uses the same credits as the dashboard. 1 credit = 1 email verification, whether via API or web interface.

2. Generate an API Key

Once you have credits, you can generate API keys from the Developer section in your dashboard.

3. Verify Your Email

For security, we send a 6-digit verification code to your email when generating a new API key. This confirms you own the account.

---

How Credits Work with the API

The API shares your account's credit pool:

• Single verification: 1 credit per email
• Bulk verification: 1 credit per email in the task
• Credits are deducted when verification completes
• Failed verifications (unknown results) are automatically refunded

Your credit balance is the same whether you verify via the dashboard or the API.

---

Response Format

All API responses are returned in JSON format.

Successful Response

{
  "email": "user@example.com",
  "status": "safe",
  "is_valid": true,
  "is_disposable": false,
  "is_role_account": false,
  "is_catch_all": false,
  "is_free_email": true,
  "mx_found": true,
  "domain": "example.com",
  "risk_score": 15,
  "deliverability": "high",
  "credits_used": 1,
  "verified_at": "2025-01-12T10:30:00Z",
  "reason": "Valid mailbox"
}

Error Response

{
    "error": "Invalid or inactive API key"
}

---

Email Status Values

The API returns one of these status values for each email:

Status	Description	Safe to Send?
safe	Valid, deliverable email address	✅ Yes
risky	Deliverable but has risk factors	⚠️ Use caution
invalid	Email address doesn't exist	❌ No
disposable	Temporary/throwaway email	❌ No
catch_all	Domain accepts all emails	⚠️ Use caution
role_account	Generic address (info@, support@)	⚠️ Depends
spamtrap	Known spam trap address	❌ No
unknown	Verification couldn't complete	⚠️ Retry later

tip

For the best deliverability, only send to emails with safe status. Use caution with risky, catch_all, and role_account results.

---

Response Fields Explained

Field	Type	Description
email	string	The email address that was verified
status	string	Verification result (see status values above)
is_valid	boolean	Whether the email is valid and deliverable
is_disposable	boolean	Whether it's a temporary/disposable email
is_role_account	boolean	Whether it's a role-based address (info@, admin@)
is_catch_all	boolean	Whether the domain accepts all emails
is_free_email	boolean	Whether it's from a free provider (Gmail, Yahoo, etc.)
mx_found	boolean	Whether valid MX records exist for the domain
domain	string	The domain part of the email
risk_score	integer	Risk score from 0-100 (lower is safer)
deliverability	string	Deliverability rating: high, medium, low, or unknown
credits_used	integer	Number of credits consumed (usually 1)
verified_at	string	ISO 8601 timestamp of verification
reason	string	Human-readable explanation of the result

---

Rate Limits

To ensure fair usage and system stability:

Limit	Value
Requests per minute	60
Requests per day	10,000

If you exceed these limits, you'll receive a 429 Too Many Requests response. See Rate Limits & Error Handling for details.

---

Security Features

We take API security seriously:

• SHA-256 hashed keys - Your API keys are securely hashed before storage
• Email verification - New keys require email confirmation
• Rate limiting - Protects against abuse and runaway scripts
• IP monitoring - Suspicious activity triggers automatic protection
• Key management - Regenerate, disable, or delete keys anytime

---

Quick Start

Ready to make your first API call? Here's how:

Step 1: Get Your API Key

Go to Developer in your dashboard sidebar and generate an API key. You'll need to verify with a code sent to your email.

Step 2: Make a Test Request

curl -X POST https://app.validemailchecker.com/api/verify-single \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "test@gmail.com"}'

Step 3: Check the Response

You'll receive a JSON response with the verification result. That's it - you've made your first API call!

---

Next Steps

Ready to dive deeper?

-> Generating API Keys - Create and manage your API keys

-> Single Verification Endpoint - Verify emails one at a time

-> Bulk Verification Endpoint - Verify lists programmatically