Why am I hitting QuickBooks or Xero rate limits while testing?

While integrating, you may see your connections fail or slow down because of rate limits coming from the underlying accounting platform — not from Rutter. These platform limits are separate from Rutter's own API rate limit, and they are most commonly hit during heavy testing.

The limits come from the platform, not Rutter

• QuickBooks Online (Intuit): Builder apps have a monthly cap on API calls (for example, 500,000 CorePlus calls per month). When you exceed it, Intuit returns a 429 ThrottleExceeded error (error code 003001) and syncs stop until the quota resets.
• Xero: Xero enforces roughly 60 API calls per minute and 5,000 calls per day per connected organization. Exceeding either pauses syncing for that organization.

Why testing burns through quota fast

Every time a connection is created, Rutter kicks off an initial sync plus any historical sync you have configured. Repeatedly connecting and disconnecting the same test account — or testing across several connections — multiplies those calls quickly. Real end users in production connect once and sync incrementally, so they very rarely approach these limits.

How to reduce the calls you make

1. Optimize your data sync configuration so you fetch only the entities you need and a shorter history window. 📄 How do I set up and optimize my data sync configuration?
2. Avoid repeatedly deleting and recreating the same test connection, since each recreate triggers a fresh full sync.
3. If your production volume genuinely needs a higher QuickBooks ceiling, apply to the Intuit App Partner Program to raise your monthly cap, or wait for the monthly quota to reset.

This is different from Rutter's own API rate limit, which applies per Rutter organization. 📄 Why is my API call being rate-limited?