API call limits and throttles

Call limits and throttles for the REST API

Note

Important

Apps that are in the Builder tier of the Intuit App Partner Program have an included limit of 500,000 CorePlus API calls per workspace per month. API calls beyond that limit will be throttled and an HTTP 429 error will be returned. For details see this article.

The following table describes the call limits and throttles for the QuickBooks Online REST API.

Server REST API endpoints Batch endpoint
Sandbox servers
  • 500 requests per minute per realm ID.
  • 10 requests per second, per realm ID and app.
  • 40 emails per day per Realm.
  • Recommended maximum number of payloads in a single batch request is 30.
  • Throttled at 40 Batch requests per minute, per realm ID and app.
  • 120 Batch requests per minute per realm ID.
Production servers
  • 500 requests per minute per realm ID.
  • 10 requests per second, per realm ID and app.
  • Recommended maximum number of payloads in a single batch request is 30.
  • Throttled at 40 Batch requests per minute, per realm ID and app.
  • 120 Batch requests per minute per realm ID.
Note: Requests are performed in a mutli-threaded environment. There may be timing issues leading to unexpected results.
Call limits and throttles for the GraphQL API

The following table describes the call limits and throttles for the QuickBooks Online GraphQL API.

Server GraphQL endpoints
Sandbox and production servers
  • 500 requests per minute per realm ID.
  • 800 requests per minute per app.

In addition to the request-rate limits above, the GraphQL API enforces limits on the complexity of an individual query. A query that exceeds any of the following limits is rejected with an HTTP 400 error:

Limit Maximum value Description
Alias count 20 The number of times a single field is called repeatedly under a different name (alias) in one query.
Root field count 40 The number of separate top-level fields requested in one query.
Query height 1700 The total number of fields requested across the entire query, including nested fields.

If a query exceeds one of these limits, the response looks like this:

{
  "errors": [
    {
      "message": "Request exceeded complexity limits",
      "extensions": {
        "code": "MAX_ALIASES_LIMIT"
      }
    }
  ]
}

The code value in extensions indicates which limit was exceeded: MAX_ALIASES_LIMIT, MAX_ROOT_FIELDS_LIMIT, or MAX_HEIGHT_LIMIT.

If your query exceeds these limits, break it into multiple smaller requests rather than combining many aliases or deeply nested fields into a single query.