⏲️Rate limits

Understand API rate limits and restrictions.

Rate limits are restrictions that our API imposes on the number of times a user or client can access our services within a specified period of time.

Why do we have rate limits?

Rate limits are a common practice for APIs, and they're put in place for a few different reasons:

• They help protect against abuse or misuse of the API. For example, a malicious actor could flood the API with requests in an attempt to overload it or cause disruptions in service. By setting rate limits, Piloty can prevent this kind of activity.

• Rate limits help ensure that everyone has fair access to the API. If one person or organization makes an excessive number of requests, it could bog down the API for everyone else. By throttling the number of requests that a single user can make, Piloty ensures that the most number of people have an opportunity to use the API without experiencing slowdowns.

• Rate limits can help Piloty manage the aggregate load on its infrastructure. If requests to the API increase dramatically, it could tax the servers and cause performance issues. By setting rate limits, Piloty can help maintain a smooth and consistent experience for all users.

Please work through this document in its entirety to better understand how Piloty’s rate limit system works. We include code examples and possible solutions to handle common issues. We also include details around how your rate limits are automatically increased in the usage tiers section below.

Piloty rate limits work?

There are no individual endpoint specific limits. By default, we allow a steady state number of 5 requests/second per API key.

Rate limit name	Requests
Default	5 per second
short	2 per second

These defaults are not guaranteed, as they may vary with server load and may change in the future. We recommend retrying using exponential backoff. Rate limits are important to prevent abuse and keep the service available to everyone.