Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / Communications / Email API
Email API logo

Sendinblue Email API

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

Use for: I need to send a transactional email, I want to the list of transactional emails on the basis of allowed filters, Search for the personalized content of a sent transactional email, Find all scheduled emails by batchid or messageid

Not supported: Does not handle payments, crm, or developer tools — use for communications only.

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

Jentic One on GithubView OpenAPI Document

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.

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

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

Monitor Email API operational status and events

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

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)

Why Jentic?

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

Credential management

Credential isolation

Email API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Intent-based discovery

Agents search by intent (e.g., 'send a transactional email') and Jentic returns the matching Email API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Time to first call

Direct Email API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio

→

Alternative communications API

Choose Twilio when you need a different approach to communications operations

Alternative

Sendgrid

→

Alternative communications API

Choose Sendgrid when you need a different approach to communications operations

Complementary

Pusher

→

Complementary communications API

Choose Pusher when you need a complementary approach to communications operations

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

GET STARTED

Start building with Email API

Explore with Jentic
View OpenAPI Document