Mailtrap Email Sending API

Name: Mailtrap Email Sending API
Brand: Mailtrap Email Sending API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsEmail DeliveryapiKey, bearer9 EndpointsREST

For Agents

Manage Mailtrap sending domains, suppressions, and email logs. Useful for agents that automate deliverability hygiene, troubleshoot bounces, and check sending statistics for an account.

Install Jentic One Beta

Connect the Mailtrap Email Sending API to your agent

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

Remove a recipient from the suppression list to allow future sends

Pull per-account sending statistics over a chosen window for reporting

GET STARTED

Start building with Mailtrap Email Sending API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Mailtrap Email Sending API for, with concrete tasks.

★ Sending Domain Onboarding

Adding a new domain to a transactional email provider is a multi-step DNS workflow. The Mailtrap sending-domain endpoint creates the domain record and returns the SPF, DKIM, and ownership values that need to land in DNS. Agents and onboarding scripts can create the domain, surface the records to the user, and then poll for verification status before enabling sends.

Call POST /api/accounts/{account_id}/sending_domains with example.com, return the DNS records to the user, and verify status with GET /api/accounts/{account_id}/sending_domains/{sending_domain_id}.

Suppression List Hygiene

Hard bounces and spam complaints are added to a suppression list to protect domain reputation. Some addresses end up there in error and need to be removed. The Mailtrap suppression endpoints list every suppressed recipient and delete a single suppression by ID, supporting both bulk audits and one-off remediations triggered from a help-desk workflow.

List suppressions for the account, find the entry matching user@example.com, and DELETE the matching suppression so future sends are allowed.

Delivery Log Investigation

Support and engineering teams need to know exactly what happened to a specific outbound email. The email-logs endpoints list recent messages and return a detailed log entry by sending message ID — including delivery status, response codes, and event timestamps — so agents can answer 'did this customer get the receipt?' without context-switching to the Mailtrap dashboard.

Call GET /api/accounts/{account_id}/email_logs/{sending_message_id} for the message in question and return the delivery status, recipient, and timestamps.

AI Agent Deliverability Assistant

An agent acting as a deliverability assistant can pull sending stats, check suppression status, and verify domain configuration on demand. Through Jentic the agent searches by intent, loads the schema, and executes the right operation while the API token stays in the vault. The same flow plugs into Slack bots, internal copilots, and on-call runbooks.

Use Jentic search 'get mailtrap sending statistics', execute GET /api/accounts/{account_id}/stats for the last 7 days, and summarise the bounce rate for the on-call channel.

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for mailtrap email sending api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/accounts/{account_id}/sending_domains

Create sending domain

GET

/api/accounts/{account_id}/sending_domains

List sending domains

GET

/api/accounts/{account_id}/sending_domains/{sending_domain_id}

Get sending domain

GET

/api/accounts/{account_id}/suppressions

List suppressions

DELETE

/api/accounts/{account_id}/suppressions/{suppression_id}

Delete suppression

GET

/api/accounts/{account_id}/stats

Get sending statistics

GET

/api/accounts/{account_id}/email_logs/{sending_message_id}

Get an email log message by ID

POST

/api/accounts/{account_id}/sending_domains

Create sending domain

GET

/api/accounts/{account_id}/sending_domains

List sending domains

GET

/api/accounts/{account_id}/sending_domains/{sending_domain_id}

Get sending domain

GET

/api/accounts/{account_id}/suppressions

List suppressions

DELETE

/api/accounts/{account_id}/suppressions/{suppression_id}

Delete suppression

Why Jentic?

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

Credential isolation

The Api-Token or bearer token is stored encrypted in the Jentic vault. Agents receive a scoped execution token and Jentic attaches the auth header server-side, so secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'remove email suppression') and Jentic returns the matching Mailtrap operation with its input schema, removing manual doc lookup.

Time to first call

Direct Mailtrap integration: under a day for auth wiring and helper functions. Through Jentic: under 30 minutes — search, load, execute.

FAQs

Specific to using Mailtrap Email Sending API through Jentic.

Why is there no official OpenAPI spec for Mailtrap Email Sending API?

Mailtrap does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mailtrap Email Sending 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 Mailtrap Email Sending API use?

Mailtrap accepts either an Api-Token request header or an HTTP bearer token. Through Jentic the credential is stored encrypted in the vault and injected at execute time so the agent never sees the raw token.

Can I add a sending domain through the API?

Yes. POST /api/accounts/{account_id}/sending_domains creates the domain on the account and the GET endpoint returns the SPF and DKIM records you need to publish in DNS for verification.

How do I look up the delivery status of a specific email?

Call GET /api/accounts/{account_id}/email_logs/{sending_message_id} with the sending message ID returned at send time. The response includes recipient, status, and event timestamps.

What are the rate limits for the Mailtrap Email Sending API?

Rate limits are not declared in the spec — they depend on the Mailtrap plan tied to the account. Check your Mailtrap dashboard before automating high-frequency log lookups.

How do I remove a suppression entry through Jentic?

Run pip install jentic, search 'remove mailtrap suppression', load the schema for DELETE /api/accounts/{account_id}/suppressions/{suppression_id}, and execute with the account and suppression IDs. The Api-Token is injected from the Jentic vault.

Mailtrap Email Sending API

Connect the Mailtrap Email Sending API to your agent

Capabilities

Start building with Mailtrap Email Sending API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs