# How to bypass rate limiter when using an API key?

**URL:** <https://meta.discourse.org/t/how-to-bypass-rate-limiter-when-using-an-api-key/25990>\
**Category:** Self-hosting\
**Created:** [5 مارس 2015، 12:01ص UTC](https://meta.discourse.org/t/how-to-bypass-rate-limiter-when-using-an-api-key/25990 "2015-03-05T00:01:14Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![rcfox](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rcfox/32/115486_2.png) [@rcfox](https://meta.discourse.org/u/rcfox)\
**Post date:** [5 مارس 2015، 1:52ص UTC](https://meta.discourse.org/t/how-to-bypass-rate-limiter-when-using-an-api-key/25990/3 "2015-03-05T01:52:36Z")

</div>

So, just spit-balling here: I don’t know very much about configuring nginx, so maybe this isn’t possible.

How about a /api/ location that would require HTTP auth using the API key, and then rewrites the URL to the normal URL, and doesn’t have a rate limit?

You could perhaps write to the auth config file when API keys are generated or revoked.

---

_[View the full topic](https://meta.discourse.org/t/how-to-bypass-rate-limiter-when-using-an-api-key/25990)._