Email Validation AI Agent / LLM

# Email Validation API — Way2API®

- **Endpoint:** `POST https://app.way2api.com/api/v1/email/validate`
- **Auth:** `Authorization: Bearer YOUR_API_KEY` (or `X-API-Key: YOUR_API_KEY`)
- **Content-Type:** `application/json`
- **Category:** Utilities
- **Availability:** Available worldwide
- **Docs:** https://app.way2api.com/documentation/email-validation

## What it does

Email Validation API — checks whether an address can actually receive mail, without sending one. result is a single verdict you can switch on: valid, invalid, invalid_syntax, risky or unknown, with is_valid as the boolean shortcut and reason explaining a rejection. The domain block classifies the receiving domain — is_disposable (throwaway inbox), is_free (consumer webmail), is_spam, is_catch_all and is_valid — while the account block flags role addresses (info@, support@) and full mailboxes. Resolved mx_records are returned too. Built for signup gating, list hygiene and bounce-rate reduction.

## Request body (application/json)

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `email` | string | yes | Email address to validate, e.g. [email protected]. Max 254 characters. |

## Example request

```bash
curl -X POST https://app.way2api.com/api/v1/email/validate \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email":"[email protected]"}'
```

## Success response — 200

```json
{
    "status": "SUCCESS",
    "status_code": 200,
    "charged": true,
    "success": true,
    "message": "",
    "message_code": "OK",
    "order_id": "W2A1739512345abcdef01",
    "data": {
        "order_id": "W2A1739512345abcdef01",
        "result": {
            "email": "[email protected]",
            "result": "valid",
            "is_valid": true,
            "is_syntax_valid": true,
            "reason": "",
            "domain": {
                "name": "example.com",
                "is_valid": true,
                "is_disposable": false,
                "is_free": false,
                "is_spam": false,
                "is_catch_all": false
            },
            "account": {
                "is_role": false,
                "is_full_mailbox": false
            },
            "mx_records": [
                "mx1.example.com.",
                "mx2.example.com.",
                "mx3.example.com.",
                "mx4.example.com.",
                "mx5.example.com."
            ]
        }
    }
}
```

## Error response — 400

```json
{
    "status": "FAILED",
    "status_code": 400,
    "charged": false,
    "success": false,
    "message": "Please pass valid value for 'email' in body.",
    "message_code": "REQUEST_FAILED",
    "order_id": "W2A1739512345abcdef01",
    "data": {
        "order_id": "W2A1739512345abcdef01",
        "error_code": "External API Error"
    }
}
```

## Integration rules

- Every response is JSON carrying `status`, `status_code`, `charged`, `success`, `message`, `message_code` and (once a call reaches the provider) `order_id`. The verification payload is under `data.result`.
- `charged` (boolean) is the authority on billing. Do NOT infer it from the HTTP status: `422` is returned both for input we rejected (not charged) and for a lookup the provider ran and billed us for that returned a negative result (charged).
- `message_code` is a fixed vocabulary — branch on it instead of parsing `message`. Values: `OK`, `ACCEPTED`, `PROVIDER_NO_RESPONSE`, `VERIFICATION_FAILED`, `NO_RECORD_FOUND`, `INVALID_INPUT`, `REQUEST_FAILED`, `MISSING_API_KEY`, `INVALID_API_KEY`, `INSUFFICIENT_BALANCE`, `NO_API_ACCESS`, `NOT_FOUND`, `RATE_LIMITED`, `INTERNAL_ERROR`, `PROVIDER_UNAVAILABLE`.
- `success` reports the verification outcome; `status` reports the ORDER lifecycle (`SUCCESS`/`PENDING`/`FAILED`). They differ on a charged negative result: the order completed and was billed while the verification did not pass.
- A failed verification is still a successful HTTP call — the outcome lives in the response body, so do not treat `200` as "verified".
- Status codes: `200` result returned, `202` pending or provider did not respond (both charged — quote the `order_id`), `401` missing/invalid key, `402` insufficient balance, `403` no access to this service, `422` see `charged`, `429` rate limited (honour the `Retry-After` header), `503` temporarily unavailable.
- Rate limits are per API key, per service, on a 1-minute sliding window.
- Load the API key from an environment variable or secret store. Never hard-code it, never commit it, and never ship it in client-side code — calls must be made from your backend.