Rate Limit

To ensure stability and availability of the API for all users, Fireberry implements various rate limits. Requests exceeding these limits will receive the response 429 Too Many Requests.

Rate limits are assigned per organization.

Standard rate limits

Our standard rate limit imposes a limit on the number of requests in a specific time frame. The limits are based on one-minute windows.


Important note

The API is limited to 100 requests per minute.

Here is an example request:

GET https://https://api.fireberry.com/api/record/account HTTP/1.1
"tokenid: APITOKENID"

And a corresponding response:

HTTP/1.1 429 Too Many Requests
Content-Type: application/json

Requests are limited based on both the amount of total requests per minute and the size of each request.

Limit TypeMaximum
Number of requests per minute100 requests
Request size per request10 MB

Example: If you have 100 ongoing read requests and try to make another, the API will return a 429 Too Many Requests error. Read and write limits are separate, so the number of read requests won't affect the number of write requests and vice versa.

Concurrent request limits

Along with limiting the overall number of requests in a designated time frame, we also restrict the number of requests processed simultaneously. These restrictions may be altered or new restrictions may be imposed in the future.

HTTP methodMaximum concurrent requests

Cost limits

You can send up to 100 API requests per minute.
If you would like to increase the limit, please contact our support team with a request to increase the number of API requests allowed per minute.

The majority of developers will not be impacted by the API limit, as the coverage is set high enough that it will only affect users who submit requests which affect the API stability. Instead of completely blocking access to the API, the rate limits allow users to continue operating at a standard, secure, and stable pace.