# 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:** [Mars 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:** 10

<div class="post-metadata">

**Author:** ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)\
**Post date:** [Septembre 18, 2017, 4:08 UTC](https://meta.discourse.org/t/how-to-bypass-rate-limiter-when-using-an-api-key/25990/10 "2017-09-18T16:08:53Z")

</div>

It’s probably the nginx web server rate limits - it has additional short-term request-counted rate limits. The Discourse rate limits are there to protect against bad behavior and generally expire per day. The nginx ratelimits are there to protect against flooding.

As you just noticed in your edit, the nginx ratelimits are on the order of seconds and minutes.

---

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