Validations
What do you think of our Email Validation API? Leave some constructive feedback here along with a brief description of your company’s use case for context purposes.
Please be courteous of others and upvote if you believe strongly enough in an idea!
-
Report false positives
It would be great if we could report a false positive result from the validator (e.g. a non-disposable email address was incorrectly marked as disposable, high risk, or donotsend, etc.) since my two legitimate email domains were marked as such, much as IP blacklist websites have ways of requesting removal from their blacklist.
1 vote -
Support multiple API keys
The v3 API allowed the use of a public API and a private API key. The v4 API only allows the use of the private API key. However, we do not want to disseminate our production private API key to the entire developer staff.
With v3 we defaulted to the public API key to allow developers to work unencumbered while also protecting the more powerful private API key from potential abuse by only having it used in production deployment. No developer has access to production.
The feature request is to either:
1) make v4 API work like v3 API and…1 vote -
provide logs of validation requests
I would like to view and query logs of previously processed validation requests and their results
1 vote -
Add an API entry point to check if an email belongs to a well-known temporary/disposable email provider
Add an API entry point to check if an email belongs to a well-known temporary/disposable email provider.
Currently, if we want to filter out disposable email address we have to monitor corresponding domain manually based on our rejection logs.
Given its position, Mailgun has probably better ways to identify disposable email address domains -- either through manual monitoring of the disposable mail offering or by cross-compiling the rejection logs of its customers.
2 votes
- Don't see your idea?