How do I export my ZapBounce verification results?

When a batch finishes, open it in your ZapBounce account and choose CSV or XLSX. You get back the file you uploaded, row for row, with new columns on the right. Nothing in your own columns changes, so a CRM export goes back into the CRM without a join. The bulk verification page shows the upload side of the same flow.

Here's what the new columns hold. result is one of four values: valid, invalid, catch_all or unknown. reason says why, for example mailbox_not_found or greylisted. role, disposable and free_provider are true or false flags, did_you_mean suggests a fix for a typo, and smtp_code is the server's literal reply so you can audit the reading. billed shows whether the row used a credit, and checked_at records when. The result codes reference lists every reason.

For a filtered export, sort or filter on result in your spreadsheet. Most teams keep valid, delete invalid, and move catch_all and unknown rows into their own tab. Unknown rows cost nothing, so it's worth re-running them in a week, once greylisting or throttling has cleared.

From code, you have two routes. The batch.completed webhook tells your server the moment results are ready, and the batch status call returns a results_url for the download. To stream rows into a database while the batch is still running, page through GET /v1/batches/{id}/results with the cursor it returns.

Download before the retention window closes. Your addresses and results are kept 30 days by default, and you can set any window from 0, deleted as soon as you download, up to 90 days per API key. The data retention docs show the setting, and you can delete any batch at once with DELETE /v1/batches/{id}.