Email Validation
API Documentation
Introduction
Email validation is a process used to verify the accuracy and authenticity of an email address. It ensures that the email provided is formatted correctly and actually exists as a reachable address. This helps in reducing bounce rates, improving email deliverability, and maintaining a clean mailing list by filtering out invalid or fraudulent addresses.
The API takes an email address and validates it for syntactical, domain correctness and resolution, and the existance of the actual email address.
https://api.addresser.com.au/emailvalidate
Example Usage
https://api.addresser.com.au/emailvalidate?email=abc@somedomain.com
Request Headers
Field | Type | Description |
---|---|---|
x-api-key | String |
Your API key. You can access API Key after registering for valid subscription, via the "My Credentials" section after logging into the "My Addresser" portal. |
Parameter
Field | Type | Description |
---|---|---|
String |
Email address to be validated. |
Response
The success response from the API consists of six email validation attributes as listed in the example extract below.
200 Success Response Structure
{ "Disposable": false, "Public_Email_Domain": false, "Role": false, "Verification_Failure_Code": null, "Verification_Failure_Reason": null, "Verified": true }
API Errors
{ "errorCode": xxxx, "errorMessage": "xxx" }
Error Code | Description | Resolution |
---|---|---|
4076 |
API key is missing or invalid. |
Check the API Key, you can get the correct API Key from the "Credentials" section of "My Addresser" portal. |
4077 |
Invalid Method or API URL. |
You have used an incorrect URL. Check the URL from the API documentation. |
4080 |
You have exceeded the allowed API calls. |
You have reached the maximum limit of API calls on your current plan. You can choose to add additional quota via Pricing page of the Addresser website. |
422 |
Email is missing or empty |
Parameter 'email' is missing or empty. |
500 |
Internal Server Error. |
{ "errorCode": 4076, "errorMessage": "API key is missing or invalid." }
Response Specification
Field | Type | Description | Example |
---|---|---|---|
Disposable | String |
This attribute indicates whether the email address is from a disposable email provider. false means the email address is not disposable, suggesting it is likely to be a more permanent and legitimate address. |
false |
Public_Email_Domain | String |
This attribute checks if the email address is registered under a public domain (like gmail.com or yahoo.com). false means the email is not from a public email domain, potentially indicating it's from a private or corporate domain. |
false |
Role | String |
This attribute identifies if the email address is associated with a role or position (like support@ or info@) rather than an individual. false indicates the email is likely registered to an individual rather than a role-based account, which can be crucial for personalization and targeting in communication. |
false | Verification_Failure_Code | String |
This field provides a specific code if the email verification fails, helping to identify the reason for failure. null suggests that there was no failure in the email verification process. |
One of the following codes:
REQUEST_TIMEOUT FORMAT_INVALID EMAIL_ACCOUNT_MISSING CONNECTION_FAILED DNS_TIMEOUT DNS_RECORD_MISSING |
Verification_Failure_Reason | String |
Similar to the failure code, this field explains the reason why an email verification might fail. null indicates there was no error during the verification process. |
One of the following reasons: 1. Request timed out 2. The email format is incorrect 3. The email account does not exist 4. Failed to connect after retries or Connection attempt failed 5. DNS resolution timed out 6. The domain is not configured to accept email |