Check lists for the senders you serve

Verify customer lists through the API, keep each client's work apart, and use delivery feedback to stop repeat bounces.

Get started free API and SDKs

Fig. 1Quality gate

Sample uploads · threshold set by you

Gate: List quality before a send
Hold: Low-quality uploads for review
Notify: A webhook when a job is done
Plans: Enterprise for volume

§ 1

Why it matters

One bad list can hurt every sender

When customers share sending infrastructure, one dirty list can damage the reputation of all of them.

For platforms and agencies that send email for their customers.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: A customer uploads a bad list, and your shared IPs pay for it.With Verifier: Each upload gets a quality check before it is sent.
Without: Your team finds the problem after the bounces.With Verifier: A low-quality job is marked not ready to send.
Without: Every customer gets the same trust.With Verifier: A webhook tells your system when the job is done.

§ 2

How it works

Check every list before it is sent

Run each uploaded list as a job, apply your policy, and send only addresses that are safe to send.

2.1Send each customer list to the API as a job.
2.2Get the results by webhook.
2.3Block or warn on lists with a low quality score.

Fig. 3A job that is not ready

Request

GET /v1/jobs/4182/approval

Response

{  "job_id": 4182,  "total_records": 2000,  "safe_to_send_count": 1300,  "safe_to_send_pct": 65.0,  "ready_to_send": false,  "recommendation": "List quality is moderate. Remove invalid and risky addresses before sending."}

1,300 of 2,000 rows are safe to send · fields trimmed

§ 3

What you get

What you get.

3.1List quality before the sendUse the list quality score to stop a risky list before it reaches your sending servers.
3.2Delivery feedback at scaleFeed bounces and complaints back, so the next upload is cleaner.

§ 4

In practice

Typical uses.

Case 4.1
Customer imports
Check a new customer's first import before you send any mail for them.

Works with the tools you send from.

All integrations

Questions

Before you start.

Do you offer volume pricing?

Yes. Contact us about the Enterprise plan.

One bad list can hurt every sender

When customers share sending infrastructure, one dirty list can damage the reputation of all of them.

For platforms and agencies that send email for their customers.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: A customer uploads a bad list, and your shared IPs pay for it.With Verifier: Each upload gets a quality check before it is sent.
Without: Your team finds the problem after the bounces.With Verifier: A low-quality job is marked not ready to send.
Without: Every customer gets the same trust.With Verifier: A webhook tells your system when the job is done.

Check every list before it is sent

Run each uploaded list as a job, apply your policy, and send only addresses that are safe to send.

2.1Send each customer list to the API as a job.
2.2Get the results by webhook.
2.3Block or warn on lists with a low quality score.

Fig. 3A job that is not ready

Request

GET /v1/jobs/4182/approval

Response

{  "job_id": 4182,  "total_records": 2000,  "safe_to_send_count": 1300,  "safe_to_send_pct": 65.0,  "ready_to_send": false,  "recommendation": "List quality is moderate. Remove invalid and risky addresses before sending."}

1,300 of 2,000 rows are safe to send · fields trimmed

From a raw listto a safe send.

Check lists for the senders you serve

One bad list can hurt every sender

Check every list before it is sent

What you get.

Typical uses.

Works with the tools you send from.

Before you start.

From a raw listto a safe send.

Check lists for the senders you serve

One bad list can hurt every sender

Check every list before it is sent

What you get.

Typical uses.

Works with the tools you send from.

Before you start.