// sales engagement and cold email
Via APIApollo email verification with pingutil
Apollo shows its own email status for contacts from its database, but lists you bring in from events, scrapers or other vendors arrive unchecked. Verify those with pingutil, then create the contact through the Apollo API with a label that tells your team whether it is safe to sequence.
Where it connects: Apollo API, POST /api/v1/contacts (create a contact) with label_names, x-api-key header
What goes wrong without it
- We import event lists and partner leads into Apollo and they bounce at a much higher rate than Apollo-sourced contacts.
- Catch-all contacts look fine in the list view and then a share of them hard-bounce.
- Different reps trust different verification results and nobody knows which contacts are safe to sequence.
What you can do with Apollo and pingutil
Verify imported lists before they become contacts
Run an outside CSV through /v1/verify/batch and create only valid contacts with the Apollo create-contact endpoint, labelled so sequences can target them.
Second check before a high-value sequence
Export the contacts you are about to sequence, verify them, and remove invalid ones from the list. Useful when the stored status is old.
Keep catch-all contacts in their own list
Use label_names to put accept_all contacts in a separate list so they can go into a lower-volume sequence.
Set it up
- 1
Create an Apollo API key with access to the create-contact endpoint (or a master key), and a pingutil API key.
- 2
Verify the list with POST https://pingutil.com/v1/verify/batch, 50 addresses per call.
- 3
Choose a label per outcome, for example "Verified" for valid and "Catch-all" for risky / accept_all.
- 4
Create each kept contact with POST https://api.apollo.io/api/v1/contacts, sending email, names, organization_name and label_names.
- 5
Set run_dedupe to true if the contact might already exist, so Apollo updates it instead of creating a duplicate.
- 6
Build your sequence from the "Verified" list.
// Node 18+. Env: PINGUTIL_KEY, APOLLO_API_KEY
type Row = { email: string; first_name?: string; last_name?: string; organization_name?: string };
const LABEL: Record<string, string | null> = {
valid: 'Verified',
accept_all: 'Catch-all',
unknown: 'Verify again',
invalid: null, // do not create
};
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 }[];
}
export async function importToApollo(rows: Row[]) {
for (let i = 0; i < rows.length; i += 50) {
const chunk = rows.slice(i, i + 50);
let results: { status: string; reason: string }[];
try {
results = await verifyBatch(chunk.map((r) => r.email));
} catch {
results = chunk.map(() => ({ status: 'unknown', reason: 'smtp_unavailable' })); // fail open to a review label
}
for (let j = 0; j < chunk.length; j++) {
const r = results[j];
const key = r.reason === 'accept_all' ? 'accept_all' : r.status;
const label = LABEL[key] ?? null;
if (!label) continue;
const res = await fetch('https://api.apollo.io/api/v1/contacts', {
method: 'POST',
headers: { 'x-api-key': process.env.APOLLO_API_KEY!, 'content-type': 'application/json' },
body: JSON.stringify({ ...chunk[j], label_names: [label], run_dedupe: true }),
});
if (res.status === 429) throw new Error('Apollo rate limit, resume later');
}
}
}What to do with each result
| pingutil result | Action in Apollo |
|---|---|
| status: valid | Create the contact with the "Verified" label and sequence it. |
| status: invalid | Do not create it. |
| status: risky, reason: accept_all | Create with a "Catch-all" label for a lower-volume sequence. |
| status: risky, reason: role_based | Skip for cold email, or route to a different play. |
| status: unknown | Create with a "Verify again" label and re-check before sequencing. |
Limits to plan for
- Apollo does not deduplicate on create unless you set run_dedupe; with it on, a match updates the existing contact and overwrites the fields you send.
- Apollo returns 429 when you exceed its API rate limit; limits depend on your plan.
- pingutil checks 300 addresses per account per day (3,000 a month) and reports catch-all domains as risky, never valid. Those are Free plan limits; Enterprise has custom limits.
Apollo documentation
Apollo is a trademark of its owner. This integration uses Apollo's documented extension points; it is not an official Apollo app.
Common questions
- Apollo already shows an email status. Why verify again?
- For contacts from Apollo data, its status may be enough. The check matters most for lists you import from elsewhere, which have no status, and for records whose status is old. pingutil gives a fresh result with a reason code at the moment you check.
- Does pingutil update the email status field in Apollo?
- No. The snippet records the result as a label on the contact. Apollo manages its own email status field.
Stop bad addresses in Apollo 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 Apollo setup will receive.