Commerce - Rate Limits

title: Rate limits description: >- Learn how Zoom API rate limits are enforced by account type, including limits for Meeting SDK, Video SDK, Zoom Phone, and Contact Center APIs, plus error handling best practices.

Rate limits define the maximum number of requests a single account can make within a given period of time. When you exceed a rate limit, the API request will fail and return a HTTP 429 status code.

Rate limit details

• Rate limits are applied at the account level. These rate limits are shared by users for all apps installed on the account.
• Rate limits are applied based on your account plan. Increased rate limits are available for all Business, Enterprise, Education, and Partner accounts. See pricing for details.
• APIs are grouped by request type with unique rate limits for each.
  • Request Type - the rate-limit category an API belongs to (Light, Medium, Heavy, or Resource-intensive), which determines the quota it uses. Each API endpoint's documentation lists this as its Rate Limit Label.
  • Rate Limit Type - how that quota is enforced, either per second (QPS) or as a daily limit.
• Some APIs have special rate limits at the user-level.
• Some APIs have limits on concurrent operations performed on a single resource.

The Zoom API uses rate limits to ensure that API request traffic is efficiently handled. We may alter these limits as needed. See the changelog for details.

Rate limits by account type

Rate limits are applied based on the account plan, either Free, Pro, and Business+ (which includes Business, Education, Enterprise & Partners). Meeting SDK is included in these account types. This outlines the rate limits applied to APIs by rate limit type for each account plan.

* Subject to combined daily rate limits:

• Pro: 30,000 requests/day for heavy and resource-intensive APIs
• Business+: 60,000 requests/day for heavy and resource-intensive APIs

Zoom Build account rate limits

The Zoom Build account uses the Pro rate limit. See Plans & Pricing for Developer for pricing.

User-level rate limits

These are some special user-level rate limits.

Meeting and Webinar create/update requests

• 100 create/update requests per day (UTC) per user
• Applies to all Meeting/Webinar IDs hosted by the user
• Resets at 00:00 UTC daily

Registration requests

• 3 requests per day (UTC) for the same registrant in the same meeting/webinar

Registrant status requests

• 10 requests per day (UTC) for the same registrant in the same meeting/webinar

Zoom Phone APIs

* Daily limit shared between heavy and resource-intensive APIs

Zoom Contact Center APIs

Zoom Contact Center APIs are rate limited by request type and applied based on the account plan:

* Daily limit shared with resource-intensive APIs

Concurrent request limits

Concurrent requests to a single resource may fail with a 429 HTTP status code. For example:

Too many concurrent requests. A request to disassociate this user has already been made.

Error handling best practices

• Handle 429 status codes by implementing a wait before retrying.
• Build retry mechanisms for failed requests.
• Reduce request frequency where possible.
• Cache responses to minimize repetitive requests.
• Use webhooks for data change events instead of polling.

Error table

This table lists errors you may encounter.