// sales engagement and cold email
Via APIMixmax email verification with pingutil
Mixmax sends sequences from each rep's own Gmail or Google Workspace mailbox, so bounces land on that rep's account and your company domain. Verify recipients with pingutil before your code adds them through the Mixmax recipients endpoint, and keep catch-all recipients out of high-volume sequences.
Where it connects: Mixmax API, POST /v1/sequences/{id}/recipients/ with the X-API-Token header
What goes wrong without it
- Bounces show up in the rep's own inbox and they stop trusting the list.
- We add recipients from Salesforce reports and some of those addresses have been dead for years.
- One rep's bad import makes the whole company domain look worse to Gmail.
What you can do with Mixmax and pingutil
Verify before adding recipients by API
Your script verifies the list in batches of 50, then adds only valid recipients to the sequence in one call.
Clean old CRM contacts before re-engagement
Contacts that have been sitting in a CRM for a year or more are the ones most likely to bounce. Verify them before a win-back sequence.
Pass the result as a variable
Send pingutil status as a recipient variable so it is on the record for reporting.
Set it up
- 1
Create a Mixmax API token in your Mixmax settings, and a pingutil API key.
- 2
Find the sequence ID in the URL while you edit the sequence.
- 3
Verify the recipients with POST https://pingutil.com/v1/verify/batch, 50 per call.
- 4
POST valid recipients to https://api.mixmax.com/v1/sequences/{id}/recipients/ with email and variables.
- 5
Check each recipient's status in the response; Mixmax returns 200 even when some recipients were not added.
// Node 18+. Env: PINGUTIL_KEY, MIXMAX_API_TOKEN, SEQUENCE_ID
type Recipient = { email: string; variables?: Record<string, string> };
async function verifyBatch(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),
});
return res.ok ? ((await res.json()).results as { status: string; reason: string }[]) : null;
} catch {
return null;
}
}
export async function addRecipients(list: Recipient[]) {
const toAdd: Recipient[] = [];
const skipped: string[] = [];
for (let i = 0; i < list.length; i += 50) {
const chunk = list.slice(i, i + 50);
const results = await verifyBatch(chunk.map((r) => r.email));
if (!results) { skipped.push(...chunk.map((r) => r.email)); continue; } // re-run these later
results.forEach((r, j) => {
if (r.status === 'valid') {
toAdd.push({ ...chunk[j], variables: { ...chunk[j].variables, 'Email Check': 'valid' } });
} else {
skipped.push(chunk[j].email);
}
});
}
const res = await fetch('https://api.mixmax.com/v1/sequences/' + process.env.SEQUENCE_ID + '/recipients/', {
method: 'POST',
headers: { 'X-API-Token': process.env.MIXMAX_API_TOKEN!, 'content-type': 'application/json' },
body: JSON.stringify({ recipients: toAdd, allowMissingVariables: true }),
});
if (!res.ok) throw new Error('Mixmax ' + res.status);
const { recipients } = await res.json();
const notAdded = recipients.filter((r: { status: string }) => r.status !== 'success');
return { added: recipients.length - notAdded.length, notAdded, skipped };
}What to do with each result
| pingutil result | Action in Mixmax |
|---|---|
| status: valid | Add to the sequence. |
| status: invalid | Skip, and update or remove the contact in your CRM. |
| status: risky, reason: accept_all | Skip in bulk sequences; let the rep send a single manual email if the account matters. |
| status: unknown | Skip for now and verify again later. |
Limits to plan for
- Mixmax accepts up to 5,000 recipients per request and returns 403 if your plan lacks the sequence activation feature.
- Mixmax recipients added by API always start at the first stage of the sequence.
- pingutil checks 300 addresses per account per day (3,000 a month), and verifying 50 slow mail servers in one batch can take a while, so run it as a background job. Those are Free plan limits; Enterprise has custom limits.
Mixmax documentation
Mixmax is a trademark of its owner. This integration uses Mixmax's documented extension points; it is not an official Mixmax app.
Common questions
- Can this run when a rep adds recipients in the Gmail sidebar?
- No. Mixmax does not call outside APIs when a rep adds recipients by hand. The check works when recipients are added through the API by your own script or an automation tool.
- Why add the result as a variable?
- It keeps a record of what was checked. Mixmax stores variables per recipient, so you can see which ones were verified when you review the sequence.
Stop bad addresses in Mixmax 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 Mixmax setup will receive.