Email Validator & Disposable Checker API
Description
Validate an email
and check if it belongs to a disposable email provider from our list of 150 000+ tracked services. This endpoint does NOT check if an email
is actively in use as doing so would be next to impossible to do reliably.
Endpoint
> GET https://api.jsonrepo.com/v1/compute/validator/email
Headers
Field | Description |
---|---|
api_key | Required Your API Key |
Parameters
Field | Type | Description |
---|---|---|
String | Required Email to examine |
Important Note:
The only way we can probabilistically determine that an email comes from a disposable service provider is if it matches one of our database entries. An email can be both
valid
ANDthrowaway
or vice versa. We currently track 150 000+ different disposable email providers.
Response
A successful request will result in a populated payload
field with the expected output.
A failed request will result in an error output as detailed in Error Rules. If the endpoint validation fails due to missing, badly formatted or invalid parameters, the endpoint will return HTTP code 400
along with a message
detailing the error.
See the examples section for more information.
Request
- Curl
// validate `email=contact@jsonrepo.com`
curl -G \
https://api.jsonrepo.com/v1/compute/validator/email \
-H "api_key: {YOUR_API_KEY_HERE}" \
--data-urlencode "email=contact@jsonrepo.com"
Success Response
{
"http_code": 200,
"http_message": "Ok",
"message": "Successful execution",
"payload": {
"email": {
"input": "contact@jsonrepo.com",
"domain": "jsonrepo.com",
"is_valid": true,
"is_disposable": false
}
}
}
Error Response Examples
// Request with no `email` parameter provided
{
"http_code": 400,
"http_message": "Bad Request",
"message": "Malformed request: email parameter was not provided",
"payload": []
}