The Email Intelligence API is designed to provide an extensive analysis of email addresses, helping businesses and developers gain deeper insights into the emails they encounter. This API validates email addresses, checks their domain's DNS records, detects disposable or temporary email addresses, and determines if the domain belongs to a government or educational institution.
Domain validation and SSL verification
Mail exchange provider information
Comprehensive DNS record verification
Government and educational domain detection
Identify temporary email addresses
Format and domain validation
Select the ideal plan for your email intelligence needs with our flexible pricing tiers
1,000 Requests / Month
10,000 Requests / Month
100,000 Requests / Month
250,000 Requests / Month
The Email Intelligence API provides comprehensive analysis and validation of email addresses. This documentation outlines how to effectively integrate and utilize the API in your applications, enabling you to enhance email security, reduce fraud, and improve data quality.
Click the button below to run and test this API with Postman:
https://email-intelligence-api.p.rapidapi.com
All requests to the Email Intelligence API require authentication. Include your RapidAPI credentials in the request headers:
{
"X-RapidAPI-Key": "YOUR_RAPIDAPI_KEY",
"X-RapidAPI-Host": "email-intelligence-api.p.rapidapi.com"
}
You can obtain your API key by subscribing to the Email Intelligence API on RapidAPI.
Retrieves comprehensive information about an email address including its validity, domain details, DNS records, temporary email status, aliasing information, website availability, deliverability score, and risk indicator.
Parameter | Type | Required | Description |
---|---|---|---|
email |
string | Yes | The email address to check |
GET /v1/[email protected] HTTP/1.1
Host: email-intelligence-api.p.rapidapi.com
X-RapidAPI-Key: YOUR_RAPIDAPI_KEY
X-RapidAPI-Host: email-intelligence-api.p.rapidapi.com
{
"status": true,
"data": {
"email": "[email protected]",
"domain": "gmail.com",
"alias": {
"main": "test",
"alias": "alias"
},
"is_subdomain": false,
"is_valid": true,
"is_temp_email": false,
"is_gov": false,
"is_edu": false,
"has_valid_mx_records": true,
"records": {
"mx": [
{
"exchange": "alt1.aspmx.l.google.com",
"priority": 5
}
],
"spf": "v=spf1 include:_spf.google.com ~all",
"dmarc": "v=DMARC1; p=none; rua=mailto:[email protected]"
},
"smtp": {
"provider": "alt1.aspmx.l.google.com",
"addresses": [
{
"exchange": "alt1.aspmx.l.google.com",
"priority": 5
}
]
},
"email_provider": {
"name": "google",
"provider": "Google"
},
"website": {
"url": "http://gmail.com",
"is_valid": true,
"ssl": true
},
"deliverability_score": 85,
"risk_indicator": "low"
}
}
email
: The provided email addressdomain
: The domain part extracted from the email addressalias
: Information about email aliases (if present)is_valid
: Boolean indicating if the email format is validis_temp_email
: Boolean indicating if it's a temporary emailrecords
: DNS records (MX, SPF, DMARC)deliverability_score
: Score from 0-100risk_indicator
: Risk assessment (low, medium, high)The API uses standard HTTP status codes to indicate the success or failure of requests:
Status Code | Description | Possible Cause |
---|---|---|
200 OK |
Request succeeded | Email analysis completed successfully |
400 Bad Request |
Invalid parameters | Missing email parameter or severely malformed email format |
401 Unauthorized |
Authentication error | Invalid API key |
403 Forbidden |
Access denied | Your subscription doesn't allow this operation |
429 Too Many Requests |
Rate limit exceeded | You've exceeded your plan's request limits |
500 Internal Server Error |
Server-side error | Unexpected error occurred on the server |
Error responses include additional details about what went wrong:
{
"error": {
"message": "Missing required parameter: email",
"code": "MISSING_PARAM",
"status": 400
}
}
API rate limits vary by subscription plan:
When you exceed your rate limit, the API will return a 429 status code. Implement exponential backoff or queuing mechanisms to handle rate limiting gracefully.
The current version of the Email Intelligence API is v1. We maintain backward compatibility for all minor updates within a major version.
Version | Status | Notes |
---|---|---|
v1 |
Current | Full validation functionality with risk scoring |
We announce API updates and changes through our documentation and via email to active users. Major version changes will be announced at least 6 months in advance.
const axios = require('axios');
const options = {
method: 'GET',
url: 'https://email-intelligence-api.p.rapidapi.com/v1/check',
params: { email: '[email protected]' },
headers: {
'X-RapidAPI-Key': 'YOUR_RAPIDAPI_KEY',
'X-RapidAPI-Host': 'email-intelligence-api.p.rapidapi.com'
}
};
try {
const response = await axios.request(options);
// Handle valid email
if (response.data.data.is_valid) {
console.log('Email is valid!');
// Check risk level
if (response.data.data.risk_indicator === 'low') {
// Proceed with low-risk email
} else if (response.data.data.risk_indicator === 'medium') {
// Add additional verification
} else {
// High-risk handling
}
} else {
console.log('Email is invalid');
}
} catch (error) {
console.error('Error validating email:', error);
// Handle rate limiting
if (error.response && error.response.status === 429) {
// Implement retry with exponential backoff
}
}
import requests
import backoff
# Example with exponential backoff for rate limiting
@backoff.on_exception(backoff.expo, requests.exceptions.RequestException, max_tries=5)
def validate_email(email):
url = "https://email-intelligence-api.p.rapidapi.com/v1/check"
querystring = {"email": email}
headers = {
"X-RapidAPI-Key": "YOUR_RAPIDAPI_KEY",
"X-RapidAPI-Host": "email-intelligence-api.p.rapidapi.com"
}
response = requests.get(url, headers=headers, params=querystring)
response.raise_for_status() # Will trigger backoff on 429 errors
data = response.json()
if data['data']['is_valid']:
print(f"Email {email} is valid")
print(f"Deliverability score: {data['data']['deliverability_score']}")
return data['data']
else:
print(f"Email {email} is invalid")
return None
try:
result = validate_email("[email protected]")
except Exception as e:
print(f"Error validating email: {e}")
The Email Intelligence API provides comprehensive analysis of email addresses to help businesses and developers validate emails, detect disposable addresses, analyze DNS records, and assess deliverability risks. It's designed to improve email security, reduce fraud, and enhance the quality of email data in applications.
The API maintains a comprehensive database of known disposable and temporary email domains. When you submit an email address for analysis, the API checks if the domain part of the email matches any entry in this database. If a match is found, the API will flag the email as a temporary or disposable address, allowing you to take appropriate action in your application.
The deliverability score is a numeric value (0-100) that estimates the likelihood of an email sent to the address being successfully delivered. The score takes into account multiple factors including domain reputation, DNS records, SMTP server configuration, and other email infrastructure elements. A higher score indicates better deliverability prospects. This can help you prioritize email addresses in marketing campaigns or identify potential delivery issues.
Email alias detection identifies when a user has utilized the "plus addressing" feature available in many email services (e.g., [email protected]). The API separates the main email address ([email protected]) from the alias portion (alias), allowing you to identify when the same user might be registering multiple accounts with different aliases. This helps prevent duplicate accounts and potential abuse of free trials or promotions.
Yes, the Email Intelligence API can significantly help reduce fraud and improve security. By identifying disposable email addresses often used for fraudulent sign-ups, detecting email aliases that might be used to create multiple accounts, and providing risk indicators based on comprehensive analysis, the API gives you valuable data to make informed decisions about user verification. Additionally, the information about DNS records and SMTP configuration helps ensure you're dealing with legitimate email domains rather than potentially malicious ones.
Connect our powerful APIs with your favorite platforms for seamless workflow automation
Connect with 3,000+ apps
Create complex automation workflows
Microsoft's enterprise automation
Open-source workflow automation
Want to see us integrate with your favorite platform? Let us know!