Verify your Brevo contacts without exporting

How it works

1. Ask for beta access (email support@simpleverifier.com from the address you sign in with), then sign in and open Integrations in your dashboard.
2. In Brevo, open the SMTP & API settings page, go to the API keys tab and click Generate a new API key.
3. Name it, generate it and copy it straight away (it starts with xkeysib-). Use an API key, not an SMTP key.
4. Paste it and click Connect. We check it with Brevo before saving it.
5. Pick one of your lists. They are read live from your account.
6. Keep the default, writing each result into the SV_STATUS contact attribute, or untick it to only check. Remove invalid contacts from this list and Blocklist invalid contacts for email stay off until you tick them and confirm.
7. Read the confirmation, which shows what the run costs on your plan, and press Verify. Follow it in History and download the results there.

What we read and what we change

Only documented Brevo API endpoints are used. To check a list, SimpleVerifier reads:

• GET /v3/contacts/lists checks the key when you connect and lists your contact lists with their size. docs
• GET /v3/account reads your company name once, when you connect. docs
• GET /v3/contacts/lists/{listId}/contacts pages through a list's contacts, 500 at a time; blocklisted contacts and contacts unsubscribed from the list are skipped. docs
• GET /v3/contacts/attributes checks whether the SV_STATUS attribute exists. docs

Only for the actions you choose, and only once verification has completed, it calls:

• POST /v3/contacts/attributes/normal/SV_STATUS creates SV_STATUS as a text attribute the first time, only when you ticked the attribute option. docs
• POST /v3/contacts/batch writes SV_STATUS for 100 contacts per call, or sets emailBlacklisted on invalid contacts if you chose to blocklist them. docs
• POST /v3/contacts/lists/{listId}/contacts/remove removes invalid contacts from this list, if you chose to. They stay in your account. docs

• Brevo allows 10 requests a second on its contact endpoints on standard plans; we stay under that. Reading your company name uses one call on a route Brevo limits to 100 an hour, only when you connect.
• If you restricted your API keys to authorised IP addresses in Brevo's security settings, Brevo refuses our server until you add its address or lift the restriction.
• Removing from the list keeps the contact in Brevo and in its other lists. Blocklisting stops email to the contact across your whole account; you can unblock a contact in Brevo. Both are off by default and need a confirmation.
• A new attribute uses one of your account's contact attributes. Build a segment where SV_STATUS is invalid to exclude those contacts from campaigns without changing anything else.
• Beta: not yet tested against a live Brevo account. The calls follow Brevo's published API v3 reference, and Brevo's real API rejects a wrong key as expected. If something behaves differently in your account, write to support@simpleverifier.com.

Common questions

How do I verify the contacts in a Brevo list?

Connect your Brevo API key in the SimpleVerifier dashboard, pick the list and press Verify. SimpleVerifier reads the email addresses through the Brevo API and checks each one with its mail server, as a normal list job: results show in History as valid, risky or invalid with a reason, with the same downloads as an uploaded CSV.

What does SimpleVerifier change in Brevo?

Only what you pick for that run, and only after verification has completed. The default writes the result into the SV_STATUS contact attribute and nothing else. Remove invalid contacts from this list is opt-in: Brevo takes them out of the list you picked. The contacts stay in your Brevo account and in their other lists. Blocklist invalid contacts for email is opt-in: Brevo marks them as blocklisted for email across your whole account, so no campaign emails them. You can unblock a contact in Brevo. These act on invalid contacts only, never risky ones, and the dashboard asks you to confirm first. Only a confirmed mailbox is written as valid; anything unconfirmed is written as risky.

What does it cost?

The same as uploading the addresses as a CSV: one check per distinct address. Free accounts use their free checks (if the list is bigger than what is left, the first addresses are checked and the rest stay unchecked and untouched). Paid plans use their monthly allowance or full-speed volume. Up to 100,000 contacts per run. Paid plans can also auto-verify new contacts once a day, up to 10,000 a day.

How is my Brevo key stored?

It is checked with Brevo, encrypted with AES-256-GCM using a server-side key and stored on our server. It is never shown again, never sent back to your browser and never written to logs. Removing it in the dashboard deletes it and skips any pending write-back.

Why a pasted key and not a one-click Connect button?

A one-click OAuth app needs a listed Brevo app, which we have not published yet. Until then you paste a key from your own account, which you can revoke in Brevo at any time. OAuth is a planned upgrade.

Is the Brevo integration live?

It is in beta. It is built on Brevo's published API reference and the same verification and billing path as our other integrations, but it has not been tested against a live Brevo account yet, so the Connect button is only switched on for accounts on the beta list. To join, email support@simpleverifier.com from the address you sign in with. Until then, export the list as a CSV and upload it.

Why was my Brevo key rejected?

Paste an API key from the API keys tab (it starts with xkeysib-), not an SMTP key. A 401 can also mean the key was deleted, or that your account only accepts API calls from authorised IP addresses.