Rate limiting

Strivacity implements rate limiting across all of its APIs, on a per instance basis. Each API path has its own independent quota, meaning the limits for one path do not affect the usage of another. 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, brands should stop using 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

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

Rate limits

Strivacity implements the following limits for production instances of Strivacity.

📘

The rate-limiting quotas are applied independently to each API path listed in the table.