Rate Limiting

Overview

To protect the service for all customers, AccelerationCloud APIs are subject to rate limiting. These limits mitigate denial-of-service attacks and abusive actions such as rapidly updating configurations, aggressive polling, and concurrency, or excessive API calls.

The AccelerationCloud API rate limits are divided into several categories: API authentication, platform, cores, and other endpoints. Each category has APIs with rate limits that are enforced individually as well as a cumulative rate limit. The rate limits vary by service subscription.

🚧

We enforce the following per-minute limits and per-day limits

If any org-wide rate limit is exceeded, a 429 status code is returned. You can anticipate hitting the rate limit by checking AccelerationCloud's rate-limiting headers. Additionally, you are sent an email notification when your org approaches its rate limit.

Metrics

Rate limiting is implemented at the client level and is counted over a 24-hour window for all authenticated calls.

The maximum number of authentication requests in a 5-second window is 10

API Request

If the API request breaches a limit, the request will be rejected with the 429 Too Many Requests response code. The response will also contain X-RateLimit-Retry-After header to indicate how long an API client should wait (in seconds) before making another request.

📘

Upgrade specific category

To request an increase in rate limits, contact Acceleration Cloud Support and provide context around the use case for your request.

{
    "code": 429,
    "errorMessage": "Request rate limit has been exceeded",
    "error": null,
    "data": null
}