The Brevo API: Your First Send, the Key It Needs, and the Limits
The app's code is ready to send a receipt and Brevo answers 401. Usually it's the key, sometimes it's the sender. Here's the request that works, what to set up before it, and how fast each endpoint lets you go.
It can send the email and the text, but nothing tells it when to.
Stuck on Brevo? Let's solve it →POST https://api.brevo.com/v3/smtp/email with an api-key header holding your API key.
Required: a sender (name and email), a to list and a subject, plus exactly one body: htmlContent, textContent or templateId. Put dynamic values in params and reference them as {{params.orderId}}.
Success is a 201 with a messageId. Keep it, because delivery events for that email are tied to it.
Before the first send goes out
Is it an API key, or an SMTP key?
Brevo issues both from the same SMTP & API settings page. The SMTP key is for SMTP relay, and the REST API only accepts an API key in the api-key header.
Is the sender address verified?
Brevo's docs say the sender must be registered and verified. Set up the sending domain too, so receipts don't land in spam.
Is the key stored outside the code?
The key reaches your whole account, contacts included. Keep it in an environment setting and give each system its own key, so one can be revoked alone.
Do you need a template or raw HTML?
A templateId lets marketing edit the receipt in Brevo without a deploy. Raw htmlContent keeps it in your codebase. A single request takes one or the other.
Where do delivery events go?
Transactional webhooks report delivered, hard and soft bounces, blocks, spam complaints, opens and clicks. Decide which system records a bounce before customers start asking where their receipt went.
How fast each Brevo endpoint lets you go
From Brevo's published limits for the general tier, which applies on every plan. Professional and Enterprise get higher ceilings. Going over returns 429 Too Many Requests.
Send it yourself, or let a Brevo automation send it
Your code decides and sends
- Receipts, password resets, booking confirmations: one message, one recipient, right now.
- Your system holds the logic and the content variables.
- Brevo's role is delivery and the event trail.
Your code reports, Brevo decides
- POST /v3/events with an event_name, the contact's identifiers and any event_properties.
- A Brevo automation starts on that event and runs the sequence: follow-ups, waits, branches.
- Marketing can change the sequence without a developer.
Brevo's automations can react to things outside Brevo, but only once something sends the event. Test that the trigger fires on the exact event name you send before relying on it.
A furniture retailer stuck on default order emails
Online furniture retailer · Brevo for marketing and order email
Order confirmations went out as the platform's generic default, because wiring a custom one to the store never seemed worth the effort.
An order posting in the store now fires a branded confirmation through Brevo's API, with the right details filled in.
Customers get the confirmation they expect.
Questions people ask
Does Brevo have an API for transactional email?
Yes. POST /v3/smtp/email sends one message the moment your system calls it, separate from campaigns. There's a matching endpoint for transactional SMS.
Is Brevo the same thing as Sendinblue?
Yes. Sendinblue rebranded to Brevo in 2023 after growing past email into SMS, chat and CRM. Same company and platform, new name. Older code may still point at Sendinblue-era hosts and libraries, so check those when you update.
Is Brevo any good?
Reviews are generally positive, especially from small businesses that want email, SMS and a light CRM without enterprise pricing. The friction developers hit is usually around the edges: the contacts rate limit and getting outside events into automations.
Does Brevo include marketing automation?
Yes. Automations can start and branch on opens, clicks, list and attribute changes, and on custom events you send through the events API. What they can't do is notice an order or a status change in another system on their own.
Does Brevo handle email automation beyond simple campaigns?
Its automation covers welcome series, cart abandonment and other multi-step flows. Flows that depend on a booking, an invoice or a support ticket in another system need that system to report the event, and building that feed is work n-frames does.
Can I use Brevo for newsletters, or do I need my own templates?
Brevo has a drag-and-drop template builder, so you don't need your own design. Custom HTML templates work too, and either kind can be referenced by templateId from the API.