Skip to content

Validate an Email

Use this endpoint to validate a single email address in real time before sending.
The API evaluates deliverability risk and returns a score, trust band, recommended action, and supporting insights.

Endpoint

POST https://validate.mx18.com/evapi/check-email

Request headers

x-api-key: <YOUR_MX18_API_KEY>
Content-Type: application/json

Request body

{
  "email": "exampleuser@gmail.com"
}

Request parameters

Field Type Required Description
email sring Yes Email address to be validated

Example request

curl -X POST https://validate.mx18.com/evapi/check-email \
  -H 'x-api-key: <<your_api_key>>'
  -H "Content-Type: application/json" \
  -d '{
    "email": "exampleuser@gmail.com"
  }'

Success response

{
  "email": "exampleuser@gmail.com",
  "score": 100,
  "trust_band": "high",
  "suggested_action": "send",
  "insights": {
    "is_catch_all": false,
    "disposable": false,
    "smtp_valid": true,
    "reputation": "good"
  }
}

Response fields (summary)

Field Description
score Overall email quality score (0–100)
trust_band Risk classification derived from the score
suggested_action Recommended next step: send, or do_not_send
insights Diagnostic signals used to compute the result

HTTP status codes

Status Description
200 OK Validation completed successfully
400 Bad Request Invalid request payload or malformed email
401 Unauthorized Missing or invalid API key
429 Too Many Requests Rate limit exceeded
500 Internal Server Error Unexpected server error

Usage notes

  • Validation is performed in real time.

  • No email is sent to the recipient during validation.

  • This endpoint is safe to use during signup flows and pre-send checks.

  • Results should be cached where appropriate to avoid repeated validations.

What’s next

  • Understanding the Response – interpret scores, trust bands, and insights

  • Best Practices – learn how to use validation effectively at scale

Need help? Contact Support or visit https://support.mx18.com