Rate limits
What is rate limits?
Rate limits help us to manage the network traffic for our API and for specific operations within our API. The rate limits sets the maximum number of requests that is allowed for the same account (user) and project in a defined time period. This is applicable to all the endpoints, and to both, the sandbox and production accounts. The limit is chosen to do not affect target applications, but to prevent infrastructure misuse.
The Project API rate limit
The hard rate limit set for the Project API is: 10 requests per second.
If a call exceeds the limit, then the call is aborted and an error is returned. When a hard rate limit is reached, no more calls are accepted until the beginning of the next time period.
Rate limit HTTP headers
The response HTTP headers of any Project API request describe your current rate limit status:
| Header name | Description |
|---|---|
Total-Allowed-Calls | The maximum number of requests you are permitted to make in a specific period of time. |
Remaining-Calls | The number of requests left for the current time window. This appears while limit is not exceed. |
Retry-After | The time you should wait until the next request. This only appears once the limit is exceed. |
Exceeding the rate limit
If you send many calls with our API and reach the set limit, you may get a 429 HTTP status code in the response body, which is an error response that means "Too many requests". This status indicates you have exceed the limit allowed.
A best practice is to examine HTTP headers that indicate the Retry-After parameter so you can wait and pause your requests until then.