The no2bounce API is designed to provide a robust solution for email validation, helping businesses ensure the accuracy and deliverability of their email lists. This email verifier API is an essential part of the no2bounce application, allowing users to validate large volumes of email addresses in real-time programmatically.
To enhance ease of use, the no2bounce API is accessible via the POST method, making it straightforward for developers to incorporate real-time email validation into their applications. With just a single endpoint, you can instantly verify the validity of an email address, ensuring that only accurate and deliverable emails are accepted.
The Real-Time Email Verification API from no2bounce provides a reliable and efficient solution for email verification needs. By integrating this tool into your application, you can significantly improve the quality of your data, reduce bounce rates, and enhance the overall user experience. Whether you’re onboarding new users or maintaining a clean email list, no2bounce makes real-time email verification simple and effective.
For businesses looking to enhance email deliverability, the Email Verifier API is an essential tool. With the Free Email Validation & Verification APIs, you can quickly validate email addresses and avoid costly mistakes. The Real-Time Email Verification API ensures every email is accurate and deliverable, while the Email Validation API Tools help businesses scale their email verification process effectively.
curl --location 'https://connect.no2bounce.com/n2b_apiValidator' \
--header 'apitoken: 0b5f6948f5aa7dbfdac5ded92ae2623f' \
--header 'Content-Type: application/json' \
--data-raw '{
"emailList": [
"demo@gmail.com",
"demo1@outlook.com",
"demo2@yahoo.com"
],
"catchall": true,
"hashkey": "uniqueStringHere"
}'
💡 The hashkey is used to prevent duplicate requests during bulk email validation, particularly when processing large datasets of over 40,000 emails. Based on customer feedback, some users experienced delays of several seconds during the validation process. This caused instances where customers clicked multiple times within a short span (less than 1 second), resulting in credit loss due to duplicate requests.To mitigate this issue, you can pass any unique string as the hashkey. Each key has a validity of 3 minutes, ensuring that subsequent requests within this timeframe are ignored, effectively preventing duplicate processing.
{
"message": "Success",
"statusCode": 200,
"data": {
"trackingId": 1724302650843,
}
}
curl --location 'https://connect.no2bounce.com/n2b_apiValidatorResult?trackingId=1724302092064'\
--header 'apitoken:0b5f6948f5aa7dbfdac5ded92ae2623f'
{
"message": "Success",
"statusCode": 200,
"data": {
"taskId": 1724302650843,
"totalEmails": 20005,
"completedEmails": 1915,
"deliverability": 142,
"catchAll": 1456,
"invalid": 317,
"bounce": 0,
"spam": 0
}
}
{
"message": "Success",
"statusCode": 200,
"data": {
"taskId": 1724302650843,
"totalEmails": 20005,
"completedEmails": 1915,
"deliverability": 142,
"catchAll": 1456,
"invalid": 317,
"bounce": 0,
"spam": 0
}
}
{
"message": "Success",
"statusCode": 200,
"data": {
"catchall_status": "Completed",
"signedUrl": "https://connect.no2bounce.com/n2b_apiValidator/generatorResult/1727095008289_catchall.csv?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA3W2VPMD3YV5O3XNP%2F20240923%2Feu-west-2%2Fs3%2Faws4_request&X-Amz-Date=20240923T123947Z&X-Amz-Expires=3600&X-Amz-Signature=38ad24d83d7dcb6eca6cd126676586ce739a67d0d6a875b0122cc0423ae0922c&X-Amz-SignedHeaders=host&x-id=GetObject"
}
}