Skip to content
Jooosi
Account
JM Jooosi Mail

Brevo

Browse documentation
Overview
Contents
On this page
  1. Before you begin
  2. Supported transport and settings
  3. Create the connection
  4. Verify delivery
  5. Webhooks
  6. Troubleshooting

Brevo can send through its API or SMTP. API is the default and uses an API key. SMTP uses the account SMTP username and SMTP key. The provider profile also supports webhooks so Jooosi Mail can record Brevo event callbacks.

Before you begin#

Have a provider account and credentials for the transport you chose. Copy credentials from the provider’s own console or account settings; never put secret values in documentation. Check the provider’s documentation for account requirements and sender acceptance.

Supported transport and settings#

  • Transport scheme: brevo+api (default), brevo+smtp.
  • Required settings: brevo+api: Brevo API key (secret). brevo+smtp: Brevo SMTP username and Brevo SMTP password (secret).
  • Optional settings: There are no additional provider configuration fields for this profile.

Jooosi Mail marks password, token, key, and private-key fields as secrets in the connection form. Enter only the fields shown for the selected scheme.

Create the connection#

  1. In WordPress admin, open Jooosi Mail → Connections and choose New connection.
  2. Enter a descriptive Connection name and select Brevo in Profile.
  3. Choose the transport scheme you want to use. Enter its required fields listed above and leave fields for other schemes empty.
  4. Review the sender, routing, and advanced settings for this connection.
  5. Choose Create connection to save it.

For the shared form workflow, see Connect a provider.

Verify delivery#

Follow Send a test email and send to a mailbox you can check. A test sends a real email. Check the mailbox and Jooosi Mail → Logs for the attempt status. For supported webhooks, see the provider note and Provider webhooks guide.

Webhooks#

Brevo webhooks are supported. Enable Webhooks under Advanced settings, save, and configure the displayed endpoint in Brevo. The adapter verifies webhook requests by source IP allowlist; it does not use the connection’s shared Webhook secret for signature verification. See the shared Provider webhooks guide for endpoint and event details.

Troubleshooting#

  • Make sure you copied an API key for API transport or the SMTP username and SMTP key for SMTP transport.
  • If events are not accepted, check the webhook event log and confirm that the request reaches the site from an IP accepted by the Brevo adapter.

Provider reference: https://developers.brevo.com/.