Brevo Transactional Emails: Setup Guide 2026

Every password reset, order confirmation, and account notification your app sends is a transactional email — and if those emails land in spam or arrive late, customers notice immediately. Brevo transactional emails promise a fix: a combined API and SMTP relay that lives inside the same Brevo account you already use for marketing campaigns, with a free tier that sends 300 emails a day.

Disclosure: Acuizz is reader-supported. Some links in this guide point to Brevo’s website; if you sign up through them, we may earn a commission at no extra cost to you. It never affects our ratings — our Brevo score is an honest 4.5 out of 5.

This is an honest setup guide. Brevo’s transactional email service is genuinely one of the best-value ways to send triggered emails in 2026 — but it’s not the fastest option on the market, and you should know that before you commit your app’s most critical emails to it.

What Are Brevo Transactional Emails?

Unlike marketing campaigns that you schedule and broadcast to a list, transactional emails are triggered by an event: a user registers, places an order, resets a password, or requests an invoice. Brevo handles these one-to-one, time-sensitive sends through two channels:

• REST API — send emails programmatically with POST /v3/smtp/email, with official SDKs for PHP, Python, Node.js, Ruby, Go, Java, and C#.
• SMTP relay — point any app, plugin, or CMS (WordPress, WooCommerce, Shopify, Magento) at Brevo’s SMTP servers with a username and password, no code required.

Both channels live in the same Brevo dashboard as your marketing emails, contacts, and CRM. That “one account for everything” design is Brevo’s biggest differentiator against pure transactional providers like Postmark or Mailgun: you get transactional sending, marketing campaigns, SMS and WhatsApp messaging, automation, and a built-in CRM without juggling five vendors.

Brevo Transactional Emails Setup: Step-by-Step

Getting Brevo transactional emails working takes roughly 20 minutes, and most of that is DNS propagation. Here’s the full process:

Step 1: Create and verify your Brevo account

Sign up at brevo.com — no credit card required on the free plan. Brevo will ask you to verify your company details; new accounts sometimes go through a quick compliance review before sending is enabled, so don’t plan a production launch for the same hour you sign up.

Step 2: Add and authenticate your sending domain

In your Brevo dashboard, go to Settings → Senders, domains & dedicated IPs → Domains and add the domain you’ll send from (e.g. mail.yourstore.com). Brevo will give you SPF and DKIM records to add to your DNS. Adding a DMARC policy as well is strongly recommended — mailbox providers increasingly penalize domains without one.

This step is non-negotiable for deliverability. Skipping authentication is the single biggest reason transactional emails land in spam, on Brevo or anywhere else. We cover the DNS mechanics in detail in our email deliverability best practices guide.

Step 3: Create your transactional template

Go to Transactional → Templates and build your email. You have three options:

• Drag-and-drop editor — for branded order confirmations and receipts your marketing team can edit without touching code.
• Rich text editor — quick plain-ish emails like password resets.
• Custom HTML — paste your own hand-coded template for full control.

Use Brevo’s template variables for dynamic data: {{ params.orderNumber }} or {{ params.firstName }} in the template, and pass those values in your API call or SMTP payload. Templates are activated individually before they can be sent through the API — don’t forget this, or your first send will fail silently.

Step 4: Choose API or SMTP relay

Use SMTP relay if you’re integrating off-the-shelf software. In WordPress with the free SMTP plugin, the settings are: host smtp-relay.brevo.com, port 587, TLS encryption, and the SMTP credentials you generate under Transactional → Settings → SMTP. It’s a five-minute config screen.

Use the REST API if you’re building a custom app. Generate a v3 API key under SMTP & API → API keys and send with a POST request. The API supports batch sending of up to 1,000 emails per request, and idempotency (a UUID with a 30-minute TTL) so that a retried request never causes a duplicate send — a genuinely useful feature for payment-related emails.

Step 5: Test before you go live

Send test messages to a few real inboxes (Gmail, Outlook, Yahoo) and check both delivery and formatting. Verify that template variables populate correctly, that links track if you enabled click tracking, and that the plain-text version is sensible. Brevo also has a sandbox/test mode concept via its API so you can validate your integration without spending quota.

Step 6: Monitor logs and set up webhooks

Brevo’s Transactional → Statistics/Logs shows a fully searchable email history with complete message content, and you can configure how long logs are retained — useful for compliance. For anything automated, configure webhooks under Transactional → Settings → Webhooks: Brevo can push real-time events for deliveries, opens, clicks, bounces, and complaints to your endpoint. Webhook your bounces into your app so you can stop emailing dead addresses automatically.

