Brevo Email API
★ Only Publicly Available OpenAPI DocumentCommunicationsEmail DeliveryapiKey16 EndpointsREST
For Agents
Send transactional emails via SMTP relay, manage reusable email templates, track delivery events, and retrieve aggregated sending statistics. Covers 16 endpoints for email delivery and monitoring.
Use for: I need to send a transactional email with a template, I want to check the delivery status of a specific email, Get aggregated email sending statistics for the last 7 days, Retrieve all delivery events for emails sent today
Not supported: Does not handle marketing campaign management, audience segmentation, or SMS messaging — use for transactional email delivery, template management, and delivery monitoring only.
Jentic publishes the only available OpenAPI specification for Brevo Email API, keeping it validated and agent-ready. Send transactional emails with template support, retrieve delivery statistics with event-level granularity, and manage blocked contacts and hard bounces. Supports 16 endpoints covering SMTP email sending, template management, delivery event tracking, and aggregated reporting with per-message UUID-based status lookups.
Install Jentic One Beta
Connect the Brevo Email API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Brevo Email API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Brevo Email API.
Send transactional emails with dynamic template variables, attachments, and per-recipient personalization
Track delivery events including opens, clicks, bounces, and spam reports at per-message granularity
Retrieve aggregated sending statistics with daily breakdowns for deliverability monitoring
Manage reusable email templates with variable placeholders for consistent transactional messaging
Delete hard-bounced contacts to maintain sender reputation and list hygiene
Look up individual email delivery status by message UUID or identifier
Use Cases
Patterns agents use Brevo Email API for, with concrete tasks.
★ AI Agent Transactional Email Delivery
AI agents use the Brevo Email API through Jentic to send transactional emails triggered by application events — order confirmations, password resets, shipping notifications, and account alerts. The agent searches for 'send transactional email' via Jentic, receives the POST /smtp/email operation schema with required fields (sender, to, subject, htmlContent or templateId), and executes the send without parsing Brevo documentation. Integration takes under an hour through Jentic versus 1-2 days for direct API key setup and template configuration.
Send a transactional email using template ID 5 to user@example.com with dynamic variables for order_id and shipping_date, then verify delivery status using the returned message UUID
Email Delivery Monitoring and Analytics
Retrieve detailed delivery event logs and aggregated statistics to monitor email performance and sender reputation. The /smtp/statistics/events endpoint returns per-message events (delivered, opened, clicked, bounced, spam) with timestamps. The /smtp/statistics/aggregatedReport endpoint provides daily rollups of sends, deliveries, opens, clicks, and bounces for trend analysis and alerting on deliverability drops.
Retrieve the aggregated email report for the last 7 days and flag any day where the bounce rate exceeds 3%
Template-Based Email Workflows
Create and manage reusable email templates with dynamic variable placeholders at /smtp/templates. Templates support HTML content with Brevo's templating syntax for personalization — recipient names, order details, account information. The POST /smtp/email endpoint accepts a templateId with params object, rendering the template server-side before delivery. Template updates propagate instantly to all future sends without code changes.
Create a new email template with HTML content containing variables for first_name and activation_link, then send a test email using that template
Sender Reputation and List Hygiene
Maintain sender reputation by identifying and removing hard-bounced and blocked contacts. The DELETE /smtp/deleteHardbounces endpoint purges contacts that have permanently bounced. The GET /smtp/blockedContacts endpoint lists contacts blocked due to bounces, spam complaints, or unsubscribes. Regular automated cleanup prevents deliverability degradation from sending to invalid addresses.
Retrieve all blocked contacts, filter for hard bounces in the last 30 days, and execute the delete hard bounces operation to clean the sending list
Key Endpoints
16 endpoints — jentic publishes the only available openapi specification for brevo email api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/smtp/email
Send a transactional email
GET
/smtp/emails
List transactional emails sent
GET
/smtp/emails/{uuid}
Get email details by UUID
GET
/smtp/statistics/events
Retrieve delivery event logs
GET
/smtp/statistics/aggregatedReport
Get aggregated sending statistics
GET
/smtp/templates
List email templates
DELETE
/smtp/deleteHardbounces
Purge hard-bounced contacts
GET
/smtp/blockedContacts
List blocked contacts
POST
/smtp/email
Send a transactional email
GET
/smtp/emails
List transactional emails sent
GET
/smtp/emails/{uuid}
Get email details by UUID
GET
/smtp/statistics/events
Retrieve delivery event logs
GET
/smtp/statistics/aggregatedReport
Get aggregated sending statistics
GET
/smtp/templates
List email templates
DELETE
/smtp/deleteHardbounces
Purge hard-bounced contacts
GET
/smtp/blockedContacts
List blocked contacts
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Brevo API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — the raw api-key header value never enters the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'send transactional email with template') and Jentic returns matching Brevo operations with input schemas, so the agent can call the right endpoint without browsing documentation.
Time to first call
Direct Brevo integration: 1-2 days for API key setup, template configuration, and delivery tracking. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Brevo Email API through Jentic.
Why is there no official OpenAPI spec for Brevo Email API?
Brevo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Brevo Email API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Brevo Email API use?
The Brevo Email API uses an API key passed in the 'api-key' header with each request. Through Jentic, your Brevo API key is stored encrypted in the MAXsystem vault. Agents receive scoped access tokens so the raw key never enters the agent's context.
Can I send emails with dynamic templates using the Brevo Email API?
Yes. POST to /smtp/email with a templateId field and a params object containing your variable values (e.g., first_name, order_id). Brevo renders the template server-side with your parameters before delivery. Templates are managed via GET and POST /smtp/templates.
What are the rate limits for the Brevo Email API?
Brevo enforces sending limits based on your plan. Free plans allow 300 emails per day. Paid plans start at 20,000 emails per month with no daily limit. The API itself allows multiple concurrent requests but will return 429 status when plan sending limits are reached.
How do I track email delivery status through Jentic?
Search Jentic for 'check email delivery status' to find the GET /smtp/emails/{uuid} operation. Each sent email returns a messageId UUID that you can use to query delivery status including whether it was delivered, opened, clicked, or bounced. Install with pip install jentic and use the search-load-execute flow.
How do I clean hard-bounced contacts from my sending list?
Use DELETE /smtp/deleteHardbounces to purge all contacts that have permanently bounced. To review before deleting, first call GET /smtp/blockedContacts to see the full list of blocked addresses with their block reason and date. Regular cleanup prevents deliverability issues from accumulating invalid addresses.
Can I retrieve per-message event logs with the Brevo Email API?
Yes. GET /smtp/statistics/events returns event-level logs including deliveries, opens, clicks, bounces, and spam reports. Filter by date range, event type, or email address. For individual message tracking, GET /smtp/emails/{uuid} returns the full event history for a specific email by its UUID.
GET STARTED