Keep lists clean as they age

Schedule re-checks for addresses that have not been checked recently, and verify new contacts as they arrive.

Get started free List hygiene guide

Fig. 1Re-check schedule

Trigger: A result older than your limit
Limit: Set in days, per workspace
Runs: In batches, on a schedule
Status: GET /v1/reverification/status

§ 1

Why it matters

Every list decays

People leave companies, and mailboxes close. A list you cleaned once slowly fills with addresses that will bounce.

A list that was clean in January is not clean in June. Re-checks catch the change before you send.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: Results get old while people change jobs.With Verifier: You set the age limit in days for the workspace.
Without: A list that was clean in spring bounces in autumn.With Verifier: Older results are checked again in batches.
Without: Someone must remember to check the list again.With Verifier: The status shows the last run and the next run.

§ 2

How it works

Re-check on a schedule

Choose how old a result can be. Addresses older than that are checked again automatically.

2.1Set how many days a result stays fresh.
2.2We re-check stale addresses in batches.
2.3Review what changed, and suppress what went bad.

Fig. 3Turn on re-checks

PUT /v1/reverification

{  "enabled": true,  "staleness_days": 30,  "batch_size": 100}

GET /v1/reverification/status

{  "enabled": true,  "staleness_days": 30,  "batch_size": 100,  "next_run_at": "2026-10-16T10:00:00Z"}

Status fields trimmed

§ 3

What you get

What you get.

3.1Pipelines for new contactsPush new contacts to a pipeline through the API, and each one is checked before it reaches your email platform. The API comes with Professional and Enterprise.
3.2Results delivered to youGet results by webhook when a run finishes.

§ 4

In practice

Typical uses.

Case 4.1
Monthly hygiene
Re-check every address older than 30 days before your monthly newsletter.

Works with the tools you send from.

All integrations

Questions

Before you start.

Do re-checks use my monthly checks?

Yes. Each re-checked address counts as one check.

Every list decays

People leave companies, and mailboxes close. A list you cleaned once slowly fills with addresses that will bounce.

A list that was clean in January is not clean in June. Re-checks catch the change before you send.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: Results get old while people change jobs.With Verifier: You set the age limit in days for the workspace.
Without: A list that was clean in spring bounces in autumn.With Verifier: Older results are checked again in batches.
Without: Someone must remember to check the list again.With Verifier: The status shows the last run and the next run.

Re-check on a schedule

Choose how old a result can be. Addresses older than that are checked again automatically.

2.1Set how many days a result stays fresh.
2.2We re-check stale addresses in batches.
2.3Review what changed, and suppress what went bad.

Fig. 3Turn on re-checks

PUT /v1/reverification

{  "enabled": true,  "staleness_days": 30,  "batch_size": 100}

GET /v1/reverification/status

{  "enabled": true,  "staleness_days": 30,  "batch_size": 100,  "next_run_at": "2026-10-16T10:00:00Z"}

Status fields trimmed

From a raw listto a safe send.

Keep lists clean as they age

Every list decays

Re-check on a schedule

What you get.

Typical uses.

Works with the tools you send from.

Before you start.

From a raw listto a safe send.

Keep lists clean as they age

Every list decays

Re-check on a schedule

What you get.

Typical uses.

Works with the tools you send from.

Before you start.