Zoom API Rate Limits

API and Webhooks
1

Description
I have created a meeting (via the API) and before adding any registrants to the meeting I update the meeting and set registrants_confirmation_email to false. Then I add registrants to the meeting.
When adding registrants to a meeting there is no bulk API and we have to call /meetings/{meetingId}/registrants for each registrant added.

The problem is we are running into API rate limits.

Is there a way for us to get increased API rate limits for our account,or cloud you please provide bulk API endpoints to create a meetings and add users to a meeting.

Also its better if we cloud set registrants_confirmation_email to false when creating a meeting.

Which Endpoint/s?
[post] - /users/{userId}/meetings
[patch] - /meetings/{meetingId}
[post] - /meetings/{meetingId}/registrants

Error
429 Too many requests

Which App Type (OAuth / Chatbot / JWT / Webhook)?
JWT

Additional context
We are prototyping a knowledge sharing web service where people can schedule and join meetings. For this we thought of using zoom to provide the audio/ video conferencing solution.

2

Hey @vishvaka,

We are coming out with improved rate limits in March, however for now please make sure you are making no more than 10 requests per second.

https://marketplace.zoom.us/docs/api-reference/rate-limits

We will also work on an easier way to bulk add registrants via our API.

Thanks,
Tommy

3

We are seeing this same issue. It appears to have started fairly recently, even though our request rates to the Zoom API have not increased. Is “10 requests per second” a new rate limit that you have started enforcing recently? Please provide as much information as you can on this. Is this rate limit per sub-account? or for the master account?

4

Hey Tommy,

We’re running into this issue with our integration as well (Acuity Scheduling, client ID: G7iUS7s2TUSJIOs5E3pICQ. It appears to have started recently (December 22nd).

For a particular account, our integration will make 1 or 2 requests at a time, and intermittently we’ll receive a 10r/s 429 rate limit response.

Is this limit per connected account, or per OAuth client account? We’re a little bit stuck on finding the root cause.

Best,
-Carl

5

Hey @tfarmer.2u, and @acuityscheduling,

What endpoints are you calling? Are rate limits have not changed:

https://marketplace.zoom.us/docs/api-reference/rate-limits

Although due note that in March we are releasing new rate limits:
https://marketplace.zoom.us/docs/guides/announcements#rate-limit-changes

Thanks
Tommy

6

Thanks Tommy, we’re calling the v2/users/:id endpoint — that’s the only one giving us the rate limit error.

We are calling it, however, right after the create-meeting call. It is just 2 calls in total, and the limit error only happens a small percentage of the time.

I did see the note about new rate limits!

Best,
-Carl

7

Hey @acuityscheduling,

You can make 10 requests per second for those endpoints. Double check you are not exceeding that or have a race condition in your code that is making excess requests.

Let us know if you see the issue again.

Thanks,
Tommy

8

Is that 10 requests per second per connected account, or per OAuth client account?

Best,
-Carl

9

Hey @acuityscheduling,

Per App, basically per each key / secret you generate.

Thanks,
Tommy

10

@tommy thank you.

The upcoming rate-limit changes will instead, be limited per-account correct?
https://marketplace.zoom.us/docs/guides/announcements#rate-limit-changes

Best,
-Carl

11

Hey @acuityscheduling,

Correct.

Thanks,
Tommy

12

Sorry I am sidetracking a bit.

@tommy, may I know for the following API endpoint
/metrics/meetings/{meetingId}/participants

Is it counted as “Resource-intensive” that got 10 requests/second for Education. Or “Resource-intensive(Dashboard*)” that got 12 requests/minute? Since the document just say “GET /v2/metrics/meetings” instead of “GET /v2/metrics/meetings/*”, so just wanna clarify.

Further, will the new rate limits be applied on March 1st or just some day in March?

13

Hey @vicker,

These endpoints are the most resource intensive:

Dashboard APIs with following endpoints:
GET /v2/metrics/meetings
GET /v2/metrics/webinars
GET /v2/metrics/zoomrooms
GET /v2/metrics/im

The other dashboard / reports endpoints are standard resource intensive.

The limits will be applied on March 1st.

Thanks,
Tommy

1 Like
14

Thank you again, @tommy

1 Like
15

Happy to help! :slight_smile:

-Tommy

16

Hi, we are receiving error 429 against https://api.zoom.us/v2/users/USER_ID/meetings API while creating a new meeting. The user is an API License user and has 478 meetings scheduled.

We are able to create the meeting with another user but for a specific user we are receiving 429 error.

17

Hey @myyogateacher,

Can you please share the error message?

Thanks,
Tommy

18

We are getting below error from API. The zoom user id for this request is FSFqTNMZSZWR94rMbec5Mw

"Request failed with status code 429 "

19

I’m getting the same error as well with a Discourse plugin that ties into Zoom, I’m not the developer just a user so forgive my ignorance. The developer says the plugin should only be making 2 api calls and should not be hitting the limit in any way.

Here’s the discussion on Discourse: https://meta.discourse.org/t/zoom-webinars-plugin/142711/5

Here is the call log:

{
endpoint: "https://api.zoom.us/v2/users/VI4TWwOvT-SKaycEEMws8w",
response_headers: [
"Set-Cookie: cred=73B256F7AFD1CC7FEA83613B92876F28; Path=/; Secure; HttpOnly"
],
date_time: "2020-03-25 11:42:17",
method: "GET",
request_body: "N/A",
response: {
code: 429,
message: "You have reached the maximum per-second rate limit for this API. Try again later."
},
request_headers: [
"authorization: ******",
"connection: close"
],
request_params: [
],
http_status: "429"
}
1 Like
20

Hey @davidkingham, do you know how many users are using this plugin? Any user using it affects the rate limits.

Thanks,
Tommy