Rate Limits on Services¶

Rate limits provide control over the number of requests to a service that can be made per minute. This is useful for managing the capacity of a service, preventing abuse.

A rate limit limits the number of HTTP requests made to a service per minute, independent of how long those requests take. Concurrency limits are available as well, which limit the number of requests that are in progress at any given time.

Rate limits are available on two levels:

• a total limit on the service, for all requests made to it combined
• a per-user limit, with both a default limit per user available as well as configurable limits for individual users

Upon reaching the rate limits, users will receive an HTTP 429 Too Many Requests response code. The response body indicates whether the total or user limit was reached.

It is encouraged to use rate limiting to protect your services from abuse and ensure fair resource usage.

Configuring rate limits¶

Rate limits can be configured through the WebApp and in the API, Client Libraries and CLI.

In the WebApp, the total rate limit for all users and the default limit per user are configurable in the Authentication and limits section of a service.

Additionally, you can set limits for individual users on the Rate limits tab of the service. Limits configured for a (service) user apply on the token used. The limits apply separately per token if a user has multiple.

User level rate limits are only available for services that require authentication, because they are applied per token. The total rate limit on a service is available for all services, both with and without authentication.