Brevo Transactional Email: API, SMTP & Email Delivery Explained
Last updated: August 2026
Transactional email is one of the less visible but most important parts of a modern customer communication stack. Order confirmations, password resets, account-verification messages, shipping notifications, invoices, and other event-triggered emails need to arrive reliably and quickly. Unlike promotional newsletters, these messages are generally triggered by a specific action or transaction.
Brevo combines transactional email infrastructure with email marketing, automation, CRM, and other communication channels. Its transactional system can be accessed through an SMTP relay or API, making it suitable for both no-code website integrations and custom applications. Brevo’s current documentation supports transactional messages through its API endpoint and SMTP relay, while its broader platform includes marketing and sales tools.
Quick Verdict
Our verdict: Brevo is a strong option for small and mid-sized businesses that want transactional email infrastructure alongside marketing automation and CRM rather than maintaining several separate platforms.
Best for: SMBs, ecommerce stores, SaaS businesses, agencies, and budget-conscious teams that need both marketing and transactional messaging.
Consider alternatives if: You need extremely specialized enterprise deliverability infrastructure, highly advanced customer-data orchestration, or a platform built primarily around sophisticated ecommerce lifecycle marketing.
Scorecard
| Category | Rating |
|---|---|
| Ease of Use | 4.5/5 |
| Deliverability Tools | 4.5/5 |
| Multi-Channel Features | 4.5/5 |
| Marketing Automation | 4/5 |
| Value for Money | 4.5/5 |
| Overall | 4.4/5 |
These scores are editorial assessments rather than official Brevo ratings. Actual results depend heavily on sender reputation, list quality, authentication, message content, and sending practices.
What Is Brevo Transactional Email?
Transactional emails are messages generated by a user’s action or a system event. Typical examples include:
- Account activation emails
- Password-reset messages
- Order confirmations
- Shipping notifications
- Payment receipts
- Invoices
- Appointment reminders
- Subscription notifications
- Security alerts
Brevo provides two primary technical approaches for sending these messages: SMTP relay and the Brevo API.
The SMTP option is generally easier for applications that already support SMTP. The API is more suitable when developers want programmatic control over message content, templates, personalization, attachments, scheduling, and event handling. Brevo’s transactional API uses the /v3/smtp/email endpoint and can return a message ID that can be used for tracking.
Brevo SMTP Relay Explained
SMTP stands for Simple Mail Transfer Protocol. It is the standard mechanism used to transfer email between systems.
Instead of having your website attempt to deliver transactional messages directly, you can configure the application to send them through Brevo’s SMTP relay.
Brevo’s documentation lists:
- SMTP server:
smtp-relay.brevo.com - Port 587 or 2525 for standard connections
- Port 465 for encrypted SSL/TLS connections
- An SMTP login and SMTP key for authentication
Importantly, Brevo distinguishes an SMTP key from an API key. Applications connecting through the SMTP relay should use the appropriate SMTP credentials rather than an API key.
When SMTP Makes Sense
SMTP is particularly useful when:
- Your website already supports SMTP configuration.
- You are using a WordPress or ecommerce plugin.
- You want to avoid developing a custom API integration.
- Your application sends standard transactional messages.
- You are migrating from another SMTP provider.
Brevo also supports plugin-based setup, which can simplify configuration for supported platforms.
Brevo Transactional API
The API provides more granular control than a basic SMTP configuration.
Developers can send messages containing:
- HTML content
- Plain-text content
- Brevo templates
- Dynamic parameters
- Attachments
- CC/BCC recipients
- Reply-to addresses
- Custom headers
- Tags
- Scheduled delivery
Brevo’s API documentation also provides examples for sending static and dynamic transactional messages. The API returns a message ID after a successful request, which can be useful when troubleshooting and tracking individual messages.
For a SaaS application, for example, the API can dynamically insert a customer’s name, order number, delivery information, or account details into a pre-designed transactional template.
API vs SMTP: Which Should You Use?
| Requirement | SMTP | API |
|---|---|---|
| Simple website integration | Excellent | Good |
| Existing SMTP-compatible software | Excellent | Not necessary |
| Custom application | Good | Excellent |
| Dynamic personalization | Good | Excellent |
| Developer control | Moderate | High |
| Custom integrations | Moderate | Excellent |
| No-code/plugin setup | Excellent | Moderate |
Bottom line: SMTP is usually the simpler route, while the API is preferable when your development team needs deeper programmatic control.
Email Deliverability: What Actually Matters?
A common mistake in email marketing is assuming that choosing a reputable email provider automatically guarantees inbox placement.
It does not.
Deliverability depends on several factors, including:
- Domain authentication
- Sender reputation
- Bounce rates
- Spam complaints
- Engagement
- List quality
- Sending consistency
- Email content
- Recipient-provider policies
Brevo supports domain authentication and recommends authenticating your sending domain before using transactional email. This is an important step because mailbox providers increasingly expect senders to demonstrate control over their domains.
SPF, DKIM and DMARC
SPF helps establish which servers are authorized to send email for your domain.
DKIM adds a cryptographic signature that helps receiving systems verify that an email was authorized by the sending domain.
DMARC builds on authentication mechanisms such as SPF and DKIM and gives domain owners a framework for handling authentication failures.
For businesses sending transactional messages from their own domain, these technologies should be considered part of the basic email infrastructure rather than optional extras.
Brevo’s setup process includes domain authentication before configuring transactional sending.
Core Brevo Features
Email Marketing and Drag-and-Drop Editor
Brevo isn’t limited to transactional email.
Its broader platform includes a drag-and-drop email editor, reusable templates, email campaigns, reporting, and personalization features. This makes it possible to manage promotional campaigns and transactional communications within the same ecosystem.
For a small business, this consolidation can reduce the need to maintain separate tools for newsletters, automated messages, and customer communication.
Multi-Channel Marketing
Brevo extends beyond email with additional channels such as:
- SMS
- Web push
- Chat
- Transactional messaging
Feature availability varies by plan and channel. Brevo’s current plan structure includes email and SMS capabilities at lower levels, while some advanced WhatsApp and other functionality is available on higher plans or as additional services.
This makes the platform more relevant to businesses developing an omnichannel customer-engagement strategy.
Marketing Automation
Brevo provides workflow automation for behavior-based marketing.
Possible use cases include:
- Welcome sequences
- Lead nurturing
- Abandoned-cart workflows
- Customer follow-ups
- Event-triggered campaigns
- Segmentation-based communication
One important distinction is that plan limits matter. Brevo currently lists a 2,000-contact automation limit for Free and Starter, while Standard provides unlimited contacts in active automations.
That distinction is worth checking before choosing a plan for a growing automation program.
Sales CRM and Pipeline Management
Brevo also includes sales CRM functionality, allowing businesses to manage contacts, deals, tasks, and sales activity within the same ecosystem.
For a small company that does not already have a dedicated CRM, this can be useful because marketing and sales data can exist within one platform rather than being distributed across several systems.
However, companies with highly specialized enterprise CRM requirements may still prefer dedicated CRM platforms.
Brevo Pricing Model
Brevo’s pricing deserves careful attention because its current structure is more nuanced than the simple claim that it “charges per email rather than contacts.”
Brevo’s paid plans allow businesses to select monthly email volumes, with the selected volume influencing pricing and, on many tiers, contact-storage limits. Brevo also offers prepaid email credits that can be purchased separately and do not expire until used.
Current Plan Structure
| Plan | Starting Price | Key Characteristics |
|---|---|---|
| Free | $0/month | 300 daily email sends, up to 100,000 stored contacts |
| Starter | From $9/month | No daily sending limit; email-volume tiers |
| Standard | From $18/month | Automation, A/B testing, advanced reporting |
| Professional | From $499/month | High-volume marketing and advanced features |
| Enterprise | Custom | Enterprise-level capabilities and support |
Brevo’s current pricing documentation lists these plans and their principal limits.
The Free plan is particularly useful for testing because it does not require a paid subscription and includes transactional email functionality, although the 300-email-per-day limit makes it unsuitable for high-volume production environments.
Why the Model Can Be Attractive
For businesses with large contact databases but relatively modest sending frequency, email-volume-based pricing can be more economical than platforms where pricing rises primarily with stored or subscribed contacts.
However, buyers should compare the complete pricing structure, including email volume, contact limits, automation requirements, SMS/WhatsApp usage, seats, add-ons, and any dedicated infrastructure.
Pros and Cons
Pros
1. Strong Transactional Infrastructure
The SMTP relay and API give businesses two practical ways to integrate transactional email into websites and applications.
2. Marketing and Transactional Email in One Platform
Combining campaigns, automation, CRM, and transactional communications can simplify a small business’s technology stack.
3. Flexible Sending Options
Businesses can use SMTP for relatively straightforward integrations or the API when they need more developer control.
4. Competitive Entry-Level Pricing
The Free and Starter options make it possible to begin without immediately committing to an expensive enterprise platform.
5. Broader Communication Channels
Email is only one part of the platform. SMS, WhatsApp, web push, and other channels can support a broader customer-engagement strategy.
Cons
1. Free Plan Sending Limit
The Free plan has a 300-email-per-day limit, which can quickly become restrictive for an active ecommerce store or application.
2. Advanced Features Require Higher Plans
Some advanced automation, reporting, landing-page, contact-scoring, and multichannel features become available only at higher tiers.
3. Pricing Requires Careful Comparison
The relationship between email volume, contact storage, features, and add-ons means buyers should calculate their actual requirements instead of comparing only the advertised starting price.
Brevo vs Competitors
| Platform | Pricing Structure | Contact Limits | Multi-Channel | Built-in CRM |
|---|---|---|---|---|
| Brevo | Primarily email-volume based on paid tiers | Varies by plan; generous Free storage | Email, SMS, WhatsApp, web push and more | Yes |
| Mailchimp | Contact + email-send limits | Plan-dependent | Email, SMS and other marketing tools | Limited compared with dedicated CRM |
| ActiveCampaign | Primarily contact-based/customized | Plan-dependent | Email, automation, SMS/WhatsApp options | Strong |
| Klaviyo | Profile-based + message/channel usage | Profile-based | Email, SMS and ecommerce-focused channels | Customer-data focused |
Mailchimp currently structures its marketing plans around contact counts alongside email-send limits; its Free plan is limited to 250 contacts and 500 monthly sends.
ActiveCampaign currently presents customized pricing based on factors such as contacts and selected products, while its higher-level plans emphasize automation, segmentation, CRM, and ecommerce integrations.
Klaviyo’s current free offering is designed for up to 250 active profiles and 500 email sends per month, with pricing and capabilities scaling around customer profiles and messaging.
The comparison therefore isn’t simply about which platform is cheapest. Brevo’s main advantage is the combination of transactional infrastructure, marketing tools, and CRM-oriented functionality in one ecosystem.
How to Set Up Brevo Transactional Email
Step 1: Create Your Account and Configure Sending
Create your Brevo account and access the transactional email section. Add the sender identity you want to use for your application.
For production email, avoid relying on generic consumer addresses. A branded business domain is generally the better foundation for professional transactional communication.
Step 2: Authenticate Your Domain
Add your sending domain to Brevo and complete the required DNS configuration.
Pay particular attention to:
- SPF
- DKIM
- DMARC
- Sender verification
- DNS propagation
Brevo specifically recommends authenticating the domain before configuring transactional email.
Do not skip this step simply because your emails appear to work initially. Authentication is an important part of building a sustainable sending setup.
Step 3: Choose SMTP or API
For a WordPress site or application that already supports SMTP, Brevo’s SMTP relay may be the easiest option.
For a custom SaaS platform, ecommerce application, or development project requiring dynamic data, the API is generally more flexible.
For SMTP, Brevo currently uses smtp-relay.brevo.com, with supported ports including 587, 2525, and 465 depending on the encryption configuration.
For API-based applications, developers can send messages through the transactional email endpoint using an API key.
Step 4: Test, Monitor and Gradually Scale
Before sending large volumes:
- Send test messages to several providers.
- Confirm SPF and DKIM authentication.
- Check links and personalization.
- Test password resets and order notifications.
- Monitor bounces and delivery events.
- Keep your contact database clean.
- Increase sending volume responsibly.
A technically correct API integration cannot compensate for poor list hygiene or consistently unwanted email.
Final Recommendation
Brevo’s transactional email offering is most compelling for businesses that want email delivery infrastructure and customer-engagement tools under one roof.
The choice between SMTP and API is straightforward: SMTP is generally better for simpler integrations, while the API is better when developers need detailed programmatic control. Both approaches can support common transactional use cases such as account notifications, order confirmations, and password resets.
Brevo is particularly attractive to SMBs and growing ecommerce or SaaS businesses that want to avoid stitching together separate tools for newsletters, automation, CRM, and transactional email.
It is not automatically the best choice for every organization. Larger companies with highly specialized infrastructure, advanced data requirements, or enterprise-specific deliverability needs should compare Brevo against dedicated alternatives before making a decision.
Overall, Brevo earns a 4.4/5 editorial rating for its combination of transactional email, marketing automation, CRM, and multichannel functionality. Its strongest advantage is not one individual feature but the breadth of capabilities available within a single platform.
Interested in trying Brevo?
[Insert Affiliate Link / CTA Button]
Editorial note: Pricing, feature availability, sending limits, and plan names can change. Always verify current terms directly with Brevo before purchasing. This review is intended for informational purposes and is not a guarantee of inbox placement or deliverability performance.