Rate Limits
The Nekosia API applies rate limits to ensure the stability and security of the services. These limits are designed to prevent server overload and ensure equal access to resources for all users. Below are the detailed limits for different parts of the service.
nekosia.cat
- Main: A maximum of
96 requeststo the server within140 seconds. - Comments: A maximum of
3 requeststo the server within30 seconds.
api.nekosia.cat
- A maximum of
320 requeststo the server within5 minutes.
cdn.nekosia.cat
- A maximum of
500 requeststo the server within5 minutes.
Cloudflare Rate Limits
We use Cloudflare to ensure the security and stability of our services. Therefore, Cloudflare may apply its own request limits. If these limits are exceeded, the user will receive an HTTP status code 429.
HTTP 429 Response
If the rate limits are exceeded, the server will return an HTTP 429 response, which means Too Many Requests.
What Next?
Hmm... So, what now...
Consequences of Exceeding Limits
Exceeding the limits results in temporary blocking of access to the API for the user or server from which the request originated. The block may last from a few minutes to a few hours, depending on the severity of the limit violation. In the case of repeated violations, the user may be permanently blocked. Such actions will be treated as an attempt to overload the server or a DDoS attack. Attack incidents will be reported to abuseip.com.
Contact and Support
If you have any questions or issues related to rate limits, contact us by sending an email to support@nekosia.cat.
Rate Limit Changes
We recommend regularly checking the API documentation, as limits may sometimes be changed by the team.