Multiple API Keys
Option to have multiple API keys, for example: client 1 has the API key exposed, we now have to roll this key, and update all clients using it.
Whereas, if we had multiple keys, we'd only need to roll and update that one client using the key.
Charles Stephenson commented
Not having this feature is making me consider alternative suppliers. We need separate API keys for statistics as well as sending.
Rodrigo Murta commented
This is a must have.
Mark Ryder commented
At least give us an API key per sending domain
Surely this is a significant security risk - if anyone misuses or highjacks a site I cannot close it down without killing all my client sites?
Definitely need this
Joseph Chekanoff commented
This is essential for service-based agencies that work with a large number of domains.
Dung Vu commented
why is this certainly feature not exist in the mailgun? we need it
guys @mailgun this is certainly something you need to work on:
- permissions in to what API key can have access for
- permissions in to what domain
Maybe there more relevant permissions?
Dmitry Popov commented
This is "must have"!
Having single API key for whole account means that when I have several different systems/server working with MailGun - I can't rotate/refresh key only in one system, i must update all my systems at once. Thats' impossible for multi-server scenarios.
Ohad Maishar commented
André Lado Cruz commented
Another good thing is to have api keys per domain too.
So we can use a sandbox api key to test all integrations without compromising the production api.
Noah Heck commented
Sounds very similar to this request as well: https://feedback.mailgun.com/forums/156243-feature-requests/suggestions/18490594-add-multiple-api-keys-or-sub-api-keys-to-be-used-f