# Error: Unauthorized: not verified or IP not authorized (Brevo)

Source: https://catalystgroup.gg/docs/email-delivery/error-brevo-unauthorized/
Updated: 2026-10-19 · By Duane Garner

Brevo refused the API call because your server's IP address is not on the account's allowed list, or the account is not verified yet.

This article is for sites using the **Brevo** mailer where a send fails with an "Unauthorized" reply that mentions an unverified account or an IP address that is not authorized.

 

> **The error as you see it:** `Unauthorized: not verified or IP not authorized` (Brevo may word it as "We have detected you are using an unrecognised IP address" with the address shown)
>  
> Shown by the **Brevo** mailer, in the failed-send banner, in **Tools → Debug Events** and in the **Email Log**. Brevo returns it with HTTP status 401.

 

## What this error means

 

Your **API Key** is a real Brevo key, but Brevo will not accept a call from where it came. Brevo lets account owners restrict API use to a list of *authorized IP addresses*. When that protection is on, any request from an address not on the list is refused, even with a correct key. The same reply is also used when the account itself has not been verified yet.

 

## Common causes

 
- **IP blocking is on and your web server's address is not on the list.** This often starts after a move to a new host or server, or when the host changes its outgoing address.
- **Your host sends from several addresses** (load balancers, IPv6 as well as IPv4), and only one is authorized.
- **The account is new and not verified** yet: email confirmation or profile details are incomplete.
- **A staging copy** with its own IP address uses the live site's key.

 

## How to fix

 
1. Find the blocked address
  Open **CRM-NG SMTP → Tools → Debug Events** and read the newest **Email Sending Errors** entry. Brevo often names the IP it saw. If not, ask your host for the server's outgoing IPv4 and IPv6 addresses.
2. Open Brevo's security settings
  Sign in to `https://app.brevo.com/`, open the account menu (your name at the top right), and go to **Security → Authorized IPs** (the console's current name may vary slightly).
3. Authorize the server
  Add each outgoing address of your web server. Alternatively, if you do not need IP restriction, turn the blocking off. Keeping it on with the right addresses is safer.
4. Check account verification
  On the Brevo dashboard, look for a notice asking you to confirm your email, complete your profile or verify the account. Finish every step it lists.
5. Confirm the key
  In **CRM-NG SMTP → Settings → General**, with **Brevo** selected, make sure **API Key** holds a v3 API key (it starts with `xkeysib-`). Press **Save Settings** if you change anything.
6. Send a test
  Go to **CRM-NG SMTP → Tools → Email Test**, fill in **Send To** and press **Send Email**.

 

## Verify it worked

 

The test page shows "Test email sent successfully! Check your inbox to confirm delivery." In Brevo, the message appears in the transactional email logs.

 

## Notes

 
- If your host changes your server's IP without warning, this error comes back. Ask the host whether your outgoing address is fixed, and keep a note of it.
- Brevo sends you an email when it blocks an unknown IP. It usually includes a one-click link to authorize it.

 

## Related

 
- [Brevo (formerly Sendinblue)](https://catalystgroup.gg/docs/email-delivery/mailer-brevo/)
- [Error: Unauthorized: key not found (Brevo)](https://catalystgroup.gg/docs/email-delivery/error-unauthorized-key-not-found/)
- [Error: Permission denied: SMTP account not activated (Brevo)](https://catalystgroup.gg/docs/email-delivery/error-smtp-account-not-activated/)
- [Troubleshooting email delivery](https://catalystgroup.gg/docs/email-delivery/troubleshooting/)