API Rate Limits

To ensure the stability and availability of the API for all users, Fireberry enforces rate limits on API requests. Requests that exceed these limits receive a 429 Too Many Requests response.

Rate limits are applied per organization. Requests are counted across all of your organization's API tokens, users, applications, and SDK integrations together, regardless of which IP address a request comes from.

How rate limits work

Every organization has two rate limits:

• A per-minute limit — how many requests you can make within a one-minute window.
• A per-day limit — how many requests you can make within a single day, which resets at 00:00 UTC.

📘

Please note

Both limits are evaluated on every request. A request is rejected as soon as either the per-minute or the per-day limit is exceeded.

Rate limits apply equally to direct API requests and requests made through Fireberry SDKs. SDK operations consume the same quota as equivalent API calls.

Per-minute limit

The per-minute limit caps how many requests your organization can make within a one-minute window.

By default, organizations can make 100 requests per minute. If your subscription includes additional API capacity, higher limits may apply.

When you reach the limit, the API returns 429 Too Many Requests for any further requests until the current one-minute window resets.

Daily limit

The daily limit caps how many requests your organization can make within a single day.

Your daily allowance depends on your subscription plan:

A few important details:

• Every API request counts toward the daily total, including requests made through Fireberry SDKs.
• GET, POST, PUT, DELETE, and query requests all count toward the limit.
• Requests count whether they succeed or return an error.
• The daily counter resets every day at 00:00 UTC, regardless of your local time zone.

When you reach the daily limit, the API returns 429 Too Many Requests for all further requests until the counter resets at the next 00:00 UTC.

🚧

Usage notifications

As your organization approaches its daily limit, the account's primary user is notified by email — once when usage reaches 90% of the limit, and again when it reaches 100%. Each notification is sent at most once per day.

Limits summary

Example 429 response

Here is an example request:

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

And the response once a limit has been reached:

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

Need more requests?

Your available API capacity depends on your subscription plan. If your integration requires additional capacity beyond your current plan's limits, please contact our support team.

Rate limits help maintain a stable, secure, and predictable API experience for all customers while ensuring fair access to shared resources.

If you would like to discuss higher limits, contact our support team.