Share your feature requests!

Help shape the future of Mailtrap! What's your idea for making it better for everyone?

API endpoint to trigger on-demand DNS re-check for a sending domain

Hi Mailtrap team, We're building a multi-tenant platform where each workspace configures its own sending domain through your Sending Domains API. After a user adds the DNS records, we'd like to give them immediate feedback on whether the domain is verified — ideally by triggering a DNS re-check on demand, the same way the "Re-check DNS Records" button does in your dashboard. We've gone through the available options and hit a wall: GET /api/accounts/{account_id}/sending_domains/{id} returns the last known status, but does not appear to trigger a fresh DNS check — the dns_verified_at timestamp and record statuses don't change on repeated calls. Your automatic re-check runs hourly, so a user who just added their records may have to wait up to an hour to see them pass. We couldn't find any re-check / re-verify endpoint in the public API, nor a webhook event for domain/DNS verification status changes. Our request: could you expose a public, token-authenticated endpoint to trigger an on-demand DNS re-check for a sending domain ? Alternatively, a webhook fired when a domain's verification status changes would also solve our use case. This would let us confirm a domain right after the user sets up DNS, instead of polling and waiting for the hourly cycle. Thanks a lot!

Kick Label 26 days ago

1

General

Show Category Timeline by Hourly

Currently, under "Email API/SMTP" → "Stats" → "Email Categories" → "Timeline", the data is displayed in a daily (date-based) format. Is it possible to add an hourly view as well, so that the statistics can be displayed on an hourly basis? Why is this feature needed? To monitor email sending frequency at a more granular level. The current daily timeline only shows aggregated totals per day, which makes it hard to see how volume is distributed within a day. An hourly view would let us track sending patterns and spot spikes as they happen. How do you intend to use it? We'd use it to monitor hourly sending frequency against our hourly limit, identify unusual bursts or peak-sending periods during the day, and better understand our sending behavior over time.

AGIT CSS about 1 month ago

1
Custom icon

Email API/SMTP

In Progress

Simplified company domain verification

Many senders use a dedicated sending domain while linking to their primary company domain throughout their emails. While this is a common and legitimate setup, when these domains appear unrelated or unverified, the traffic can resemble phishing behavior and trigger additional scrutiny. We want to help customers reduce that risk by introducing a lightweight way to verify ownership of company and customer domains without requiring them to be configured as sending domains. What we're planning A new Company domain tool dedicated to ownership verification Simple DNS-based verification requiring only a verification TXT record No need to configure the domain for sending traffic Reduced risk of compliance reviews or suspended sending caused by domain ownership concerns

services about 1 month ago

Custom icon

Email API/SMTP