ZapBounce

ZapBounce and Sendinblue

Sendinblue rebranded to Brevo in 2023, and a lot of working integrations still carry the old name in their configuration. That matters here because an automation pointing at a deprecated endpoint can fail quietly while appearing to run.

The verification work is the same either way. The thing worth checking first is which API your import is actually hitting.

A rename leaves stale integrations behind

Scripts written against the older Sendinblue API are common in accounts that predate the rebrand. Some still work, some have been deprecated, and the failure mode for a deprecated contact-import endpoint is a silent partial import.

That produces a specific confusion: contacts appear in the platform, some are missing, and nobody can tell whether the gap is bad data or a broken import. Verifying the file before the import removes one of the two explanations.

The underlying platform constraints are Brevo's: an account review before the first send, and bounce-rate limits after it.

How the data moves

  1. Check which API your import uses

    Before anything else. An import you cannot fully account for is not a data-quality problem you can reason about.

  2. Verify the CSV before import

    Export from the platform, verify the file, and import the results back with the verdict as an attribute.

  3. Use an attribute for the verdict

    Attributes are usable in list conditions, so the verdict becomes a filter rather than a note.

  4. Reconcile the counts after import

    The verified file's row count and the platform's contact count should agree. A gap is the stale-integration problem, not a verification one.

Setting it up

  1. Confirm whether your import path uses the current Brevo API or an older Sendinblue endpoint.
  2. Export the contact list as CSV with all attribute columns.
  3. Verify the file and download the results when the webhook fires.
  4. Create an attribute for the verdict and import the verified file.
  5. Reconcile the row count of your file against the contact count in the platform.
  6. Blocklist the invalid contacts rather than deleting them.

Sendinblue: common questions

Is Sendinblue the same as Brevo?

Yes, renamed in 2023. The platform constraints on this page are Brevo's, and the Brevo integration page covers the same ground under the current name.

Why does my import lose rows?

Usually a deprecated endpoint or a field-mapping mismatch rather than the data. Reconcile the counts before concluding anything about the addresses.

Should I update my integration?

Yes, to the current API. A silent partial import is a bug you will otherwise diagnose as a data problem for months.

Reference

Check a Sendinblue export today

100 free checks a month, no card. Unknown results and duplicates are never billed.

Get an API keySee pricing