Skip to content

// sales engagement and cold email

Via API

Outreach email verification with pingutil

In Outreach, every rep mails from the company domain, so a few bad imports raise the bounce rate for the whole team. Put pingutil in front of the code that creates prospects: verify the address, then create the prospect only if it is valid, and tag catch-all ones so reps know to go easy.

Where it connects: Outreach REST API v2 (JSON:API), POST /api/v2/prospects with an OAuth access token

What goes wrong without it

  • Reps import their own lists and our domain reputation pays for it.
  • Prospects bounce on step one, sit in sequences doing nothing, and skew our reply-rate reports.
  • Our enrichment job writes prospects into Outreach with no check that the mailbox exists.

What you can do with Outreach and pingutil

  • Gate your prospect sync

    If you sync leads from a warehouse, form or enrichment job into Outreach through the API, verify each address with pingutil in the same job and only create valid ones.

  • Label catch-all prospects

    Create accept_all prospects with a tag such as pingutil-catch-all, so reps can put them in a shorter sequence or call first.

  • Audit an existing list before a big push

    Export the prospects you plan to sequence, run them through /v1/verify/batch, and remove or opt out the invalid ones in Outreach before enrolling.

Set it up

  1. 1

    Register an Outreach OAuth app with prospect write access and store the access and refresh tokens.

  2. 2

    Create a pingutil API key in the dashboard.

  3. 3

    In the job that creates prospects, call POST https://pingutil.com/v1/verify (or /v1/verify/batch for 50 at a time).

  4. 4

    For valid results, POST the prospect to https://api.outreach.io/api/v2/prospects with Content-Type application/vnd.api+json.

  5. 5

    For risky / accept_all, create it with a tag your reps recognise. Skip invalid. Queue unknown for a retry.

Verify, then create an Outreach prospect
// Node 18+. Env: PINGUTIL_KEY. outreachToken is a current OAuth access token.
type Verification = { status: 'valid' | 'invalid' | 'risky' | 'unknown'; reason: string; score: number };

async function verifyEmail(email: string): Promise<Verification | null> {
  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(30_000), // slow mail servers can take up to ~25 s
    });
    return res.ok ? await res.json() : null;
  } catch {
    return null;
  }
}

export async function createProspect(
  outreachToken: string,
  p: { email: string; firstName?: string; lastName?: string },
) {
  const v = await verifyEmail(p.email);
  if (v?.status === 'invalid') return { skipped: true, reason: v.reason };

  const tags: string[] = [];
  if (!v) tags.push('pingutil-unchecked'); // pingutil unavailable: create, but flag it
  else if (v.reason === 'accept_all') tags.push('pingutil-catch-all');
  else if (v.status !== 'valid') tags.push('pingutil-' + v.status);

  const res = await fetch('https://api.outreach.io/api/v2/prospects', {
    method: 'POST',
    headers: {
      authorization: 'Bearer ' + outreachToken,
      'content-type': 'application/vnd.api+json',
    },
    body: JSON.stringify({
      data: {
        type: 'prospect',
        attributes: { emails: [p.email], firstName: p.firstName, lastName: p.lastName, tags },
      },
    }),
  });
  if (!res.ok) throw new Error('Outreach ' + res.status + ': ' + (await res.text()));
  return { skipped: false, prospect: await res.json() };
}

What to do with each result

pingutil resultAction in Outreach
status: validCreate the prospect and let it enter sequences normally.
status: invalidDo not create it. Send the address back to whoever supplied the list.
status: risky, reason: accept_allCreate with a pingutil-catch-all tag and use a shorter or call-first sequence.
status: unknownCreate with a pingutil-unknown tag, or hold it and verify again later.

Limits to plan for

  • Outreach requires OAuth for its REST API; access tokens in its example expire after 7,200 seconds and must be refreshed.
  • Requests without the application/vnd.api+json content type get a 415 from Outreach.
  • pingutil verification can take several seconds per address and is capped at 300 addresses a day (3,000 a month) per account, so verify in a background job, not while a rep waits. Those are Free plan limits; Enterprise has custom limits.

Outreach documentation

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

Common questions

Can I run this inside Outreach itself?
Outreach does not run your code. The check lives in whatever creates prospects through the API: your sync job, a serverless function, or an automation tool such as Zapier, Make or n8n.
What about prospects that are already in Outreach?
Export them, verify the file with /v1/verify/batch or the dashboard CSV upload (50 rows per file), then update or remove the invalid ones before your next push.

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