Brevo Transactional Emails: How to Send via API and SMTP

Someone just bought from your store. They’re waiting for that order confirmation. Thirty seconds pass. A minute. Nothing arrives. They check spam. Nothing there either. Now they’re worried. Did the payment go through? Is their order real?

That moment of doubt costs you trust. And trust is everything in ecommerce.

Transactional emails are the emails your customers actually wait for. Order confirmations. Password resets. Shipping updates. Account verifications. These aren’t marketing messages people ignore. These are mission-critical communications that need to arrive instantly and reliably.

Brevo transactional emails solve this problem. You get 99% deliverability rates. Emails send in seconds. You can use SMTP relay for simple setups or the REST API for full developer control. And everything integrates with Brevo’s marketing platform so you’re not managing multiple tools.

In this guide, I’ll explain how Brevo transactional emails work. We’ll cover the different sending methods, walk through setup, and look at deliverability best practices. By the end, you’ll know exactly how to ensure your critical emails reach inboxes every time.

What Are Brevo Transactional Emails?

Brevo transactional emails are automated messages triggered by specific user actions. Unlike marketing emails that you schedule and send to lists, transactional emails fire automatically when something happens — a purchase, a password reset request, an account signup.

Here’s the key difference. Marketing emails promote your business. Transactional emails respond to your customers. One is about what you want to say. The other is about what they need to receive.

Common transactional email types include:

• Order confirmation after purchase
• Shipping notification with tracking details
• Password reset links
• Account verification emails
• Payment receipts and invoices
• Login alerts and security notifications
• Subscription renewal reminders

These emails are time-critical. When someone requests a password reset, they need that link now — not in an hour. When someone completes a purchase, they expect immediate confirmation. Delays create anxiety and erode trust.

Brevo’s transactional email service delivers with 99% inbox placement rates. That’s not a marketing claim. It’s backed by proper email infrastructure, authentication protocols, and sender reputation management.

The platform offers multiple sending methods. SMTP relay works for platforms that support standard email configuration — WordPress, WooCommerce, custom applications. The REST API gives developers complete control for building email into applications. And the automation builder lets non-technical users create trigger-based emails without code.

Pricing follows a pay-per-use model. You’re charged based on email volume, not contacts. For businesses sending a mix of marketing and transactional emails, this consolidated approach is more cost-effective than maintaining separate services.

Since December 2025, Brevo’s free tier includes unlimited transactional email volume. You pay nothing until you exceed sending limits. That makes it accessible for startups testing the waters or small businesses with modest volume.

The transactional email service integrates with Brevo’s broader platform. Sent emails sync with contact profiles. You can view delivery status, open rates, and engagement alongside your marketing data. One dashboard handles everything.

For businesses relying on time-critical communications — ecommerce stores, SaaS applications, membership sites — reliable transactional email delivery isn’t optional. It’s fundamental to customer experience.

Types of Transactional Emails You Can Send

Not all transactional emails are equal. Some confirm actions. Some provide security. Some keep customers informed about ongoing processes. Understanding the types helps you build a complete transactional email strategy.

The common thread is user-initiated action. Every transactional email responds to something the recipient did. They bought something. They requested something. They triggered something in your system. The email acknowledges and facilitates that action.

Brevo handles all transactional email types through the same infrastructure. Whether you’re sending order confirmations or password resets, the delivery reliability remains consistent. The 99% deliverability rate applies across categories.

Templates make creating these emails faster. Brevo includes pre-designed transactional templates you can customize. Add your branding, adjust the content, insert dynamic fields for personalization. You don’t start from scratch unless you want to.

Personalization goes beyond just using someone’s name. Transactional emails can include specific order details, product images, tracking numbers, account information — whatever context the recipient needs. Dynamic content pulls this data automatically from your system.

Let me break down the two most important categories.

Order Confirmations and Shipping Notifications

For ecommerce businesses, order confirmations and shipping notifications are the most critical transactional emails you’ll send. They directly impact customer trust and reduce support inquiries.

