Verify SparkPost recipient lists, suppress the bad ones
Connect SparkPost with an API key, choose a recipient list, and every address is verified. SparkPost cannot update one recipient at a time, so this connector works by removal: invalid addresses go to your suppression list.
- No export, no re-import
- Catch-all and unknown are free
- Nothing is ever hard-deleted
How the SparkPost integration works
- 1
Connect SparkPost
Paste a SparkPost API key. US and EU accounts are both supported.
- 2
Choose a recipient list
Pick the recipient list you want checked. We pull its addresses and remove duplicates first, so an address listed twice is only verified, and charged, once.
- 3
We verify it in the background
Every address goes through the full check: syntax, domain and MX records, disposable and role detection, and a live conversation with the receiving mail server. The run shows in your Bulk Jobs like any other, so you can close the tab.
- 4
Results land in SparkPost
No verdict is written onto recipients. SparkPost can only replace a whole recipient list, and rewriting your list to add a field would risk data we did not round-trip, so we do not. Download the full results from the bulk job instead.
What each result means
Every address gets one of these verdicts in the job results. In SparkPost itself, only invalid addresses are acted on, through suppression.
| Result | Meaning | Credit |
|---|---|---|
| pv-good | The mailbox was confirmed to exist. Safe to send. | 1 |
| pv-risky | A catch-all domain: it accepts every address, so the mailbox could not be confirmed either way. | Free |
| pv-invalid | The mailbox does not exist. Sending here earns a hard bounce. | 1 |
| pv-unknown | No definite answer from the mail server (blocked, greylisted or timed out). | Free |
Cleaning up SparkPost
Remove invalid adds those addresses to your SparkPost suppression list, which stops future sends to them.
Removal is always your choice and never deletes anything. pv-risky and pv-unknown are never removed, because neither proves an address is bad. If a sync fails part way, nothing is written back at all rather than acting on partial results.
Why SparkPost users verify
SparkPost is used for high-volume sending where bounce rates directly affect throughput and reputation. Suppressing addresses that do not exist before a send is the fastest way to keep bounces down.
What it costs
A SparkPost sync costs exactly what verifying those addresses any other way would: 1 credit per definite answer (valid, invalid or disposable). Catch-all, unknown and error results are free, because none of them confirms anything. Credits never expire, and new accounts get free credits to try it, no card needed. See pricing for packs.
SparkPost integration FAQ
Why are there no tags in SparkPost?
SparkPost's API can only replace an entire recipient list, not update one recipient. Rewriting your list just to add a field would risk your data, so the connector suppresses invalid addresses and leaves the list itself alone.
Where do I see the verdict for every address?
The sync runs as a normal bulk job in Prime Verifier; download its results for the full breakdown.
Guides
Other integrations
- SendGrid
- Mailgun
- Mailjet
- Mailchimp
- HubSpot
- Klaviyo
- ActiveCampaign
- Brevo
- MailerLite
- Campaign Monitor
- Zoho CRM
- Google Sheets
- Zapier
Not seeing your tool? See every way to connect, including the REST API and webhooks.
Clean your SparkPost recipient list today
Free credits on sign-up. No card. You only pay for definite answers.
Start free