API vs SMTP Relay: Which Should You Use?

For most readers, the choice is made by the integration in front of you:

For password resets and 2FA codes, the API’s speed edge matters. For order confirmations from WooCommerce, SMTP is perfectly fine. You can also use both on the same account without conflicts — SMTP for your CMS, API for your app.

Brevo Transactional Email Pricing and Limits

Brevo charges by emails sent, not by contacts — unlimited contacts on every plan. The transactional and marketing sends share one volume allowance, which is worth knowing if you run both from the same account.

The free plan is one of the most generous in the industry — SendGrid’s trial caps at 100/day for 60 days, and Mailgun’s free tier is around 100/day. If you send under ~9,000 transactional emails a month, Brevo’s free plan handles it. API rate limits are generous too: the transactional send endpoint allows 1,000 requests per second on the base tier.

For the complete pricing picture (marketing features included on each tier), see our full Brevo review.

How Brevo Transactional Emails Perform: The Honest Bit

Brevo advertises 99%+ deliverability on its shared IPs, with dedicated IPs available for high-volume senders. Independent testing tells a more nuanced story: EmailTooltester’s 2026 seed-list rounds averaged 79.8% inbox placement for Brevo — the lowest among the combined marketing+transactional platforms tested, behind dedicated transactional specialists like Postmark (93.8%) and SMTP2GO (95.5%).

What does that mean for you? Brevo shares infrastructure between marketing campaigns and transactional sends, which is convenient but inherently less optimized than a provider whose entire business is transactional speed. For order confirmations and welcome emails, Brevo is more than adequate. For time-critical sends at serious volume (2FA, payment alerts), a dedicated provider may be worth the second vendor relationship. Also know that “support on Starter and Free tiers is slow” is a common complaint across reviews — factor that into your plans.

Common Brevo Transactional Email Mistakes to Avoid

• Sending before domain authentication propagates. Wait for SPF/DKIM to verify in the dashboard before your first production send.
• Forgetting to activate the template. Templates must be activated in the dashboard before the API can use them.
• Putting marketing content in transactional emails. Transactional emails enjoy legal privileges (they’re exempt from some unsubscribe rules), but stuffing them with promotions invites complaints and hurts the deliverability of the emails that actually matter.
• Ignoring the suppression list. Brevo automatically handles hard bounces and complaints — check it regularly rather than fighting it.
• Not setting up bounce webhooks. If your app keeps emailing bounced addresses, your reputation decays silently.

Brevo Transactional Emails FAQ

Are Brevo transactional emails really free?

Yes — the free plan includes 300 emails per day via both the API and SMTP relay, forever. The only catches are Brevo branding on emails and the daily cap. For a small store or side project, that’s often all you need.

Does Brevo offer a dedicated IP for transactional email?

Yes, dedicated IPs are available for high-volume senders (typically on custom/Enterprise plans). For most senders, Brevo’s shared IPs are fine — only consider a dedicated IP when shared infrastructure demonstrably isn’t working for you.

Can I use Brevo transactional emails with WordPress or WooCommerce?

Yes. Install an SMTP plugin (or Brevo’s official WordPress plugin) and configure it with your Brevo SMTP credentials — host smtp-relay.brevo.com, port 587, TLS. All WooCommerce order emails then route through Brevo’s infrastructure with proper authentication.

How do I track transactional email opens and bounces in Brevo?

Two ways: the searchable logs under Transactional → Statistics in the dashboard, and real-time webhooks for deliveries, opens, clicks, bounces, and complaints that push events to your own endpoint.

Brevo vs Postmark vs Mailgun for transactional email?

Brevo wins on value and convenience (free tier, marketing + transactional in one account); Postmark and Mailgun win on raw transactional speed and inbox placement. Choose Brevo if you already use it for marketing; choose a specialist if transactional email is mission-critical infrastructure.

The Verdict

Brevo transactional emails are the best-value way to add triggered email to a small business or app in 2026: a genuinely free tier with 300 emails/day, both API and SMTP relay from day one, good templates, webhooks, searchable logs, and pricing that stays cheap as you grow. The honest caveat is that it’s a marketing platform doing transactional email, not a transactional specialist — deliverability is good but not best-in-class.

If you run your newsletters on Brevo already, using it for transactional sends is a no-brainer — one bill, one dashboard, one authenticated domain. If you don’t, the free tier still makes it the cheapest credible way to stop sending password resets from your web host’s mail server. Try Brevo free and send your first transactional email today.