Order confirmation emails should send immediately after purchase. Within seconds, not minutes. The customer just gave you money. They want proof it worked.

An effective order confirmation includes:

• Order number for reference
• List of items purchased with images
• Prices and total amount charged
• Shipping address confirmation
• Estimated delivery timeline
• Contact information for questions

Brevo’s transactional templates support dynamic product blocks. Connect your ecommerce platform — Shopify, WooCommerce, or others — and order details populate automatically. Product names, images, prices, quantities — all pulled from the actual order data.

Personalization matters here. Address customers by name. Reference their specific items. Show you know who they are and what they bought. This isn’t just friendly — it confirms accuracy and builds confidence.

Shipping notifications keep customers informed as orders move. When you create a shipment, trigger an email with tracking information. Include the carrier name and tracking number. Link directly to tracking pages when possible.

Multiple shipping updates work even better. Send when the order ships, when it’s out for delivery, and when it’s delivered. Each touchpoint reassures the customer and reduces “where’s my order?” support tickets.

The business impact is measurable. Ecommerce stores using automated order and shipping emails report 25% higher customer retention. People come back to businesses that communicate well.

Brevo integrates with major ecommerce platforms to automate these emails. Connect your store, configure the triggers, and emails send without manual intervention. Order placed triggers confirmation. Shipment created triggers tracking notification. Delivery confirmed triggers follow-up.

For high-volume stores, reliability matters intensely. Missing order confirmations create support chaos. Brevo’s infrastructure handles volume without degradation — emails deliver in under 20 seconds regardless of how many you’re sending.

Password Resets and Account Verification

Security-related transactional emails are different from order emails. They’re not about keeping customers happy — they’re about protecting accounts and enabling access.

Password reset emails are urgent by nature. Someone is locked out of their account right now. They need that reset link immediately. Delays frustrate users and can push them toward competitors.

A proper password reset email includes:

• Clear subject line identifying the purpose
• Explanation of what was requested
• Secure reset link with expiration time
• Instructions for what to do
• Warning about not sharing the link
• Contact info if they didn’t request the reset

Security best practices apply here. Reset links should expire after a reasonable period — typically 24 hours or less. Include information about request origin (IP address or device) so users can identify unauthorized attempts.

Brevo’s transactional API handles password reset flows smoothly. Your application generates the reset token, passes it to Brevo via API, and the email sends instantly. The user clicks the link and returns to your site to complete the reset.

Account verification emails confirm new signups. When someone creates an account, send an email with a verification link. They click to confirm their email address is real and they control it.

Verification emails reduce fake accounts and spam signups. They also confirm email deliverability before you start sending other communications. If the verification email doesn’t arrive, something is wrong — better to catch that early.

Login alerts notify users about account access. “Your account was accessed from a new device” type messages. These security notifications help users identify unauthorized access quickly.

Two-factor authentication codes are another category. When users enable 2FA, they receive codes via email to complete login. These are extremely time-sensitive — codes typically expire in minutes.

For SaaS applications and membership sites, these security emails are foundational. Users can’t access your product without them. Password resets, verification links, and security alerts must arrive reliably.

Brevo’s 99% deliverability becomes critical here. A password reset that lands in spam means a frustrated user. A verification email that never arrives means a lost signup. The stakes are higher than with marketing emails.

The transactional email API supports all these use cases. Trigger emails programmatically from your application logic. Pass dynamic data for personalization. Track delivery and opens for monitoring.

How to Send Brevo Transactional Emails

Brevo offers multiple methods for sending transactional emails. Choose based on your technical capabilities and platform requirements.

The three main options are:

1. SMTP relay — Standard email protocol that works with most platforms
2. REST API — Full programmatic control for developers
3. Automation builder — No-code trigger-based emails within Brevo

SMTP works best for existing platforms that already support email configuration. WordPress, WooCommerce, and most web applications have SMTP settings you can point at Brevo.

The API suits developers building custom applications or needing granular control. You make HTTP requests to send emails, and Brevo handles delivery.

