Convert an API rate limit (requests/s, /min, /h, or /day) into per-client requests per second, daily total, and minimum call interval — with support for multiple concurrent clients.
Inputs
Rate Limit
≥ 1
The maximum number of requests the API allows within the chosen time window.
The time window the rate limit applies to.
≥ 1
How many clients share this rate limit. Each client receives an equal share of the budget.
Results
Enter a value to see results.
Per-Client Budget
The effective call rate available to each client: ... req/s based on 100 requests per window divided among 1 clients.
The shortest time in milliseconds each client should wait between consecutive calls to stay within the rate limit: ... ms.
Daily Total
The total number of requests each client can make in 24 hours at the sustained rate of ... req/s.
Frequently Asked Questions (FAQ)
How do I convert 100 requests per minute to per second?
Divide by 60: 100 ÷ 60 ≈ 1.67 requests per second. More generally, divide the rate limit by the number of seconds in the window — 1 for per-second limits, 60 for per-minute, 3 600 for per-hour, and 86 400 for per-day limits.
This calculator does the conversion automatically and also divides the result by the number of concurrent clients, so you can plan the budget each client actually has available.
What call spacing avoids HTTP 429 errors?
Wait at least the minimum call interval between consecutive requests from each client. For example, a shared limit of 100 requests per minute with 5 concurrent clients means each client should wait at least 3 000 ms (3 seconds) between calls.
In practice, add a small buffer (10–20 %) for clock drift and network jitter. Many rate-limit schemes also allow short bursts above the sustained rate — consult the API documentation for the provider's burst policy.