Skip to main content

Understanding Brevo Errors in Hurree

Troubleshoot Brevo integration errors in Hurree. Not for general Brevo issues.

S
Written by Shauna Doherty

If you're experiencing issues with your Brevo widgets, this guide explains the most common errors and how to resolve them. Each error below matches the message you'll see in Hurree. If you encounter an error that isn't covered below, please contact our support team for assistance.

Your Brevo connection could not be verified

Explanation: This happens when the credentials used to connect your account are missing, expired, or no longer valid, preventing your widgets from retrieving updated data.

How to solve: Reconnect your Brevo account via Hurree to restore access. Reconnecting re-establishes the connection with valid credentials, and your widgets should begin retrieving data again. If the issue continues after reconnecting, please contact our support team for assistance.

There's an issue with your Brevo account

Explanation: Your Brevo account may not be active, or it may have insufficient credits. Brevo restricts API access when an account is suspended or has run out of email credits.

How to solve: Check your account status and remaining credits in Brevo, then try again. If your account is active and has credits but the error persists, please contact our support team.

You do not have permission to access this resource

Explanation: You don't have permission to access this Brevo resource. This can occur if your user role has changed, access has been revoked, or you have not been granted the appropriate level of access within Brevo.

How to solve: Check that your Brevo account has the necessary access rights, or contact your administrator and ask them to review your permissions. Once the required access has been granted, refresh your connection and try retrieving the data again.

The requested resource could not be found

Explanation: The requested Brevo resource could not be found. This may occur if a campaign, contact list, or other resource has been deleted, or if the reference is incorrect.

How to solve: Review the relevant Brevo account and verify that the resource still exists. If it has been removed, you may need to update your widget settings or select an alternative data source.

You've reached the Brevo API limit

Explanation: Brevo restricts the number of requests allowed within a given time window, and if your connected widgets are pulling data at a high frequency, this limit may occasionally be reached.

How to solve: Wait a moment before trying again, your access will resume automatically once the rate limit window resets. If you are consistently hitting this limit, please contact our support team so we can review your connector configuration.

Brevo internal server error

Explanation: An unexpected error occurred on Brevo's servers. This is not caused by any action on your part, and as the issue originates within Brevo's infrastructure, it is outside of our control.

How to solve: Internal server errors are typically temporary and often resolve automatically. Wait a moment and try again, or check your widget after the next scheduled sync period. If the error persists after multiple sync attempts, please contact our support team for assistance.

Other Request Errors

Explanation: You may occasionally see 400: Bad Request, 405: Method Not Supported, or 406: Not Acceptable. These indicate that something about the request sent to Brevo was invalid, incorrectly formatted, or could not be returned in the expected format, they are typically handled automatically and are rarely caused by anything on your side.

How to solve: Review your integration settings for any incorrect entries and try again. If any of these errors persist, please contact our support team with the error name you're seeing and we'll investigate.

⚠️ Note: This article is intended only for Hurree users troubleshooting Brevo Widgets errors within the Hurree platform. If you're seeing Brevo errors outside of Hurree, please visit Brevo's Help Center.

Did this answer your question?