Skip to content

What features do you want to see added to Mailgun?

← Feature Requests

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.

107 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Nic Davies shared this idea  ·   ·  Report…  ·  Admin →
completed  ·  AdminChris Farmer (Product Manager, Mailgun) responded  · 

Hi all,


Thanks so much for your feedback here. We've recently released the ability to create multiple API keys for your Mailgun account. Additionally, we've enhanced the security of the keys such that they are now hashed vs just encrypted (this does mean that once you generate a key and close the modal, we will be unable to display it in plain text, so be sure to store your key safely).

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Alfred commented  ·   ·  Report

    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  ·   ·  Report

    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.

  • André Lado Cruz commented  ·   ·  Report

    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.

2 Next →

Feature Requests: Feature Enhancements

Categories

Feedback and Knowledge Base

(thinking…)