Email Validation
The email validation endpoint provides a way to verify if an email address follows the correct structural format according to RFC 5322 standards. This validation focuses solely on the syntax and structure of the email address - confirming elements like the presence of an @ symbol, valid domain format, and proper character usage.
Email validation is a critical component of data quality assurance, helping to catch basic formatting errors before they enter your system. While structural validation cannot guarantee an email address is active or reachable, it serves as an essential first line of defense against obvious formatting errors.
IMPORTANT
This validation performs ONLY syntactic pattern matching of the email address structure and does not verify the actual existence or functionality of the email account. A successful validation only confirms that the email address follows the correct format (e.g., contains "@", valid character sets, proper domain structure).
A "valid" result should NOT be interpreted as confirmation that emails sent to this address will be delivered or received. For mission-critical systems requiring guaranteed email deliverability, additional verification steps such as DNS checks, mailbox verification, or email confirmation workflows must be implemented separately.
Model
Specific structure of the data that represents the entity within the API. It defines the attributes and their data types associated with the entity.
It's important to note that you'll need to retrieve the complete identifier for an entity each time you require its complete model. This can be achieved by utilizing the find endpoint to locate the entity and then using the retrieved identifier to call the retrieve endpoint for complete model.
- Name
email- Type
- string
- Name
domain- Type
- object
- Description
- Name
mailbox- Type
- string
- Name
name- Type
- string
- Name
tld- Type
- string
- Name
isValid- Type
- boolean
Validate
This endpoint analyzes an email address to verify its structural validity according to RFC 5322 standards. It performs checks including:
- Presence and proper placement of the @ symbol
- Valid characters in local-part (before @) and domain (after @)
- Proper domain name formatting
- Valid top-level domain structure
Mandatory headers
- Name
x-api-key- Type
- string
- Description
- A valid API key obtained through active subscription must be included in the header in order for the endpoint to work.
Required parameters
- Name
email- Type
- string
- Description
- The email address to validate.
Request
curl "https://api.vigil.sh/validate/email/?email=user@example.com" \
-H 'x-api-key: {api-key}'
Response
{
"result": {
"email": "user@example.com",
"domain": {
"mailbox": "user",
"name": "example.com",
"tld": "com"
},
"isValid": true
}
}