Too Many Requests The 429 status code indicates that the user has sent too many requests in a given amount of time ("rate limiting"). The response representations SHOULD include details explaining the condition, and MAY include a Retry-After

Get Help
,
1

Ready to post? :magnifying_glass_tilted_right: First try searching for your answer.[Too Many Requests The 429 status code indicates that the user has sent too many requests in a given amount of time (“rate limiting”). The response representations SHOULD include details explaining the condition, and MAY include a Retry-After header indicating how long to wait before making a new request. For example: HTTP/1.1 429 Too Many Requests Content-Type: text/html Retry-After: 3600 Too Many Requests

Too Many Requests

I only allow 50 requests per hour to this Web site per logged in user. Try again soon.

Note that this specification does not define how the origin server identifies the user, nor how it counts requests. For example, an origin server that is limiting request rates can do so based upon counts of requests on a per-resource basis, across the entire server, or even among a set of servers. Likewise, it might identify the user by its authentication credentials, or a stateful cookie. Responses with the 429 status code MUST NOT be stored by a cache.]

3

Hi @md3449907

Welcome to the Auth0 Community!

I understand that you are writing regarding a 429 status code error of Too many requests.

Please let us know if you are facing an issue resulting in this error message, any particular user action, application or behaviour that might cause this. In the mean time, I recommend checking our documentation on Rate Limit Policy which outlines the limits Auth0 enforces to configure your application for the best user experience. At the same time, the Rate Limit Configurations documentation presents the specific Rate Limit Polocies in place per each subscription type.

Looking forward to your input!

Best regards,
Gerald