Understanding API Rate Limits

To ensure the reliability and performance of our API, monday.com enforces several rate limits. These limits help manage the system load and ensure fair usage across all users. Hitting these limits can lead to temporary errors, but understanding them will help you avoid disruptions.

You can find technical details and examples in our developer documentation on rate limits.

Types of Rate Limits

1. Complexity Limit

This controls how "heavy" a query is. Most users won’t hit this, but if you do, you’ll see an error:

• Error Message: COMPLEXITY_BUDGET_EXHAUSTED
• What to do:
• Only request the data you need
• Avoid overly complex or deeply nested queries
• Use pagination where possible

2. Daily Call Limit

Each API request may consist of multiple API calls. Each account has a daily cap on the number of API calls:

• Error Message: DAILY_LIMIT_EXCEEDED

• What to do:
• Optimize your code to reduce unnecessary calls
• Wait until the limit resets at midnight UTC
• If you are an Admin, you can also purchase additional daily API call capacity with an API calls add-on. It can be done through the admin section, by reaching out to your account team or support. Each unit adds 25,000 daily API calls, and you can purchase multiple units.

3. Minute Rate Limit

Limits the number of queries per minute. If exceeded:

• Error Message: Rate Limit Exceeded
• What to do:
• Reduce the frequency of requests
• Use the Retry-After header to know when you can safely try again.

4. Concurrency Limit

Restricts how many API calls can be handled at once.

• Error Message: maxConcurrencyExceeded
• What to do:
• Send fewer requests in parallel
• Add retry logic to wait before trying again

5. IP Limit

Limits the number of requests from a single IP in a short time (5,000 requests per 10 seconds).

• Error Message: IP_RATE_LIMIT_EXCEEDED
• What to do:
• Pause before retrying as suggested by the retry_in_seconds field in the error response

General best practices

• All requests—even failed ones—count toward your limits.
• Avoid retrying requests immediately after a rate limit error. Always check the retry_in_seconds field in the response.
• If you're using our SDK, it automatically respects rate limit responses and retries after the appropriate wait time.

For developers, we recommend reviewing the full Rate Limits Documentation to understand how limits apply based on your use case and plan.

Need help optimizing your API usage? Contact our support team for guidance.