GoAdmio
GoAdmio Documentation

Brevo API

From the GoAdmio knowledge base.

Brevo API

This page explains the Brevo API integration in GoAdmio. It routes outgoing email from Roundcube webmail through the Brevo transactional email API for improved deliverability — with automatic fallback to the server's default SMTP when Brevo credits run out.

Location: Admin Panel → Email → Brevo API


Overview

Brevo (formerly Sendinblue) is a transactional email provider with a strong sender reputation. The Brevo API integration in GoAdmio sends Roundcube's outgoing mail through Brevo's HTTP API instead of SMTP, which typically improves deliverability and gives you visibility into credit usage.

Key behaviors:

  • Roundcube-only — affects webmail sending only, not SnappyMail, Outlook, Thunderbird, or PHP mail()
  • Automatic fallback — if Brevo credits run out, mail reverts to the server's default SMTP without interruption
  • Auto-disabled per domain — any domain with a custom SMTP configuration is skipped automatically
  • Requires domain verification — the sending domain must be authenticated in Brevo (SPF, DKIM, tracking domain)
  • Requires IP whitelisting — the server's public IP must be added to your Brevo account
> Important: This feature works exclusively with Roundcube. For SnappyMail or external mail clients (Outlook, Thunderbird, mobile apps), use Custom SMTP Relay or Global SMTP Relay instead.

How It Works

When Brevo API is enabled:

  1. A user logs in to Roundcube and sends a message.
  2. GoAdmio checks whether the domain has a custom SMTP configured:
- Yes → Brevo API is skipped for that domain; the custom SMTP is used - No → proceed to step 3
  1. GoAdmio sends the message through the Brevo API (HTTP, not SMTP).
  2. If Brevo accepts it, the message is delivered by Brevo.
  3. If credits are exhausted (or Brevo returns an error), GoAdmio falls back to the server's default SMTP automatically.
> Note: The fallback is seamless — the user does not see an error, and the message still sends. Credits and fallback events are visible on the Brevo API page.

What the Page Shows

| Field | Description | Example |
|---|---|---|
| Brevo API Key | Your Brevo API key (starts with xkeysib-) | xkeysib-4a4f...-nrTU9PIYCyhEVSdl |
| Email Credits | Remaining Brevo email credits | 217 |
| IPv4 | The server's public IPv4 address (must be whitelisted in Brevo) | 161.97.154.191 |
| IPv6 | The server's public IPv6 address (must be whitelisted in Brevo) | 2a02:c206:2079:4015::1 |

> Tip: The Email Credits count is your early warning signal. When it approaches zero, the system starts falling back to default SMTP — top up credits before that happens if you rely on Brevo for deliverability.


Prerequisites

Before enabling Brevo API:

  1. A Brevo account — https://www.brevo.com
  2. A Brevo API key — generate one in Brevo → SMTP & API → API Keys
  3. The sending domain verified in Brevo — including:
- SPF record added - DKIM record added - Tracking domain configured (if you use tracking)
  1. The server's public IPv4 (and IPv6) whitelisted in your Brevo account
  2. Roundcube installed on the server — see Webmail
  3. Root access to the GoAdmio Admin Panel
> Note: If any prerequisite is missing, GoAdmio will not fail — Roundcube simply continues sending through the server's default SMTP until the requirement is met. Verify each step before expecting Brevo routing.

How to Configure

Step 1 — Get a Brevo API key

  1. Log in to your Brevo account.
  2. Navigate to SMTP & API → API Keys.
  3. Click Generate a new API key.
  4. Name it (e.g., GoAdmio Roundcube).
  5. Copy the key — it starts with xkeysib- and is shown only once.
> Warning: Treat the API key like a password. Never share it, and rotate it if it is ever exposed. See Security best practices below.

Step 2 — Verify your domain in Brevo

In Brevo → Senders & IPs → Domains:

  1. Add the domain (e.g., example.com).
  2. Copy the SPF record into your DNS — see DNS Manager and SPF / DKIM.
  3. Copy the DKIM record into your DNS.
  4. Add the tracking domain if you use Brevo's tracking features.
  5. Wait for DNS propagation, then click Verify in Brevo.
> Tip: Use dig to confirm the records before verifying: ```bash dig TXT example.com | grep -i spf dig TXT brevo._domainkey.example.com
↑