Skip to content

// website builders and cms

Via API

Outseta email verification with pingutil

Outseta runs signup, billing and email for many small SaaS and membership sites, so a fake signup lands in your CRM, your email lists and your trial numbers at once. Outseta does not document a way to reject a signup from your server, so the check runs right after: the Account Created notification posts the account and its people to your endpoint, pingutil verifies each email, and the Outseta API stores the result on the person.

Where it connects: Outseta activity notification (Settings > Notifications, Account Created) with a SHA256 webhook signature

What goes wrong without it

  • Trial signups on Outseta keep coming from disposable inboxes and the same people come back for another trial.
  • Our Outseta email lists have addresses that bounce on the first broadcast.
  • I cannot tell which new accounts are real companies without opening each one.

What you can do with Outseta and pingutil

  • Tag people with their email status

    Write status and reason to a custom person property, then build Outseta segments or filters on it to keep invalid addresses out of broadcasts.

  • Catch repeat trial abuse

    Disposable and randomized addresses come back as invalid or risky. Review those accounts before their trial converts or hands out credits.

  • Flag business accounts

    Run /v1/lookup on the primary person's email and store category and company.name, so sales can see which new accounts are companies.

Set it up

  1. 1

    Generate a 32-byte hex key (openssl rand -hex 32) and set it as the Webhook Signature Key under Settings > Notifications.

  2. 2

    Add a custom property to people (for example EmailStatus) to hold the result.

  3. 3

    Under Settings > Notifications, click Add Notification, choose the Account Created activity and enter your endpoint URL.

  4. 4

    In the endpoint, check x-hub-signature-256 against an HMAC-SHA256 of the raw body, answer 200, then verify each person in PersonAccount.

  5. 5

    Write the result back with PUT /api/v1/crm/people/{personUid} using the Outseta {api_key}:{api_secret} authorization header.

Express endpoint for the Outseta Account Created notification
import crypto from 'node:crypto';
import express from 'express';

const app = express();
const OUTSETA = 'https://' + process.env.OUTSETA_SUBDOMAIN + '.outseta.com/api/v1';

function validSignature(signature, rawBody) {
  const key = Buffer.from(process.env.OUTSETA_SIGNATURE_KEY, 'hex');
  const expected = 'sha256=' + crypto.createHmac('sha256', key).update(rawBody).digest('hex');
  return signature.length === expected.length && crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
}

async function verifyEmail(email) {
  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(25_000),
    });
    return res.ok ? await res.json() : null; // 429 / 5xx: fail open
  } catch {
    return null;
  }
}

async function screenAccount(account) {
  for (const { Person } of account.PersonAccount ?? []) {
    const result = await verifyEmail(Person.Email);
    if (!result) continue; // check skipped: leave the person untouched
    await fetch(OUTSETA + '/crm/people/' + Person.Uid, {
      method: 'PUT',
      headers: {
        authorization: 'Outseta ' + process.env.OUTSETA_API_KEY + ':' + process.env.OUTSETA_API_SECRET,
        'content-type': 'application/json',
      },
      // EmailStatus is the system name of your custom person property
      body: JSON.stringify({ Uid: Person.Uid, Email: Person.Email, EmailStatus: result.status + ':' + result.reason }),
    });
  }
}

app.post('/webhooks/outseta', express.raw({ type: 'application/json' }), (req, res) => {
  const raw = req.body.toString('utf8');
  if (!validSignature(req.get('x-hub-signature-256') ?? '', raw)) return res.status(401).end();
  res.status(200).end(); // Outseta retries errors 20 times, 20 minutes apart
  screenAccount(JSON.parse(raw)).catch((err) => console.error('outseta screen failed', err));
});

app.listen(3000);

What to do with each result

pingutil resultAction in Outseta
status: "invalid"Set EmailStatus to invalid and exclude the person from lists and broadcasts.
status: "risky" (accept_all, role_based, randomized_local_part)Set EmailStatus to risky and review the account before the trial converts.
status: "valid"Set EmailStatus to valid.
No result (timeout, 429, 5xx)Leave the person untouched; re-check later from a scheduled job.

Limits to plan for

  • The Account Created notification fires after the account and person exist, and it also fires for accounts admins create by hand. Outseta also has a Sign Up Callback URL, but its docs do not say it can reject a signup, so treat both as post-signup.
  • Outseta retries a failed notification 20 times at 20-minute intervals, so a slow or failing endpoint means repeated deliveries; make the handler safe to run twice.
  • Each person checked counts toward pingutil's 300 verified addresses a day (3,000 a month). Those are Free plan limits; Enterprise has custom limits.

Common questions

Account Created or the Sign Up Callback URL?
The Sign Up Callback URL only fires on registrations and sends Person, Account and Subscription together. Account Created fires for every new account. Either works as the trigger; this example uses Account Created so admin-created accounts are checked too.
How do I find the custom property name?
Use the property's system name, the same key you see when you GET a person through the API. Custom properties are written the same way they are returned.

Stop bad addresses in Outseta 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 Outseta setup will receive.