Brevo connector: the quota that cuts your emails
Last updated:
What the connector watches
One thing, and it is the one that breaks: the sending credits you have left. On the free tier, 300 emails a day; the 301st fails, and it is almost always the one carrying a password reset or an account confirmation.
StatHall reads GET /v3/account once an hour and opens an alert:
- below 100 credits — warning (P2), there is still room;
- below 25 credits — major (P1), the cut-off is today.
When credits come back (monthly top-up, upgraded plan), the alert closes by itself and says so.
What you need
An API v3 key (it starts with xkeysib-), created in Brevo under
SMTP & API → API keys. Older SMTP keys (xsmtpsib-) do not open that
route: StatHall refuses them at input rather than failing hourly without
saying why.
The key is encrypted before storage and never leaves the application. StatHall only reads: no sending, no contact changes, no campaigns.
Where to connect it
On the target whose emails Brevo sends — the application, or the server holding the API. If several targets share one Brevo account, configure it once and use Shared services on the others: the token stays in one place, and the alert opens everywhere.
What it does not watch
Deliverability, bounces and complaints are not tracked: those are marketing usage signals, not outages. If you need them, they live in Brevo’s own dashboards.