Frontegg rate limit policies
Frontegg applies rate limit policies on its APIs in order to protect your application and user management infrastructure, so your users will have a frictionless non-interrupted experience
Handling rate limits in code
Frontegg responds with HTTP Status Code 429 (Too Many Requests) when the rate limits exceed.
Your code logic should be able to handle such cases by checking the status code on the response and recovering from such cases.
If a retry is needed, it is best to allow for a back-off to avoid going into an infinite retry loop.
Limits for Frontegg workspaces
In some of the cases, the limits will be by IP address and in some of the cases, the limits will be by vendor Id.
|Endpoint||Path||Limited by||Rate limit|
|Password reset request||IP address||10 requests per minute|
|Password verification||IP address||10 requests per minute|
|MFA verification||IP address||10 requests per minute|
|MFA recovery||IP address||10 requests per minute|
|Magic link login||IP address||100 requests per minute|
|SSO prelogin||IP address||100 requests per minute|
|User authentication||IP address||100 requests per minute|
|Social login||IP address||100 requests per minute|
|User sign up||IP address||5 requests per minute|
|API token authentication||Workspace||100 per second|
|Vendor Authentication||IP address||30 per second|
|Invite user||IP address||30 per minute|
|Get users (DEPRECATED)||IP address||30 per minute|
Updated about 2 months ago