MailWizz + VerifyAnyEmail

Setup

1. 1
   Export or read subscribers

   Use MailWizz’s own API to pull subscribers for a list, or hook into subscriber creation.

2. 2
   Verify each address

   Call POST /v1/verify with X-VAE-Source: mailwizz for each email (or use the batch endpoint for large lists).

3. 3
   Act on the result

   Unsubscribe or mark as “unconfirmed” any subscriber whose status is undeliverable, so they’re excluded from future campaigns.

$ch = curl_init('https://api.verifyany.email/v1/verify');
curl_setopt_array($ch, [
  CURLOPT_POST => true,
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_HTTPHEADER => [
    'Authorization: Bearer YOUR_API_KEY',
    'Content-Type: application/json',
    'X-VAE-Source: mailwizz',
  ],
  CURLOPT_POSTFIELDS => json_encode(['email' => $email]),
]);
$data = json_decode(curl_exec($ch), true);
$status = $data['result']['status']; // deliverable | undeliverable | risky | unknown

Handling the result

Every verification returns a result object with a status, a 0–100 score and a “did you mean” suggestion for typos. Branch on the status:

For sign-up and checkout forms, the safe default is to block only undeliverable so you never turn away a real customer, and to surface the suggestion (“did you mean gmail.com?”) inline to recover typos.

Security & reliability

• Keep your API key server-side. Never expose it in client-side JavaScript. In MailWizz, store it in the integration’s credential/secret store, not in a shared script.
• Fail open. If the API errors or times out, let the address through rather than blocking a real user over a transient issue.
• Retry transient errors. Back off and retry on 429 (rate limit) and 5xx; don’t retry 4xx validation errors.
• Cache per address. One credit is spent per unique verification — cache results (e.g. 12–24h) so re-submits don’t re-charge.
• Tag the source. This recipe sends X-VAE-Source: mailwizz so your dashboard shows where verifications come from.

Troubleshooting

This is an API recipe, not a one-click app — you wire it up once with the steps above. See the full API reference for every field and error code.