canonical: https://jentic.com/apis/developers.brevo.com/brevo

# Brevo Email API

The Brevo Email API sends transactional emails and reports on how they performed. You can send a message, look up its delivery status, pull aggregated and event-level statistics, and manage the reusable templates and blocked-contact list behind your sending. It covers the transactional email side of Brevo rather than marketing campaigns or CRM.

## For AI agents

Send transactional emails through Brevo, check their delivery status, read aggregated and event-level statistics, and manage email templates and blocked contacts.

## Scope

Covers transactional email only. Does not handle marketing campaigns, SMS, or CRM contact management, which live in other parts of the Brevo platform.

## Capabilities

- Send a transactional email to one or more recipients
- Look up the delivery status of a sent message
- Read aggregated and event-level sending statistics
- Create, update, and list reusable email templates
- Review and manage the list of blocked contacts
- Remove hard bounces to clean the sending reputation

## Use cases

### AI Agent Transactional Email Sender

An AI agent can send confirmations, alerts, and receipts on behalf of an application by calling the send operation with a template or inline content. Through Jentic the agent finds the send operation by intent and supplies recipients and variables, so a support or workflow agent can email users without a developer wiring the endpoint by hand.

Example prompt: Send a transactional email to a customer using a named template and return the resulting message id

### Delivery Monitoring Assistant

A monitoring agent can confirm that important emails reached recipients and surface problems early. The API returns per-message delivery status plus aggregated and event-level statistics, so an agent can report opens, clicks, and bounces or flag a message that failed to deliver, all without a person checking a dashboard.

Example prompt: Fetch delivery events for the last day and report how many messages bounced or were opened

### Template and Sender Hygiene

An operations agent can keep transactional sending healthy by maintaining templates and cleaning the contact list. The API lets an agent create or update templates, review blocked contacts, and clear hard bounces, so a team can standardize messaging and protect sender reputation as part of a routine workflow.

Example prompt: List the available templates, then remove hard bounces to clean the sending list

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/smtp/email` | Send a transactional email |
| GET | `/smtp/emails` | List sent transactional emails |
| GET | `/smtp/emailStatus/{identifier}` | Get the status of a sent email |
| GET | `/smtp/statistics/events` | Read event-level sending statistics |
| GET | `/smtp/statistics/aggregatedReport` | Read an aggregated sending report |
| GET | `/smtp/templates` | List transactional email templates |
| POST | `/smtp/templates` | Create a transactional email template |
| GET | `/smtp/blockedContacts` | List blocked contacts |

## Key resources

- **Transactional Emails** — Send messages and look up their delivery status by identifier
- **Statistics** — Read aggregated reports and event-level delivery, open, and click data
- **Templates** — Create, update, list, and delete reusable transactional email templates
- **Blocked Contacts** — Review blocked contacts and remove hard bounces from the list

## Why Jentic

- **Setup:** Wiring Brevo by hand means creating an API key, adding it to the api-key header on every call, and mapping the send and statistics operations. Through Jentic you install once, import Brevo from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** You decide which Brevo operations the agent may use. Allow it to read statistics without sending, or allow sending while blocking template deletion, and because message and template ids sit in the URL path, a rule can restrict it to specific resources.
- **Credential handling:** Your Brevo API key is stored encrypted by your own Jentic One instance and injected into the api-key header at execution time. It never enters the agent's prompt, logs, or context window.
- **Discovery method:** Agents search Jentic by intent such as 'send a transactional email' or 'get email statistics', and Jentic returns the matching Brevo operation with its input schema so the agent calls the right endpoint.

## Related APIs

- **Mailjet** — Mailjet is a transactional and marketing email API with similar send and tracking features.
- **Mailchimp** — Mailchimp offers transactional and marketing email with audience management.
- **Sendinblue** — Sendinblue is Brevo's former brand and exposes closely related email operations.

## FAQ

### Is there a Brevo MCP server?

You don't need an MCP server to give your agent the Brevo Email API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can send transactional emails and read statistics. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

### Can I restrict what my agent is allowed to do with the Brevo Email API?

Yes. You choose which operations the agent may call, so you can allow it to read delivery statistics but not send mail, or allow sending but block template deletion. Because template and message ids appear in the URL path, a rule can also pin the agent to specific templates, and every call is logged.

### What authentication does the Brevo Email API use?

The Brevo Email API authenticates with an API key, passed in the api-key request header per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and added to each request at call time, so it never appears in the agent's prompt or logs.

### Can my agent check whether an email was delivered with the Brevo Email API?

Yes. After sending, the agent can look up a message by its identifier to read delivery status, and it can pull aggregated reports or per-event data to see opens, clicks, and bounces. This lets a monitoring agent confirm delivery and flag failures automatically.

### What are the rate limits for the Brevo Email API?

The OpenAPI spec does not specify rate limits. Check the Brevo developer documentation at https://developers.brevo.com for the current per-plan sending and request limits before running high-volume workloads.

### How do I send transactional email through Jentic?

Search Jentic for 'send a transactional email', import the Brevo operation, and store your API key once. Your agent then sends messages and reads their statistics on demand. To run it on your own infrastructure, install Jentic One from its GitHub repo.