APIRate limitting

Rate limitting

To ensure the smooth functioning of the Hybiscus API, rate limitting is put in place to allow a smooth and equal service to all users.

Rate limits are in place on the following API endpoints:

  • /api/v1/build-report
  • /api/v1/preview-report
  • /api/v1/get-task-status

The rate limit in place is 60 requests per minute, or equivalent to 1 request per second.

Burst mode

To deal with scenarios where you may send 10 requests very quickly (known as burst mode), but overall no more than 60 requests in a minute, the Hybiscus API allows up to 10 requests to be submitted within this burst mode. In this scenario, the response to the requests will be delayed to spread them out evenly. If more than 10 requests are made in a burst, the 11th request and onwards will be returned the HTTP status code of 503, effectively denying the request.

Exceeding the limit

If more than 60 requests are made per minute, the requests exceeding your limit will be returned a HTTP status code of 503.

Missing something?

Hybiscus is continuously improving and adding new features. If you think we are missing a critical feature, please do not hesitate to contact us and offer your feedback at info@hybiscus.dev