Sendinblue Email API

Name: Email API
Brand: Email API
Availability: InStock

✓ Official Vendor SpecCommunicationsEmail DeliveryapiKey25 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Email API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 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.

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 | sh

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 instance

Jentic 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 Email API.

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

GET STARTED

Start building with Email API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Email API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

25 endpoints — sendinblue.

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)

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Email API through Jentic.

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.

Sendinblue Email API

Connect the Email API to your agent

Capabilities

Start building with Email API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs