RATE LIMITING

Rate limits govern a single user or device in order to ensure the health and accessibility of an API. In this context, rate limiting can be seen as a form of security.

SLASCONE's rate limiting is based on the number of requests allowed over a period of time. This reduces the impact of clients accidentally or intentionally sending large amounts of traffic to the API, such as during a retry storm.

In SLASCONE, we employ constraints not to restrict you, but to drive optimal API integration, which ultimately ensures optimal system performance.

API V2 LIMITS

Since SLASCONE is a database-centric application, it enforces rate limits on the endpoints that create persistent data. These are typically heartbeat events.

LIMIT EXHAUSTION

In case of limit exhaustion, the API returns a 429 http error (Too Many Requests). Do not retry immediately, since this is going to lead to an infinite blocking loop. Instead, retry after at least 20 seconds.

CUSTOM LIMITS

The default rate limits indicate the maximum values that a typical integration should reach. These limits are meant to ensure optimal system performance. However, these limits can be easily customized, in order to facilitate your scenario.

Just contact us to request custom limits.