Rate Limits

Scale uses a number of safeguards against bursts of incoming traffic to help maximize its stability. If you send many requests in quick succession, you might see error responses with status code 429 Too Many Requests.

API limiters

We have several limiters in the API:

• 100 requests per minute

Handling limiting gracefully

important

Continuing to make requests while you are rate limited may result in your integration being banned.

If you receive a rate limit error, you should stop making requests temporarily according to these guidelines:

• If the Retry-After response header is present, you should not retry your request until after that many seconds has elapsed.
• Otherwise, wait for at least one minute before retrying. If your request continues to fail due to a rate limit, wait for an exponentially increasing amount of time between retries, and throw an error after a specific number of retries.

A basic technique for integrations to gracefully handle limiting is to watch for 429 status codes and build in a retry mechanism. The retry mechanism should follow an exponential backoff schedule to reduce request volume when necessary.