Use case
Check a list before it hurts your sender reputation
An old address list can damage the reputation of your sending domain. With email verification you remove what cannot be delivered, and you only pay for clear results.
For businesses and self-employed professionals only
How the clean-up works
You call the endpoint per address, with your own concurrency. There is no batch endpoint.
-
Check an address
Call
GET /v1/email-verification/{email}for each address.curl "https://api.flowdata.one/v1/email-verification/max@example.com" \ -H "Authorization: Bearer fd_YOUR_KEY" -
Sort by `result`
safecan go out,riskydepends on the campaign,invalidis removed from the list. -
Retry `unknown` later
An
unknowncosts nothing. Try again at a later time instead of deleting the address.
What matters
Check before sending, not after
Hard bounces hurt the sender reputation. Lists from old exports or forms are the most common cause.
Do not drop
riskyacross the boardRole addresses and catch-all domains can have real recipients. Decide by campaign and list size.
Plan the cost
You pay per checked address with a clear result. The price is on the pricing page.