Rate Limiting

To maintain a high level of service for all clients of the platform, we enforce rate limiting on our APIs. These limits are applied based on the authentication credentials being used.

By default, the Connect API allows up to 1000 applied individually by resource endpoint, which should be sufficient for most high-traffic applications. We monitor the number of requests made by each API client and apply throttling if the allowed limit is exceeded.

Depending on our requirements, we may adjust this limit or establish different limits for certain API calls. If the current rate limits do not meet your needs, please contact us via Service Desk Jira support to request an increase.

To prevent your systems from becoming unavailable, we strongly recommend implementing custom logic to handle the rate limiting quotas. For every API request that stays within the current rate limits, you will receive a response with the following HTTP headers:

HTTP Header	Description
x-rate-limit-limit	The number of requests available for this API client.
x-rate-limit-remaining	The number of requests remaining in the current quota.
x-rate-limit-reset	The timestamp (Milliseconds since Unix Epoch) when the quota will reset

If you exceed the rate limit quota, you will receive a 429 Too Many Requests error, indicating that you have sent too many requests within the quota period.

Example:

{
    "message": "Rate limit exceeded ! You reach the limit of 10 requests per 1 minutes",
    "http_status_code": 429
}