# Current Mailgun API key does not work

**URL:** <https://meta.discourse.org/t/current-mailgun-api-key-does-not-work/93661>\
**Category:** Bug\
**Created:** [August 1, 2018, 4:09pm UTC](https://meta.discourse.org/t/current-mailgun-api-key-does-not-work/93661 "2018-08-01T16:09:49Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![oxxi](https://avatars.discourse-cdn.com/v4/letter/o/53a042/32.png) [@oxxi](https://meta.discourse.org/u/oxxi)\
**Post date:** [August 1, 2018, 4:09pm UTC](https://meta.discourse.org/t/current-mailgun-api-key-does-not-work/93661/1 "2018-08-01T16:09:50Z")

</div>

It appears that Discourse has hard-coded a regex check for the Mailgun API key. Mailgun’s API keys have undergone a format change to prevent spammers from scrapping publicly accessible repositories for Mailgun API keys. The regex check would need to be addressed to allow API keys that do not match the old naming convention or remove the restriction on the discourse instance locally.

---

_[View the full topic](https://meta.discourse.org/t/current-mailgun-api-key-does-not-work/93661)._
