Mandrillapp Mandrill

Name: Mandrill API
Brand: Mandrill
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsEmail DeliveryapiKey90 EndpointsREST

For Agents

Send transactional emails through Mailchimp's Mandrill — including templated sends, scheduling, suppression management, and inbound routing — over a JSON POST API.

Install Jentic One Beta

Connect the Mandrill to your agent

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

Send a transactional email with HTML, text, attachments, and merge variables

Render and send messages from a stored Mandrill template by template name

Schedule a message for later delivery and reschedule or cancel it before send

GET STARTED

Start building with Mandrill API

Explore with Jentic

View OpenAPI Document

Mandrill is Mailchimp's transactional email service for sending data-driven, one-to-one messages such as receipts, password resets, and order confirmations. The API is a long-standing JSON-over-POST surface organised by resource group — messages, templates, users, webhooks, inbound, exports, subaccounts, tags, urls, ips, metadata, rejects, whitelists, and senders — with the API key sent in the request body of every call. It supports template-driven sends with merge variables, click and open tracking, scheduled delivery, suppression management, and inbound email routing.

Use Cases

Patterns agents use Mandrill API for, with concrete tasks.

★ Transactional email for SaaS notifications

Product teams need reliable delivery for password resets, signup confirmations, and billing receipts. Mandrill's POST /messages/send.json and POST /messages/send-template.json endpoints accept the recipient, subject, and either raw HTML or a stored template name with merge variables, returning a per-recipient send status. The result is a per-message delivery record that can be checked later via the search and content endpoints.

Send the 'password-reset' template to user@example.com with a reset_url merge variable and confirm the send was queued.

Suppression list maintenance

Teams running long-lived transactional senders need to keep bounces and complaints out of future sends to protect deliverability. POST /rejects/list.json returns the current suppression list, /rejects/add.json adds an address, and /rejects/delete.json removes one. Wiring these into a churn or refund flow keeps the sender reputation clean.

Add hardbounce@example.com to the Mandrill rejects list with reason 'invalid' and verify it appears in the next list call.

Inbound email parsing for support workflows

Support tools often need to accept inbound email replies, parse them, and create or update tickets. Mandrill's inbound endpoints — POST /inbound/add-domain.json and POST /inbound/add-route.json — register a domain and forward parsed messages as JSON to an HTTPS endpoint. The application receives the parsed body, headers, and attachments, with no MX or MIME parsing on its side.

Register the inbound domain reply.example.com in Mandrill and add a route forwarding all messages to https://app.example.com/inbound.

Agent-driven transactional email

An AI agent acting on a user's behalf — confirming a booking, sending a follow-up — needs to dispatch email without holding the Mandrill API key in its context. Through Jentic the agent searches by intent, loads the messages send schema, and executes with a scoped credential. The send is logged on Mandrill with the agent's audit metadata attached.

Given a booking record, send a confirmation email from the 'booking-confirmed' template to the customer and store the returned message id.

Key Endpoints

90 endpoints — mandrill is mailchimp's transactional email service for sending data-driven, one-to-one messages such as receipts, password resets, and order confirmations.

METHOD

PATH

DESCRIPTION

POST

/messages/send.json

Send a transactional message

POST

/messages/send-template.json

Send a message rendered from a stored template

POST

/messages/search.json

Search past messages by tag, sender, or recipient

POST

/templates/list.json

List stored templates

POST

/rejects/list.json

List suppressed addresses

POST

/rejects/add.json

Add an address to the rejects list

POST

/inbound/add-route.json

Add an inbound parse route

POST

/webhooks/add.json

POST

/messages/send.json

Send a transactional message

POST

/messages/send-template.json

Send a message rendered from a stored template

POST

/messages/search.json

Search past messages by tag, sender, or recipient

POST

/templates/list.json

List stored templates

POST

/rejects/list.json

List suppressed addresses

Why Jentic?

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

Credential isolation

Mandrill API keys are stored encrypted in the Jentic vault. The key is injected into the JSON request body at call time — agents never see it, so leaked transcripts cannot expose the sending credential.

Intent-based discovery

Agents search Jentic by intent (e.g. 'send a transactional email') and Jentic returns the matching Mandrill /messages/send.json operation with its input schema, so the agent can dispatch without reading the Mandrill docs.

Time to first call

Direct Mandrill integration: 1-2 days for auth, retry, and webhook plumbing. Through Jentic: under an hour — search, load schema, execute.

FAQs

Specific to using Mandrill API through Jentic.

What authentication does the Mandrill API use?

Mandrill uses an API key passed inside the JSON request body as the 'key' field on every call, rather than a header. Through Jentic, the API key is stored encrypted in the vault and injected into the request body at execution time, so the raw key never appears in the agent's prompt or transcript.

Can I send a templated email through the Mandrill API?

Yes. POST /messages/send-template.json takes a template_name plus an array of merge variables and recipient overrides, renders the stored template, and queues the send. Use POST /templates/list.json to discover the available template names in the account.

What are the rate limits for the Mandrill API?

Mandrill applies an hourly send quota that varies by account reputation rather than a fixed per-second limit. The /users/info.json call returns the current hourly_quota, sent, and reputation values, which is the documented way to check headroom before a large batch send.

How do I send a transactional email through Jentic?

Run pip install jentic, then search Jentic for 'send a transactional email through mandrill'. Jentic returns the POST /messages/send.json operation, you load its schema, and execute with the to, from_email, subject, and html fields to dispatch the message.

Does Mandrill support inbound email through this API?

Yes. POST /inbound/add-domain.json registers an inbound domain (after MX records point at Mandrill), and POST /inbound/add-route.json maps a pattern on that domain to an HTTPS endpoint. Mandrill posts the parsed message JSON to that endpoint when mail arrives.

Is the Mandrill API free?

Mandrill is a paid add-on to a Mailchimp account, billed per block of emails. There is no free tier on the transactional API itself; the cost-per-block is published on the Mailchimp transactional pricing page and is independent of the Mailchimp marketing plan.

Mandrillapp Mandrill

Connect the Mandrill to your agent

Capabilities

Start building with Mandrill API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs