API Rate Limit Calculator
Whether your expected API traffic fits inside a rate limit — with the headroom left, the burst you can absorb, and how long a backlog takes to drain.
A rate limit is a budget per window: 1,000 calls a minute is about 16.
How the api rate limit calculator works
A rate limit is a budget per window: 1,000 calls a minute is about 16.7 a second. Compare that with what you actually need — clients multiplied by calls each — and the difference is your headroom. Because traffic is bursty, the average fitting inside the limit is not enough: a burst factor shows the peak second, and if callers retry on rejection the backlog can take considerably longer to drain than the burst lasted.
Formula: usage = clients × calls per client; headroom = (limit − usage) ÷ limit
Worked examples
| Inputs | Headroom | Note |
|---|---|---|
| 200 clients × 3 calls against 1,000/min | 40% | 600 calls, 40% headroom, but a 2.5× burst overflows |
| Comfortably inside the limit | 80% | 2,000 calls — 80% headroom |
| Already over | -100% | 200 calls against a 100 limit |
FAQFrequently asked questions
What is a burst factor?
How much busier the peak second is than the average. Traffic driven by a cron job or a broadcast can burst tenfold.
What happens when I exceed a limit?
Most APIs return 429 Too Many Requests with a Retry-After header. Naive clients that retry immediately make the overload worse.
How should I handle rate limits?
Exponential backoff with jitter, plus a client-side queue. Spreading scheduled jobs over the window rather than firing them all on the minute helps most.
Are limits per key or per account?
It varies, and it matters: a per-account limit shared by every server means your own instances compete with each other.
Can I just ask for a higher limit?
Often yes, especially on paid tiers — but fix obviously wasteful call patterns first, such as polling where a webhook would do.
Where these figures come from
- IEC 80000-13 — Information science and technology (quantities and units) — the decimal (kB, MB) versus binary (KiB, MiB) prefixes used throughout
- RFC 4632 — Classless Inter-domain Routing (CIDR) — the address-plan arithmetic behind the subnet calculator
- RFC 1918 — Address Allocation for Private Internets — the private ranges the subnet calculator recognises
- NIST SP 800-63B — Digital Identity Guidelines, Authentication — length over composition rules; the basis of the password guidance here
- NIST SP 800-57 Part 1 — Recommendation for Key Management — key-strength comparisons used by the key-space calculator
- Australian Cyber Security Centre — Essential Eight — national guidance on passphrases and system hardening
Last checked: September 2026. Units follow the SI decimal convention (IEC 80000-13 defines the binary alternatives); network and security figures cite the defining standard.