Skip to content

// sales engagement and cold email

Via API

Klenty email verification with pingutil

Klenty cadences start emailing as soon as a prospect is added, so a bad address bounces on day one. Verify the email with pingutil, create the prospect with a tag that records the result, and only start the cadence for addresses you trust.

Where it connects: Klenty API, POST /apis/v1/user/{userEmail}/prospects then POST /apis/v1/user/{userEmail}/startcadence

What goes wrong without it

  • Prospects from our CRM sync start a cadence the moment they arrive, verified or not.
  • Our bounce rate jumps every time a rep uploads a list they found themselves.
  • We want catch-all prospects in Klenty but not in the email-heavy cadence.

What you can do with Klenty and pingutil

  • Verify, create, then start the cadence

    Three calls per prospect: pingutil verify, Klenty create prospect, Klenty startcadence, with the last one skipped when the address is not valid.

  • Tag by verification result

    Klenty Tags take pipe-separated values, so you can add pingutil-valid or pingutil-catchall alongside your own tags.

  • Pick the cadence by result

    Start valid prospects on the email cadence and catch-all prospects on a call-first cadence.

Set it up

  1. 1

    Generate the Klenty API key under Settings, Integrations, and create a pingutil API key.

  2. 2

    Verify the prospect's email with POST https://pingutil.com/v1/verify.

  3. 3

    Create the prospect with POST https://api.klenty.com/apis/v1/user/{userEmail}/prospects, adding a pingutil tag.

  4. 4

    For valid prospects, call /startcadence with Email and cadenceName. For catch-all, use a call-first cadence or none.

  5. 5

    Skip invalid prospects entirely, and retry unknown ones later.

Verify, create a Klenty prospect and start a cadence
// Node 18+. Env: PINGUTIL_KEY, KLENTY_API_KEY, KLENTY_USER (your Klenty login email)
const base = 'https://api.klenty.com/apis/v1/user/' + encodeURIComponent(process.env.KLENTY_USER!);
const klenty = (path: string, body: unknown) =>
  fetch(base + path, {
    method: 'POST',
    headers: { 'x-API-key': process.env.KLENTY_API_KEY!, 'content-type': 'application/json' },
    body: JSON.stringify(body),
  });

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(30_000),
    });
    return res.ok ? ((await res.json()) as { status: string; reason: string }) : null;
  } catch {
    return null;
  }
}

export async function addProspect(p: { Email: string; FirstName?: string; LastName?: string; Company?: string }) {
  const v = await verify(p.Email);
  if (v?.status === 'invalid') return { created: false, reason: v.reason };

  const label = !v ? 'pingutil-unchecked' : v.reason === 'accept_all' ? 'pingutil-catchall' : 'pingutil-' + v.status;
  const created = await klenty('/prospects', { ...p, Tags: label });
  if (!created.ok) throw new Error('Klenty ' + created.status);

  if (v?.status === 'valid') {
    await klenty('/startcadence', { Email: p.Email, cadenceName: 'Outbound - Email first' });
  } else if (v?.reason === 'accept_all') {
    await klenty('/startcadence', { Email: p.Email, cadenceName: 'Outbound - Call first' });
  }
  // unknown or unchecked: prospect exists, no cadence until it is verified again
  return { created: true, label };
}

What to do with each result

pingutil resultAction in Klenty
status: validCreate with a pingutil-valid tag and start the email cadence.
status: invalidDo not create the prospect.
status: risky, reason: accept_allCreate with pingutil-catchall and start a call-first cadence.
status: unknownCreate with a tag but do not start a cadence until a later check passes.

Limits to plan for

  • The Klenty API URL includes your Klenty login email, and the key goes in the x-API-key header.
  • Klenty's help center documents create, bulk create (up to 100) and start cadence; check the current docs for rate limits.
  • pingutil checks 300 addresses per account per day (3,000 a month) and cannot confirm mailboxes on catch-all domains. Those are Free plan limits; Enterprise has custom limits.

Klenty documentation

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

Common questions

Why not start the cadence for unknown results?
Unknown means the mail server did not give a clear answer (greylisting, timeouts, blocks). It is safer to check again a few hours later than to send into the unknown from a sales mailbox.
Can I use Zapier instead of code?
Yes. A Zap can call pingutil with a webhook step, filter on status, then use Klenty's Zapier actions. The logic is the same as the snippet.

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