Why is my API call being rate-limited?

Last updated: January 29, 2026

When using the Rutter API, you may occasionally encounter rate limit errors. These are safeguards to ensure fair and stable usage of both Rutter's infrastructure and the underlying platform APIs.

There are two types of rate limit errors you might see:

  • 429 Too Many Requests — enforced by Rutter

  • 452 Platform Rate Limit Reached — enforced by the underlying platform (e.g. QuickBooks, Xero)

This article explains what each of these errors means and how to address them.

Rutter Rate Limits (429)

Rutter applies a rate limit of 500 API requests per 10 seconds per organization, regardless of how many connections that organization has. This helps maintain performance and reliability across our system.

If you receive a 429 error, we recommend implementing a retry mechanism with exponential backoff or using a queue to pace your API calls.

Platform Rate Limits (452)

Platform rate limits vary depending on the third-party service you're connecting to. Rutter surfaces these platform-specific limits as a 452 error code so you can handle them distinctly from Rutter-imposed limits.

Here are some examples of platform-specific rate limits: