Rate limits

The Quickbook API is rate limited per your SLA tier and enforced per client id. Staying within your limit keeps responses fast for every integration on the account.

Rate limit headers

Every response includes headers describing your current allowance:

Header	Description
X-RateLimit-Limit	The maximum number of requests allowed in the current window.
X-RateLimit-Remaining	The number of requests remaining in the current window.
X-RateLimit-Reset	When the current window resets.

HTTP/1.1 200 OK
X-RateLimit-Limit: 120
X-RateLimit-Remaining: 118
X-RateLimit-Reset: 1752316800

Exceeding the limit

When you exceed your allowance, the API returns 429 Too Many Requests. Back off and retry after the window resets rather than retrying immediately.

{
  "status": "429",
  "code": "CONFLICT",
  "type": "System Error",
  "message": "The number of requests exceeded the rate limit."
}

Recommendations

• Watch X-RateLimit-Remaining and slow down before you hit zero.
• Back off exponentially on 429, honouring X-RateLimit-Reset.
• Cache rarely-changing data such as the product list for an account instead of requesting it on every booking.

In the API Reference

The 429 response is documented on every operation in the API Reference.