We've set API rate limits to protect Katana from API traffic spikes that could put our systems at risk. These limits also help ensure that our platform remains stable and usable for everyone. We evaluate the number of requests sent to an API and will throttle them if they surpass the allowed amount.
By default, Katana API allows 30 requests per 60 seconds.
Your current rate limit quota is provided in the response headers of each request.
| Header | Description |
|---|---|
| X-Ratelimit-Limit | Number of requests available for this application. |
| X-Ratelimit-Remaining | Number of requests remaining in quota. |
| X-Ratelimit-Reset | The timestamp (as milliseconds since epoch) when the quota will reset. |
# Example with the default rate limit of 30
HTTP/1.1 200 OK
Content-Type: application/json
X-RateLimit-Limit: 30
X-RateLimit-Remaining: 29
X-RateLimit-Reset: 1640995199
# If you make more than the allowed requests
HTTP/1.1 429 Too Many Requests
Content-Type: application/json
Retry-After: 15
If the rate limit is surpassed, you will receive a 429 error code indicating that you have sent too many requests within a period. If this happens, you will receive a 'Retry-After' header with a value indicating how many seconds you need to wait before sending another request.
In situations where there is rate abuse, we may reduce limits or, if possible, increase limits to enable a higher amount of traffic.