Rate Limits

Why do we have rate limits?

Rate limits are a common practice for APIs, and they are put in place for different reasons:

  • They help protect against abuse or misuse of the API . For example, a malicious actor could flood the API with requests in an attempt to overload it or cause disruptions in service. By setting rate limits, Zuora can prevent this kind of activity.
  • Rate limits help ensure that everyone has fair access to the API . If one person or organization makes an excessive number of requests, it could slow down the API for everyone else. By throttling the number of requests that a single user can make, Zuora ensures that the most number of people have an opportunity to use the API without experiencing slowdowns.
  • Rate limits can help Zuora manage the aggregate load on its infrastructure . If requests to the API increase dramatically, it could tax the servers and cause performance issues. By setting rate limits, Zuora can help maintain a smooth and consistent experience for all users.

How do these rate limits work?

Rate limits are measured in three ways: RPM (requests per minute), RPH (requests per hour), and RPD (requests per day).

All requests are classified as one of: UI (UI requests), AUTH (authentication requests) or API (API requests, excluding authentication).

Zuora enforces the following rate limits on each tenant:

UI 20,000 1.2M 14.4M
AUTH 2,000 (100 per IP address) 67,500 810,000
API 50,000 2.25M 27M

We recommend you treat these limits as maximums and avoid generating any unnecessary load. We may reduce limits to prevent abuse, or increase limits to enable high-traffic applications. To request an increased limit, contact Zuora Global Support.

In summary:

  • Rate limits are imposed at the tenant level, not user level.
  • Rate limits vary by the type of request being made.

Rate limits in headers

In addition to checking these rate limits, you can also view important information about your rate limits such as the maximum number of requests that are permitted before exhausting the rate limit, the remaining number of requests that are permitted before exhausting the rate limit, and the time until the rate limit resets to its initial state.

You can expect to see the following header fields:

Field Sample Value Description
ratelimit-limit 2250000, 50000;w=60, 2250000;w=3600, 27000000;w=86400 The maximum request limit for the time window closest to exhaustion plus the maximum number of requests that are permitted before exhausting the rate limit for each window: RPM, RPH, and RPD.
ratelimit-remaining 399 The remaining number of requests that are permitted before exhausting the rate limit.
ratelimit-reset 1200 The time until the rate limit resets to its initial state.

In the case of the sample values in the preceding table, it means that you can make 399 more requests at most in the next 1,200 seconds. If you instead make 399 requests in the next 600 seconds, when you make the 400th request you will receive an HTTP 429 - Too Many Requests response as below:

HTTP/1.1 429 - Too Many Requests
Content-Type: application/json
ratelimit-limit : 2250000, 50000;w=60, 2250000;w=3600, 27000000;w=86400
ratelimit-remaining : 0
ratelimit-reset : 600

Retrying with exponential backoff

One easy way to avoid rate limit errors is to automatically retry requests with a random exponential backoff. Retrying with exponential backoff means performing a short sleep when a rate limit error is hit, then retrying the unsuccessful request. If the request is still unsuccessful, the sleep length is increased and the process is repeated. This continues until the request is successful or until a maximum number of retries is reached.

This approach has the following benefits:

  • Automatic retries means you can recover from rate limit errors without crashes or missing data
  • Exponential backoff means that your first retries can be tried quickly, while still benefiting from longer delays if your first few retries fail
  • Adding random jitter to the delay helps retries from all hitting at the same time.

Note that unsuccessful requests contribute to your per-minute limit, so continuously resending a request won’t work.

These rate limits are in addition to, and independent of, concurrent request limits.

Concurrent request limits

In addition to rate limits, Zuora also has concurrent request limits. Like rate limits, concurrent request limits apply at the tenant level but if the Multi-entity feature is enabled in your tenant, the concurrent API request limits apply at the entity level.

Concurrent request limits are classified as one of: TOTAL (most UI and API requests), BIG_PROCESS, BIG_DATA, or CUSTOM.

Type Concurrent Requests

The total request limit applies to all requests except custom requests (which are limited to 200 requests) and OAuth requests (which are unlimited).

Requests Big Data Request Limit Big Process Request Limit Custom Request Limit

Create an account

Create an order

Preview an order


Payment Pages 2.0 (PublicHostedPageLite.do)

AQuA and Data Source Export file downloads green_checkmark    

Usage file uploads

List all payments for an account   green_checkmark