The automation builder works for users already in the Brevo ecosystem who want trigger-based emails without writing code.

Most businesses use a combination. SMTP handles platform-level emails from WordPress or ecommerce systems. API handles application-specific messages from custom code. Automation handles marketing-related triggers from Brevo’s own platform.

Let me explain each method in detail.

Using Brevo SMTP Relay

SMTP relay is the simplest way to route your existing emails through Brevo’s infrastructure. If your platform already sends emails, you just change where those emails route.

SMTP stands for Simple Mail Transfer Protocol. It’s the standard way email servers communicate. Your website or application connects to Brevo’s SMTP server and hands off messages for delivery.

Brevo SMTP settings are:

Note the password field. You don’t use your Brevo login password. You generate a separate SMTP key in your account settings. This key authenticates your sending without exposing your main credentials.

For WordPress integration:

Install an SMTP plugin like WP Mail SMTP. Go to settings. Select “Other SMTP” as the mailer. Enter the Brevo SMTP settings. Save and send a test email.

Once configured, all WordPress emails — contact form submissions, password resets, WooCommerce orders — route through Brevo. You get better deliverability than default WordPress email without changing your site’s functionality.

For WooCommerce specifically:

WooCommerce uses WordPress’s email system. Configure SMTP at the WordPress level, and WooCommerce emails automatically route through Brevo. Order confirmations, shipping notifications, customer account emails — everything flows through reliable infrastructure.

For custom applications:

Most programming languages have SMTP libraries. Configure your application’s email settings with Brevo’s SMTP server details. Emails route through Brevo transparently.

SMTP advantages include simplicity and compatibility. Almost every platform supports SMTP configuration. You don’t need to rewrite email logic. Just change the server settings.

The limitation is control. SMTP sends emails as-is. For dynamic content, advanced personalization, or programmatic logic, the API offers more flexibility.

Using Brevo Transactional Email API

The REST API gives developers complete control over transactional email sending. You make HTTP requests to Brevo’s endpoints, passing email content and recipient details. Brevo handles delivery and tracking.

API integration requires development work but offers significant advantages:

• Full programmatic control over email content
• Dynamic data insertion from your application
• Webhook callbacks for delivery events
• Better error handling and retry logic
• Template management via code

Basic API workflow:

1. Generate an API key in your Brevo dashboard
2. Make POST requests to the transactional email endpoint
3. Include recipient, subject, content, and any personalization
4. Brevo processes and delivers the email
5. Optionally receive webhook notifications about delivery status

API request structure:

You send a JSON payload with email details. Required fields include sender information, recipient email, subject line, and content (HTML or text). Optional fields cover personalization, attachments, and tracking parameters.

Brevo provides SDKs for popular programming languages — PHP, Python, Node.js, Ruby, and others. These libraries simplify API integration by handling authentication and request formatting.

Webhooks for event tracking:

Configure webhooks to receive notifications about email events. When an email is delivered, opened, clicked, or bounced, Brevo sends a POST request to your specified URL. Your application can log events, trigger follow-up actions, or update user records.

This real-time feedback loop is powerful. Know immediately when a password reset email bounces. Identify which order confirmations get opened. Track engagement without checking dashboards manually.

Template management:

Create transactional email templates in Brevo, then reference them via API. Your code passes the template ID and personalization data. Brevo merges the data with the template and sends.

This approach separates design from development. Marketing or operations teams can update email templates without code changes. Developers focus on trigger logic, not HTML formatting.

Rate limits and queuing:

Brevo’s API handles high-volume sending. Built-in queuing manages bursts. Retry logic handles temporary failures. You don’t need to build email infrastructure — just send requests, and Brevo manages delivery.

For applications with significant email volume — thousands or millions of messages — the API scales accordingly. Send a single password reset or a million order confirmations through the same endpoint.

The API suits developers building custom applications, SaaS products, or complex integrations. SMTP works for simpler platform-level needs. Many businesses use both — SMTP for WordPress emails, API for application-triggered messages.

Email Deliverability and Authentication

Sending transactional emails is only half the job. Getting them into inboxes is what actually matters. If your password reset lands in spam, it’s useless. If your order confirmation gets blocked, customers panic.

Email deliverability measures what percentage of your emails reach the inbox versus spam folder or getting blocked entirely. Brevo transactional emails achieve 99% deliverability rates. That’s not automatic though. It requires proper authentication setup.

Email providers like Gmail, Outlook, and Yahoo are suspicious by default. Anyone can claim to send email from your domain. Authentication proves you’re legitimate. Without it, major providers filter your messages aggressively.

Three authentication protocols matter most:

SPF (Sender Policy Framework) tells receiving servers which mail servers are authorized to send email for your domain. You add a DNS record listing Brevo’s servers. When your email arrives, the recipient checks: “Is this server allowed to send for this domain?” If yes, it passes.

Your SPF record should include: v=spf1 include:spf.brevo.com ~all

DKIM (DomainKeys Identified Mail) adds a digital signature to every email. This signature proves the message wasn’t altered during transit. Brevo generates your DKIM key. You add the public key to your DNS. Every email gets signed automatically.

DMARC (Domain-based Message Authentication, Reporting and Conformance) tells providers what to do when emails fail SPF or DKIM checks. Should they reject? Quarantine? DMARC also provides reports about authentication failures.

Setting up authentication in Brevo takes about 15 minutes:

1. Go to Senders & Domains in your Brevo dashboard
2. Add your sending domain
3. Brevo shows the exact DNS records needed
4. Add each record to your domain’s DNS settings
5. Wait for propagation (usually a few hours)
6. Verify in Brevo — green checkmarks confirm success

IP reputation also affects deliverability. Email providers track sending behavior for each IP address. Too many bounces, spam complaints, or suspicious patterns damage reputation. Good sending practices build it.

Brevo offers two IP options. Shared IPs are used by multiple senders — your reputation partly depends on others’ behavior. Dedicated IPs are yours alone — complete control but require warming up gradually.

For transactional emails specifically, shared IPs usually work fine. Brevo monitors their shared pools carefully. Dedicated IPs make sense for high-volume senders needing maximum control.

The 99% deliverability guarantee comes from this infrastructure. Proper authentication, maintained IP reputation, and robust sending infrastructure combine to ensure your critical emails arrive.

Transactional Email Templates and Personalization

Nobody wants to code HTML emails from scratch for every message type. Templates save time and ensure consistency. Brevo provides both pre-designed templates and a drag-and-drop editor for creating your own.

The template library includes common transactional email types:

• Order confirmations
• Shipping notifications
• Password resets
• Account verification
• Invoice and receipt emails
• Welcome messages

Each template is professionally designed and mobile-responsive. Start with a template, customize colors and branding, add your content, and you’re ready.

The drag-and-drop editor works like building blocks. Add text sections, images, buttons, and dividers. Rearrange by dragging. No HTML knowledge required. What you see is what recipients get.

For developers preferring code control, Brevo accepts raw HTML templates. Build exactly what you need with full design flexibility. The platform renders your HTML across email clients properly.

Dynamic content transforms templates from static to personalized. Instead of “Dear Customer,” your email says “Dear Sarah.” Instead of generic order details, it shows the exact products purchased.

Personalization uses merge tags — placeholders that get replaced with actual data when sending. Common merge tags include:

• {{contact.FIRSTNAME}} — recipient’s first name
• {{params.ORDER_ID}} — order number
• {{params.PRODUCT_NAME}} — purchased item
• {{params.TRACKING_URL}} — shipment tracking link

You define these parameters when sending via API or SMTP. Brevo inserts the values into your template automatically.

Conditional logic takes personalization further. Show different content based on data values. If order total exceeds $100, include a thank-you discount. If shipping is international, include customs information. Templates adapt to each recipient’s situation.

Responsive design is built into Brevo’s editor. Templates automatically adjust for mobile screens. Given that most emails open on phones, this matters significantly. Buttons stay tappable. Text stays readable. Images scale appropriately.

For ecommerce stores, product blocks pull item details automatically. Connect your store, and templates can include product images, names, prices, and links without manual data entry.

The combination of templates and personalization means transactional emails feel crafted for each recipient while taking minutes to set up. You’re not choosing between efficiency and quality.

Tracking and Analytics for Transactional Emails

Transactional emails aren’t just sent and forgotten. You need visibility into what happens after they leave your server. Did they deliver? Did recipients open them? Did anyone click the links?

Brevo provides comprehensive tracking for all transactional emails:

Delivery rate shows what percentage of emails reached their destination. A healthy rate is 98% or higher. Lower rates indicate authentication problems, list issues, or infrastructure failures.

Open rate tracks how many recipients opened the email. For transactional emails, open rates are typically high — 60% or more for order confirmations. People expect and want these messages.

Click-through rate measures link engagement. Did recipients click the tracking link in their shipping notification? Did they use the password reset link? Clicks confirm the email served its purpose.

Bounce tracking identifies undeliverable addresses. Hard bounces mean the address doesn’t exist — remove these contacts. Soft bounces are temporary failures — the inbox might be full or the server temporarily down.

All this data appears in Brevo’s real-time analytics dashboard. Filter by date range, email type, or specific campaigns. See trends over time. Identify problems quickly.

Event logs provide granular detail. View the complete history for any email: when it was sent, when it was delivered, when it was opened, what links were clicked. For troubleshooting “I never got my confirmation” complaints, event logs are invaluable.

Webhooks push event data to your systems in real-time. Configure endpoints to receive notifications when emails deliver, bounce, or get opened. Your application can react immediately — log events, trigger follow-ups, or alert support staff.

Common webhook events include:

• Email delivered
• Email opened
• Link clicked
• Hard bounce occurred
• Soft bounce occurred
• Spam complaint received

For businesses with compliance requirements, Brevo maintains indefinite log retention. You can access historical email data for audits, disputes, or customer service inquiries. GDPR-compliant data handling ensures this retention meets regulatory standards.

Performance monitoring helps optimize over time. If password reset emails have low open rates, maybe subject lines need improvement. If order confirmations show high bounce rates, maybe checkout forms aren’t validating emails properly.

The analytics transform transactional email from a black box into a measurable channel. You see exactly what’s happening and can improve accordingly.

Brevo Transactional Email Pricing

Brevo’s transactional email pricing follows a pay-per-use model. You pay based on email volume, not contacts or features. This approach works well for businesses with variable sending needs.

Free tier includes generous limits for getting started:

• 300 emails per day
• Full API and SMTP access
• Template builder
• Tracking and analytics
• GDPR compliance tools

For small businesses or development testing, free handles the basics. You can send order confirmations, password resets, and other transactional emails without paying.

Paid plans scale with volume. Pricing tiers are based on monthly email volume:

These prices bundle transactional and marketing email capacity. You’re not maintaining separate services with separate bills.

Pay-as-you-go credits offer flexibility for irregular sending. Purchase credit blocks, use them when needed. Credits don’t expire, so there’s no pressure to send just because you’ve paid.

Per-email costs work out to roughly $0.001 per message at higher volumes. That’s a fraction of a cent per critical communication delivered.

Dedicated IP addresses cost extra — typically $50 or more monthly. Most businesses don’t need dedicated IPs, but high-volume senders benefit from complete reputation control.

Compared to competitors:

Brevo competes favorably on price while offering broader functionality. Unlike pure transactional services, Brevo includes marketing email, SMS, chat, and CRM in the same platform.

For businesses sending both marketing and transactional emails, consolidation saves money and simplifies operations. One bill, one dashboard, one contact database.

The pricing model suits ecommerce stores, SaaS applications, and service businesses with regular transactional volume. You pay for what you use without contact-based penalties as your list grows.

FAQs About Brevo Transactional Emails