Changelog

Email logs are now available in SDKs, which allows you to:

• Query your sent email history directly from code using our official SDKs.

• List messages with rich filtering by recipient, sender, subject, delivery status, date range, engagement (opens/clicks count), sending stream, and more. All filters support operators like contains, equals, and greater/less than.

• Fetch individual message details to get the full event timeline (deliveries, opens, clicks, bounces, spam reports, unsubscribes) along with ESP responses and a signed URL to download the raw .eml.

Similarly, you can now pull your sending statistics directly from your application code, including delivery rates, bounces, opens, clicks, and more.

Available in Node.js v4.5.1, Python v2.5.0, Ruby v2.10.0, PHP v3.11.0, Java v1.2.0, .NET v3.1.1

We've updated the compliance status values returned by the Create sending domain API endpoint to be clearer and more consistent so you can understand what's happening with your domain verification without having to cross-reference documentation:

• pending → awaiting_questionnaire

• pending_cc → awaiting_card_verification

• initial and under_review → under_review (merged into one)

• exhausted → demo_exhausted

Note: These changes are not backward compatible. That said, if you've already added a sending domain via API, you've most likely completed the compliance questionnaire and card verification steps at least once — which means the statuses most likely to affect active integrations (awaiting_questionnaire and awaiting_card_verification) won't be triggered again for your account. The only edge case worth checking is initial, which has been merged into under_review.

You can now access Mailtrap features directly from your terminal using the official Mailtrap CLI. 

What you can do:

• Send emails without leaving your terminal.

• Use it in CI/CD pipelines: a CLI command in a GitHub Action is cleaner than a curl call with JSON parsing. The CLI handles auth, pagination, and output formatting.

• Script your infrastructure, from domain setup and token rotation to contact imports in Bash/Makefile.

• Run one-off tasks where writing an API script is overkill: clean a sandbox, check stats for a domain, rotate a token. 

• Work in SSH sessions, jump boxes, and containers with no GUI access.

• Pull stats by domain, ESP, or category from the command line to spot issues fast.

For a quick installation guide, please check out the official Knowledge Base article.

Team members within the same account can now access and reuse images uploaded by their colleagues in the email editor (campaigns and templates).

This feature is enabled by default for new accounts. Existing customers can request it by contacting support — please note that previously uploaded images won’t carry over to the shared library, so your team would start fresh.

From now on, instead of clicking through dashboard tabs or running manual data hunts, you can ask plain-English questions and get answers without leaving your workflow. 

What you can do:

• Ask questions about your deliverability, bounces, or campaign results and get your actual numbers.

• Debug deliverability issues by asking for bounce rates, ESP breakdowns, or daily trends on demand.

• Check campaign performance or plan limits in a single question instead of navigating to a separate page.

• Ask about best practices for campaign deliverability before a product launch.

From now on, Mailtrap sends all webhook callbacks from a fixed set of Mailtrap-owned IPv4 CIDR blocks: 45.158.83.0/24 and 5.181.200.0/24. The same IP ranges also cover SMTP sending.

This gives you predictable, stable IPs that replace dynamic AWS addresses, a tighter security posture by whitelisting just two /24 blocks instead of the entire AWS IP pool, and consistent test & production behavior since webhook test calls use the same IPs as real traffic. 

Static IPs are especially useful if:

• Your endpoint is behind a corporate or on-premise firewall.

• You're in a regulated industry (finance, healthcare, insurance) with strict network policies.

• Your security team requires an explicit allowlist for all inbound traffic.

• You're automating infrastructure and need static CIDRs for IaC/Terraform templates, including SOC-2 compliant environments that block unknown IPs.

For more information, please read the in-depth Knowledge Base article.

You can now manage API tokens programmatically using five new endpoints — no UI required.

For instance, this allows you to provision sending tokens per customer at signup, automate token rotation without interrupting production, or give AI agents isolated credentials.

Available endpoints:

• List API tokens – Returns all API tokens visible to the current API token.

• Create API token – Creates a new API token for the account with the given name and resource permissions.

• Get API token – Returns a single API token by id.

• Delete API token – Permanently deletes an API token.

• Reset API token – Rotate a token: the old one expires after a short grace period and the new one inherits the same scope and permissions.

The full token lifecycle is covered: from creation to rotation, and each endpoint is scoped to a specific account, project, sandbox, or sending domain.

For more details, please consult the official API documentation.

Hey there!

We’re happy to announce that we’ve added an AI-powered support chat directly in the app. Got a question? Start there! It's the fastest way to get an answer.

And in case our AI assistant isn’t able to help with your issue, simply click on the Start Conversation button and talk to a real human from our customer support team.