Free Tools

API Documentation

Email Validation API. Validate email addresses in real time; each check consumes 1 credit. This documentation is public so you can evaluate the API before signing up.

Base URL

https://api.aimailtools.com

Authentication

All requests require an API key sent in the header:

X-API-Key: your_api_key

You get API keys after registering and verifying your email, in My API keys. Each key can have its own rate and daily limits.

Security (for you): Never expose your API key in client-side code (JavaScript, mobile apps, or public repos). Call our API only from your server or backend. If a key is leaked, revoke it immediately in My API keys and create a new one.

Validate email

POST /check

Request body (JSON):

{"email": "[email protected]"}

Success response (200):

{
  "email": "[email protected]",
  "status": "good",
  "reason": null,
  "took_ms": 42
}

Invalid/risky email (200):

{
  "email": "[email protected]",
  "status": "bad",
  "reason": "No MX record",
  "took_ms": 15
}

status is good or bad. reason explains the result when applicable.

Rate limits

Each API key has:

Requests per minute (RPM): limit per minute; excess requests are rejected with HTTP 429.
Daily limit: maximum requests per day; excess requests are rejected with HTTP 429.

Responses include standard HTTP headers where applicable (e.g. rate limit info). If you need higher limits, contact support.

Credits

Each successful validation consumes 1 credit from your account balance. When balance is zero, the API returns an error. Top up via the dashboard or contact support.

Errors

401 Unauthorized: Missing or invalid X-API-Key.
429 Too Many Requests: Rate limit (RPM or daily) exceeded.
402 Payment Required / 4xx: Insufficient credits or key inactive.
400 Bad Request: Invalid body (e.g. missing email or invalid JSON).

Health check

GET / — No authentication. Returns service status (e.g. 200 OK). Use for monitoring only, not for validation.

Our commitment (security & fairness)

We log API usage (key, endpoint, timestamp) for abuse prevention, support, and billing. We do not sell your data. Keys can be revoked at any time. Do not share keys; create separate keys per environment or application. By using the API you agree to use it fairly and not to circumvent rate limits or abuse the service.