We strive to provide a top-tier API experience that is reliable and consistent for all users. To maintain a high-quality service and ensure optimal performance, users are subject to the following limits to help manage the API's consumption and throughput:

• Complexity limit
• Daily call limit
• Minute limit
• Concurrency limit
• IP limit
• Resource protection limits

Remembering these limits when using the API is crucial to prevent workflow disruptions and delays.

🚧

All limits and exceptions are subject to change. Additional guidelines may be introduced in the future.

Limits

Complexity limit

Complexity defines the load that each call puts on the API. This limit restricts the heaviness of each query to help prevent excessive load and maintain optimal performance. The limit will not affect most users—the quota is set sufficiently high to impact only users making requests that would compromise the stability of the API.

You will receive a ComplexityException error if you hit the limit.

The limit varies based on how you're making the call:

*Per-minute budgets follow a sliding window and reset 60 seconds after the first API call was made

Calculating complexity

Calculating the complexity of each query in advance can prevent you from hitting the limit. The simplest way to do so is by adding the complexity field to your queries to return the remaining complexity before and after the query, the complexity of the query itself, and when the limit resets.

mutation {
  complexity {
    query
    before
    after
  }
  create_item(board_id:1234567890, item_name:"test item") {
    id
  }
}

Reducing complexity

You can avoid hitting the complexity limit by:

• Requesting only the data you need
• Reducing nested queries
• Utilizing the page and limit arguments

Daily call limit

The daily call limit helps prevent disruptions caused by excessive load from individual accounts, maintains the API service as a free feature across all plans, and controls operational costs to continue delivering value to all our users.

All API calls made through personal tokens, private applications, and public applications (excluding marketplace apps and those developed by monday.com) count towards this limit.

You will receive a DAILY_LIMIT_EXCEEDED error if you hit the limit.

The limit varies based on your monday.com plan:

*Indicates the recommended usage. Please request an increase through the API analytics dashboard if your account consistently exceeds this limit.

Exceptions

A single API request typically deducts one call from your daily limit. However, there are exceptions for specific calls:

Minute limit

The minute limit restricts the number of requests in a given period. It is defined per minute, but you may not need to wait for the full minute before retrying your request. You can use the Retry-After header to determine when you can retry the request.

You will receive a Minute limit rate exceeded error if you hit the limit.

The limit varies based on your monday.com plan and the type of request:

Endpoint-specific minute limits

Each endpoint is subject to the limits mentioned above, but some have additional limits to keep in mind:

Concurrency limit

The concurrency limit restricts the number of requests being handled at any moment. You will receive a Concurrency limit exceeded error if you hit the limit.

The limit varies based on your monday.com plan and the type of request:

IP limit

The IP limit helps control the API traffic coming from a given IP address within a short period. You will receive an IP_RATE_LIMIT_EXCEEDED error if you hit the limit.

Resource protection limit

In rare cases, an internal monday resource might reject the request. In such a case the same retry logic applies.

Guidelines

• All requests count towards the stated limits, even those that fail or return an error. You can prevent unnecessary API usage by waiting for the time indicated in the retry_in_seconds field before retrying the call.
• The API SDK respects the rate-limited responses and waits the appropriate amount of time before automatically retrying the request, up to a configurable maximum number of retries.
• Unless otherwise noted, limits are measured per account, per app. Usage through a personal token counts toward the same limit.