Rate limiting

Overview

Strivacity implements rate limiting across all of its APIs, on a per instance basis. Rate limits may vary depending on the type of API that is being used.

In general, APIs will respond with HTTP 429 Too Many Requests when the rate limit has been reached.

If the rate limit is being reached then brands should back off on their use of the API until the rate limit period has expired.

Our default rate limiting should facilitate approximately:

1) 144,000 registrations over a 24 hour period

2) 144,000 logins over a 24 hour period

3) 86 million anonymous visitors and consents over a 24 hour period.

If a higher rate limit is required then contact us at [email protected].

Rate Limits

Strivacity implements the following limits for production instances of Strivacity.

NamePathInstance Limit per SecondInstance Limit per MinuteSingle IP Limit per SecondSingle IP Limit per Minute
Administrative APIs/admin/api/v15050010100
Anonymous Visitor API/api/v1/identities100010
Authentication APIs

/login/...
/provider/...
/.well-known/...
/oauth2/...
/userinfo/...

3001000010100

/m
/login/api/v2/forgottenPasswordEmail
/login/api/v2/forgottenPasswordPhone
/login/api/v2/registration

30010000550
/login/api/v2/mfaMethod30010000N/A10

/login/api/v2/forgottenUsername
/login/api/v2/sendAccountActivation

30010000N/A1
Miscellaneous Landings (Errors, Magic Link, etc.)/landing3001000010100
Self Service APIs

/myaccount/...
/go/...

30010000550