canonical: https://jentic.com/apis/sendinblue.com/sendinblue

# Sendinblue Email API

sendinblue.com/main version 1.0.0. The API exposes 25 endpoints secured with apiKey authentication.

## For AI agents

Programmatically send a transactional email, get the list of transactional emails on the basis of allowed filters. Covers 25 operations with apiKey authentication.

## Scope

Does not handle payments, crm, or developer tools - use for communications only.

## Capabilities

- Send a transactional email
- Get the list of transactional emails on the basis of allowed filters
- Delete scheduled emails by batchId or messageId
- Fetch scheduled emails by batchId or messageId
- Monitor Email API operational status and events

## Use cases

### Communications Operations

Use the Email API to perform communications operations programmatically. The API provides 25 endpoints covering core functionality including send a transactional email, get the list of transactional emails on the basis of allowed filters, get the personalized content of a sent transactional email.

Example prompt: Call POST /smtp/email to send a transactional email

### Automated Inbound Management

Automate inbound operations by combining multiple Email API endpoints. Agents can get the list of transactional emails on the basis of allowed filters and then get the personalized content of a sent transactional email in a single workflow.

Example prompt: Call GET /smtp/emails to get the list of transactional emails on the basis of allowed filters, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Email API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'send a transactional email', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /smtp/email | Send a transactional email |
| GET | /smtp/emails | Get the list of transactional emails on the basis of allowed filters |
| GET | /smtp/emails/{uuid} | Get the personalized content of a sent transactional email |
| DELETE | /smtp/email/{identifier} | Delete scheduled emails by batchId or messageId |
| GET | /smtp/emailStatus/{identifier} | Fetch scheduled emails by batchId or messageId |
| POST | /smtp/deleteHardbounces | Delete hardbounces |
| GET | /smtp/statistics/reports | Get your transactional email activity aggregated per day |
| GET | /smtp/statistics/events | Get all your transactional email activity (unaggregated events) |

## Key resources

- **Inbound** — Operations for inbound
- **Smtp** — Operations for smtp

## Why Jentic

- **Setup:** Wiring the Brevo Email API by hand means setting up its api-key header auth against api.brevo.com/v3 and handling status codes and delivery reporting yourself. Through Jentic you install once, import the Email API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The Email API keys transactional records off a message identifier or UUID for lookups rather than a resource you own outright, so scope your agent to the operations it needs, such as sending an email or reading its status. You choose the operations it may call, so ones that change state like deleting hard bounces are not included unless you add them.
- **Credential handling:** Your Brevo API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a transactional email', and Jentic returns the matching Email API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Email API use?

The Email API uses an API key passed in the `api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I send a transactional email with the Email API?

Yes. Use the POST /smtp/email endpoint. The API returns structured JSON responses that agents can parse and act on directly.

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

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

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

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send a transactional email'. Jentic returns the matching Email API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Email API have?

The Email API exposes 25 endpoints covering inbound, smtp operations.

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

Yes. Because you run Jentic One yourself, you decide which Brevo Email API operations your agent may call, so you can grant only what it needs, such as POST /smtp/email to send a transactional email or GET /smtp/emails and GET /smtp/emailStatus/{identifier} to read email status. State-changing operations like POST /smtp/deleteHardbounces or DELETE /smtp/email/{identifier} are excluded unless you add them. Your own rules govern which operations and stored credentials the agent is allowed to use, keeping its access scoped to those specific calls.