Skip to content

// email marketing and newsletters

Via API

Omnisend email verification with pingutil

Omnisend signup forms and popups collect emails for discounts, and plenty of them are disposable or mistyped, which hurts the welcome series and every campaign after it. A webhook action in your automation workflow posts the contact's email to your endpoint, pingutil verifies it, and the Omnisend contacts API adds tags and sets invalid addresses to unsubscribed.

Where it connects: Omnisend automation workflow webhook action (sendWebhook block) plus the API v5 create or update contact endpoint

What goes wrong without it

  • Our welcome discount is the most-bounced email we send, because so many popup signups use temp-mail.
  • Store owners on our team keep asking why the subscriber count grows while revenue per email drops.
  • We have no way to spot mistyped emails until the order confirmation bounces.

What you can do with Omnisend and pingutil

  • Verify at the start of the welcome series

    The webhook action runs first, then a delay and a split on the pingutil tag decide whether the discount email goes out.

  • Unsubscribe throwaway discount hunters

    Contacts with disposable or nonexistent addresses are set to unsubscribed for email, so they stop counting toward campaign sends.

  • Tag catch-all contacts for careful sending

    Risky results get a pingutil-risky tag you can exclude from large campaigns while keeping the contact for order emails.

Set it up

  1. 1

    Create an Omnisend API key with contacts write access and a pingutil API key.

  2. 2

    Deploy the endpoint below.

  3. 3

    In your welcome automation, add a webhook action as the first step, set the HTTPS callback URL, add an X-Webhook-Secret header, and use the JSON body from the snippet comment with the [[contact.email]] tag.

  4. 4

    Add a delay after the webhook and a split on the pingutil tags before the discount email.

  5. 5

    Enable the automation and sign up through your popup with a test address.

Endpoint for the Omnisend automation webhook
// Omnisend webhook action body: { "email": "[[contact.email]]" }
// Custom header: X-Webhook-Secret: <secret>
import express from 'express';

const app = express();
app.use(express.json());

async function verify(email: string) {
  try {
    const res = await fetch('https://pingutil.com/v1/verify', {
      method: 'POST',
      headers: { Authorization: 'Bearer ' + process.env.PINGUTIL_KEY, 'Content-Type': 'application/json' },
      body: JSON.stringify({ email }),
      signal: AbortSignal.timeout(30000),
    });
    return res.ok ? await res.json() : null;
  } catch {
    return null; // fail open
  }
}

async function handle(email: string) {
  const v = await verify(email);
  if (!v) return;
  const identifier: Record<string, unknown> = { type: 'email', id: email };
  if (v.status === 'invalid') identifier.channels = { email: { status: 'unsubscribed' } };

  await fetch('https://api.omnisend.com/v5/contacts', {
    method: 'POST', // creates or updates the contact
    headers: { 'X-API-KEY': process.env.OMNISEND_API_KEY!, 'Content-Type': 'application/json' },
    body: JSON.stringify({
      identifiers: [identifier],
      tags: ['pingutil-' + v.status],
      customProperties: { pingutil_reason: v.reason },
    }),
  });
}

app.post('/hooks/omnisend', (req, res) => {
  if (req.get('x-webhook-secret') !== process.env.HOOK_SECRET) return res.sendStatus(401);
  res.sendStatus(200);
  const email = String(req.body?.email ?? '');
  if (email.includes('@')) handle(email).catch(console.error);
});

app.listen(3000);

What to do with each result

pingutil resultAction in Omnisend
status: "invalid"Set channels.email.status to unsubscribed and tag pingutil-invalid.
reason: "disposable_domain"Invalid path; store pingutil_reason to measure popup abuse.
status: "risky"Tag pingutil-risky; exclude from large campaigns, keep for order-related emails.
status: "unknown"Tag pingutil-unknown and leave subscribed.

Limits to plan for

  • Webhooks in Omnisend automations are not available on the free plan, and the callback URL must be HTTPS on port 443 with a valid certificate.
  • Omnisend blocks a custom Content-Type header on webhook actions and sends JSON by default, so authenticate with your own header such as X-Webhook-Secret.
  • pingutil checks up to 300 addresses per account per day (3,000 a month). Popup-heavy stores may need Enterprise limits or the fast /v1/lookup screen. Those are Free plan limits.

Omnisend documentation

Omnisend is a trademark of its owner. This integration uses Omnisend's documented extension points; it is not an official Omnisend app.

Common questions

Which personalization tags can the webhook body use?
Omnisend documents tags such as [[contact.email]], [[contact.first_name]] and [[event.raw.<property>]]. The email tag is all pingutil needs.
Will unsubscribing invalid contacts affect SMS?
The snippet only sets the email channel status. SMS consent stays as it was.

Stop bad addresses in Omnisend today

Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your Omnisend setup will receive.