// sales engagement and cold email
Via APIInstantly email verification with pingutil
Instantly makes it easy to load thousands of leads and mail them from many accounts, which also makes it easy to bounce at scale. Verify each lead with pingutil, then create only the ones you want to mail through the Instantly v2 leads endpoint with the result stored in custom_variables.
Where it connects: Instantly API v2, POST /api/v2/leads (create lead in a campaign)
What goes wrong without it
- A list from a lead database looked clean, then the campaign bounced hard and Instantly started pausing our accounts.
- We run several workspaces for clients and want one verification step before leads go into any of them.
- Catch-all addresses are a large share of every B2B list and we do not know how hard to push them.
What you can do with Instantly and pingutil
Verify leads before an API import
Your script verifies each address with pingutil, then creates the lead with campaign, email and names. Leads that would bounce are never created.
Tag leads with the verification result
Write status and score into custom_variables so you can filter, personalize or report on them inside Instantly later.
Split catch-all leads into a cautious campaign
Create accept_all leads in a separate campaign with lower volume, and keep the main campaign on valid addresses only.
Set it up
- 1
Create a pingutil API key, and an Instantly API v2 key with the leads:create (or broader) scope.
- 2
Load your list and verify it with POST https://pingutil.com/v1/verify/batch, 50 addresses at a time.
- 3
Decide per status: valid to the main campaign, risky / accept_all to a catch-all campaign, invalid dropped, unknown retried later.
- 4
Create each kept lead with POST https://api.instantly.ai/api/v2/leads, passing campaign, email, names and custom_variables.
- 5
Set skip_if_in_workspace to true so leads already in another campaign are not added twice.
// Node 18+. Env: PINGUTIL_KEY, INSTANTLY_API_KEY, MAIN_CAMPAIGN_ID, CATCHALL_CAMPAIGN_ID
type Row = { email: string; first_name?: string; last_name?: string; company_name?: string };
async function verify(emails: string[]) {
try {
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) return null;
return (await res.json()).results as { status: string; reason: string; score: number }[];
} catch {
return null; // fail open to "unchecked", never to "send"
}
}
async function createLead(row: Row, campaign: string, status: string, score: number) {
const res = await fetch('https://api.instantly.ai/api/v2/leads', {
method: 'POST',
headers: { authorization: 'Bearer ' + process.env.INSTANTLY_API_KEY, 'content-type': 'application/json' },
body: JSON.stringify({
campaign,
email: row.email,
first_name: row.first_name ?? null,
last_name: row.last_name ?? null,
company_name: row.company_name ?? null,
skip_if_in_workspace: true,
custom_variables: { pingutil_status: status, pingutil_score: score },
}),
});
if (res.status === 429) throw new Error('Instantly rate limit, slow down');
}
export async function importRows(rows: Row[]) {
const unchecked: Row[] = [];
for (let i = 0; i < rows.length; i += 50) {
const chunk = rows.slice(i, i + 50);
const results = await verify(chunk.map((r) => r.email));
if (!results) { unchecked.push(...chunk); continue; }
for (let j = 0; j < chunk.length; j++) {
const r = results[j];
if (r.status === 'valid') await createLead(chunk[j], process.env.MAIN_CAMPAIGN_ID!, r.status, r.score);
else if (r.reason === 'accept_all') await createLead(chunk[j], process.env.CATCHALL_CAMPAIGN_ID!, r.status, r.score);
else if (r.status === 'unknown') unchecked.push(chunk[j]);
}
}
return unchecked; // verify these again later
}What to do with each result
| pingutil result | Action in Instantly |
|---|---|
| status: valid | Create the lead in the main campaign. |
| status: invalid | Do not create the lead. Log the reason (mailbox_not_found, no_mx, disposable_domain) for the list vendor. |
| status: risky, reason: accept_all | Create in a catch-all campaign with lower volume. |
| status: risky, reason: role_based | Skip for cold outreach. info@ and sales@ inboxes rarely reply and often complain. |
| status: unknown | Keep out of Instantly for now and verify again in a few hours. |
Limits to plan for
- pingutil defaults are 60 requests per minute and 300 verified addresses per day (3,000 a month) per account. Large lists need several days or Enterprise limits. Those are Free plan limits.
- Instantly custom_variables accept strings, numbers, booleans or null only, and the leads schema rejects unknown properties.
- Instantly returns 429 when you exceed its API rate limit; its docs do not publish a fixed number on the create-lead page.
Instantly documentation
- developer.instantly.ai/api-reference/lead/create-lead
- help.instantly.ai/en/articles/9245059-verifying-leads
Instantly is a trademark of its owner. This integration uses Instantly's documented extension points; it is not an official Instantly app.
Common questions
- Instantly can verify leads on upload. Do I still need this?
- Not necessarily. Instantly has a Verify leads option at upload and a verify_leads_on_import flag in its API, billed in Instantly credits. pingutil is useful when you want the check outside Instantly, for example in a pipeline that also feeds your CRM, or a second opinion with a reason code per address.
- Can pingutil confirm catch-all addresses?
- No. A catch-all server says yes to every address, so we return risky with reason accept_all instead of rounding it up to valid.
Stop bad addresses in Instantly 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 Instantly setup will receive.