16 October 2026
Limits
We have introduced rate limiting for non-production Projects. This means the API now returns an error when your API client sends too many requests in a short time. The error response includes headers with details about the current rate limit and the time when the client can retry the request. Before, the platform returned 503 errors with no indication when to retry the request. Exponential backoff was the suggested retry strategy for this case.
The rate limit can vary by service and change over time. Instead of relying on a fixed number, use the values from the rate limit headers in the response to determine when to retry the request.
Please contact support to schedule your load tests to ensure they are not rate-limited.
This change only affects non-production Projects.
Changes:
- [API] Added the TooManyRequests error code, returned with HTTP status code
429.