Skip to content

// sales engagement and cold email

Via API

Reply.io email verification with pingutil

Reply.io sequences pull contacts from imports, the Chrome extension and the API, and invalid addresses that slip in cost you bounces and sender health. When you add contacts through the v3 API, verify them with pingutil first, create only the ones you want to mail, and store the result in a custom field.

Where it connects: Reply.io API v3, POST /v3/contacts then POST /v3/contacts/{id}/move-to-sequence

What goes wrong without it

  • Contacts from our sync job go straight into sequences and nobody checks them first.
  • We want one check that runs before contacts reach any of our client workspaces.
  • Catch-all and role addresses keep landing in our main sequence.

What you can do with Reply.io and pingutil

  • Verify before create

    Your job calls pingutil, then POST /v3/contacts for addresses you keep. Invalid addresses never become contacts.

  • Record the result in a custom field

    Send customFields with a pingutil_status key so Reply.io filters and reports can use it.

  • Send catch-all contacts to a separate sequence

    Move accept_all contacts into a sequence with fewer email steps and more calls or LinkedIn touches.

Set it up

  1. 1

    Create a Reply.io API key with contacts:write and contacts:operate scopes, and a pingutil API key.

  2. 2

    Verify each address with POST https://pingutil.com/v1/verify, or 50 at a time with /v1/verify/batch.

  3. 3

    Create kept contacts with POST https://api.reply.io/v3/contacts and an Authorization: Bearer header.

  4. 4

    Move the new contact into the right sequence with POST /v3/contacts/{id}/move-to-sequence and a sequenceId.

  5. 5

    Back off when Reply.io returns 429 and respect its Retry-After header.

Verify, create a Reply.io contact, move it to a sequence
// Node 18+. Env: PINGUTIL_KEY, REPLY_API_KEY, MAIN_SEQUENCE_ID, CATCHALL_SEQUENCE_ID
const reply = (path: string, body: unknown) =>
  fetch('https://api.reply.io' + path, {
    method: 'POST',
    headers: { authorization: 'Bearer ' + process.env.REPLY_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 addToSequence(c: { email: string; firstName?: string; lastName?: string; company?: string }) {
  const v = await verify(c.email);
  if (v?.status === 'invalid') return { added: false, reason: v.reason };
  if (!v || v.status === 'unknown') return { added: false, reason: 'retry_later' }; // hold, re-check later

  const created = await reply('/v3/contacts', {
    ...c,
    customFields: [{ key: 'pingutil_status', value: v.reason === 'accept_all' ? 'catch_all' : v.status }],
  });
  if (!created.ok) throw new Error('Reply.io create ' + created.status);
  const { id } = await created.json();

  const sequenceId = Number(v.status === 'valid' ? process.env.MAIN_SEQUENCE_ID : process.env.CATCHALL_SEQUENCE_ID);
  const moved = await reply('/v3/contacts/' + id + '/move-to-sequence', { sequenceId });
  return { added: moved.status === 204, contactId: id };
}

What to do with each result

pingutil resultAction in Reply.io
status: validCreate the contact and move it to the main sequence.
status: invalidDo not create the contact.
status: risky, reason: accept_allCreate with pingutil_status catch_all and move to a sequence with fewer email steps.
status: unknownHold the contact and verify again in a few hours.

Limits to plan for

  • Reply.io v3 uses Bearer API keys with scopes; creating contacts needs contacts:write and moving them needs contacts:operate.
  • Reply.io returns 429 with Retry-After when you exceed its rate limit.
  • pingutil verifies 300 addresses per account per day (3,000 a month) and can only report catch-all addresses as risky. Those are Free plan limits; Enterprise has custom limits.

Reply.io documentation

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

Common questions

Reply.io has email validation built in. Is this a replacement?
Not necessarily. Reply.io can validate contacts manually or automatically when they are added to a sequence, using its validation credits. pingutil runs before the contact exists in Reply.io, which suits teams that verify once upstream for several tools.
Can I verify contacts already in Reply.io?
Export them to CSV, verify the file with /v1/verify/batch or the pingutil dashboard (50 rows per upload), then remove or mark the invalid ones in Reply.io.

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