Skip to content

// sales engagement and cold email

Via API

Saleshandy email verification with pingutil

Saleshandy imports prospects straight into a sequence step, and its own verification is optional per import. If you verify upstream with pingutil, you import only the rows you mean to mail, tag catch-all ones, and can leave verifyProspects off for lists you already checked.

Where it connects: Saleshandy Open API, POST /v1/prospects/import-with-field-name with stepId (import into a sequence step)

What goes wrong without it

  • We rotate many sender accounts and a bad import still drags all of them down.
  • Our list builder sends CSVs from several sources and we want one rule for all of them.
  • Catch-all prospects get the same steps as everyone else and some bounce.

What you can do with Saleshandy and pingutil

  • Clean a CSV before the API import

    Verify the file in batches of 50 and send only the valid rows in prospectList to the sequence step.

  • Tag catch-all prospects on import

    Import accept_all rows in a second call with a catch-all tag, or into a different sequence.

  • Avoid paying twice for the same check

    For lists already verified with pingutil, set verifyProspects to false on the import. For others, you can keep Saleshandy's own check on.

Set it up

  1. 1

    Create a Saleshandy API key and find the stepId of the sequence step you import into. Create a pingutil API key.

  2. 2

    Verify the CSV with POST https://pingutil.com/v1/verify/batch, 50 rows per call.

  3. 3

    Build prospectList from valid rows using Saleshandy field names such as "Email", "First Name" and "Company".

  4. 4

    POST to https://open-api.saleshandy.com/v1/prospects/import-with-field-name with x-api-key, stepId, verifyProspects and conflictAction.

  5. 5

    Import accept_all rows in a separate call with a catch-all tag, and poll the import status with the returned requestId.

Import pingutil-verified prospects into a Saleshandy step
// Node 18+. Env: PINGUTIL_KEY, SALESHANDY_API_KEY, STEP_ID
type Row = { Email: string; 'First Name'?: string; 'Last Name'?: string; Company?: string };

async function verifyBatch(emails: string[]) {
  const res = await fetch('https://pingutil.com/v1/verify/batch', {
    method: 'POST',
    headers: { authorization: 'Bearer ' + process.env.PINGUTIL_KEY, 'content-type': 'application/json' },
    body: JSON.stringify({ emails }),
    signal: AbortSignal.timeout(120_000),
  });
  if (!res.ok) throw new Error('pingutil ' + res.status);
  return (await res.json()).results as { status: string; reason: string }[];
}

async function importRows(prospectList: Row[], tags: string[], verifyProspects: boolean) {
  if (prospectList.length === 0) return null;
  const res = await fetch('https://open-api.saleshandy.com/v1/prospects/import-with-field-name', {
    method: 'POST',
    headers: { 'x-api-key': process.env.SALESHANDY_API_KEY!, 'content-type': 'application/json' },
    body: JSON.stringify({ prospectList, stepId: process.env.STEP_ID, verifyProspects, conflictAction: 'overwrite', tags }),
  });
  if (!res.ok) throw new Error('Saleshandy ' + res.status);
  return (await res.json()).payload.requestId as string; // poll v1/prospects/import-status/{requestId}
}

export async function run(rows: Row[]) {
  const valid: Row[] = [], catchAll: Row[] = [], unchecked: Row[] = [];
  for (let i = 0; i < rows.length; i += 50) {
    const chunk = rows.slice(i, i + 50);
    try {
      const results = await verifyBatch(chunk.map((r) => r.Email));
      results.forEach((r, j) => {
        if (r.status === 'valid') valid.push(chunk[j]);
        else if (r.reason === 'accept_all') catchAll.push(chunk[j]);
        else if (r.status === 'unknown') unchecked.push(chunk[j]);
      });
    } catch {
      unchecked.push(...chunk);
    }
  }
  await importRows(valid, ['pingutil-valid'], false);      // already verified
  await importRows(catchAll, ['pingutil-catch-all'], false);
  await importRows(unchecked, ['pingutil-unchecked'], true); // fail open: let Saleshandy check these
}

What to do with each result

pingutil resultAction in Saleshandy
status: validImport into the step with a pingutil-valid tag.
status: invalidLeave out of the import.
status: risky, reason: accept_allImport with a pingutil-catch-all tag, or into a separate sequence.
unknown, or pingutil unavailableImport with verifyProspects true so Saleshandy checks them, or hold for a later pingutil run.

Limits to plan for

  • Saleshandy imports run asynchronously; you poll the import status with the returned requestId, and field names must already exist in your account.
  • Saleshandy's import accepts up to 100,000 prospects and 90 MB per request.
  • pingutil verifies 300 addresses per account per day (3,000 a month), so big lists take several days on the Free plan. Those are Free plan limits.

Saleshandy documentation

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

Common questions

Saleshandy verifies prospects itself. Should I turn that off?
Only for rows you already verified with pingutil, to avoid checking twice. For rows pingutil could not check, leaving verifyProspects on is a sensible fallback.
Where do I find the stepId?
It identifies the sequence step the prospects enter. Saleshandy's API reference lists endpoints to fetch sequences and their steps.

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