Overview
The Dazos API enforces a rate limit of 45 calls per minute, per user. This limit is measured within a rolling 60-second window — not across your total runtime. Understanding how this window works is key to avoiding unexpected throttling, even when your calls appear well-spaced overall.
Why This Matters
Many integrations spread API calls across several minutes and assume that staying under 45 calls in total will prevent throttling. However, if a cluster of calls falls within the same 60-second window and exceeds 45, those calls will fail — regardless of how long your overall script has been running.
For example: making 75 calls over 5 minutes sounds safe, but if calls 1–45 all land within the same 60-second window, calls 46 onward will be rejected until the window resets.
How the Rolling 60-Second Window Works
The rate limit window is rolling, not fixed to a clock minute. This means the window is calculated dynamically from the time of your first call in any given sequence.
The window starts when your first API call is made.
Up to 45 calls are permitted within any 60-second span.
Once 45 calls have been made in that window, additional calls will fail with a rate-limit error until the window resets.
After the window resets, calls will succeed again — until another burst exceeds 45 within a new 60-second window.
⚠️ Important: Simply spreading calls across a total duration (e.g., 5 or 7 minutes) does not guarantee you stay within the limit. What matters is how many calls occur within any single 60-second window.
What a Rate-Limit Error Looks Like
When the limit is exceeded, the API returns a failure response for each call that goes over the threshold. Calls resume succeeding once the 60-second window resets. A common pattern looks like this:
Calls 1–44: Succeed — within the 45-call threshold.
Calls 45–X: Fail — the limit has been hit and the window has not yet reset.
Calls X+1 onward: Succeed again — the 60-second window has reset.
How to Avoid Throttling
To prevent rate-limit errors in your integration, implement the following strategies:
Track calls within the current 60-second window. Build logic into your integration that counts how many API calls have been made in the current window. When you approach 45, pause briefly before making the next call.
Add a retry with exponential backoff. When your code receives a rate-limit failure response, wait before retrying. Use exponential backoff — start with a short delay and increase it with each consecutive failure — to avoid hammering the API and extending the throttle period.
💡 Tip: Do not rely solely on a fixed delay between calls or a total call count over your script's runtime. Active window tracking is the most reliable way to stay under the limit.
Current Rate Limit
The Dazos API rate limit is currently 45 calls per minute per user. This was increased from a previous limit of 30 calls per minute.