DELETE user rate limit/429 too many requests (only 1 request per 10 minutes?)

I am making a service to create new users. Part of that is being able to delete a user. I am running into an issue where I get 429’s when trying to delete more than once in a 5-10 minute period. My understanding is delete is part of the light api which at the most basic level allows 100 requests per day, or 40ish requests per second, which is way more than what I am experiencing. I can only delete a user once every ~10 minutes which is not right.

>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:14:15.826761841 +0000 UTC m=+1.398423623
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:14:45.948567594 +0000 UTC m=+31.520229378
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:15:27.183152381 +0000 UTC m=+72.754814164
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:16:11.519410124 +0000 UTC m=+117.091071917
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:16:47.066023088 +0000 UTC m=+152.637684871
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:17:23.736551798 +0000 UTC m=+189.308213591
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:17:59.855145662 +0000 UTC m=+225.426807455
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:18:11.518789323 +0000 UTC m=+237.090451116
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:18:41.667804824 +0000 UTC m=+267.239466607
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:19:37.876531425 +0000 UTC m=+323.448193218
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:20:25.887051601 +0000 UTC m=+371.458713384
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:21:20.73844259 +0000 UTC m=+426.310104373
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:22:00.155384265 +0000 UTC m=+465.727046048
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:22:35.774273843 +0000 UTC m=+501.345935626
>>>>>>>>>>>>>>>>RETRY CONDITION>>>>>>>>>>>>>>>
2022-05-17 15:23:52.043365806 +0000 UTC m=+577.615027589

Above is the timestamping of my retries. I had it retry once every 30 seconds for a total of 6 retries, and I had to run it 3 times with it finally succeeding on the last run.

First run timestamp: 15:14:15.826761841
Successful run timestamp: 2022-05-17 15:23:52.043365806

There is a ~10 minute gap between my first attempt and when my retry actually deleted the user. The entire time before then I am getting 429 Too Many Requests back.

Some info:

  1. I am hitting /users/{userId} and get a successful delete the first time, then any deletes within about 5-10 minutes will fail with a 429 too many requests.
  2. Not concurrent, one request at a time.
  3. Business or Pro level account being used (auth through JWT, not using my personal account).
  4. No 429/rate limiting on POST or GET, only experience with DELETE (have not tried PATCH/PUT).
  5. Absolutely no where near the daily limit, this is definitely not a daily limit issue.

Here’s a header dump of a failed retry:

http.Header{"Cache-Control":[]string{"no-cache, no-store, must-revalidate, no-transform"}, "Content-Disposition":[]string{"inline;filename=f.txt"}, "Content-Length":[]string{"113"}, "Content-Type":[]string{"application/json;charset=UTF-8"}, "Date":[]string{"Tue, 17 May 2022 15:37:25 GMT"}, "Expires":[]string{"Thu, 01 Jan 1970 00:00:00 GMT"}, "Pragma":[]string{"no-cache"}, "Set-Cookie":[]string{"zm_aid=\"\"; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly", "zm_haid=\"\"; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly", "zm_tmaid=\"\"; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly", "zm_htmaid=\"\"; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly", "cred=1170219DAA4D51DBE17538513AC635B1; Path=/; Secure; HttpOnly", "_zm_ctaid=\"\"; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly", "_zm_chtaid=\"\"; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly", "_zm_ctaid=\"\"; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly", "_zm_chtaid=\"\"; Domain=.zoom.us; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly", "TS01d0dc3f=01bbf59e3b8036c2ebf62e3e7d0b8ca2611490eb711227138331f8d04966abe29b0cc99d7fa5496e13fd67a0ce076d7d98191d3d38; Path=/; Secure; HttpOnly; SameSite=Strict;", "TS01a42040=01bbf59e3b8036c2ebf62e3e7d0b8ca2611490eb711227138331f8d04966abe29b0cc99d7fa5496e13fd67a0ce076d7d98191d3d38; path=/; domain=.zoom.us"}, "Vary":[]string{"Origin", "Access-Control-Request-Method", "Access-Control-Request-Headers"}, "X-Content-Type-Options":[]string{"nosniff"}, "X-Ratelimit-Category":[]string{"Light"}, "X-Zm-Trackingid":[]string{"v=2.0;clid=us02;rid=WEB_79567f7d869bffd07b2ab7fe3a827b9d"}, "X-Zm-Zoneid":[]string{"VA"}}

I’m stumped on why I’m getting too many requests. Anyone have any experience with this?

Thanks.

Hi @mha

Thanks for reaching out to the Zoom Developer Forum, I am happy to help here!
Are you still experiencing this behavior?
I can confirm that the rate limit label for this endpoint is Light

Find our Rate Limits by account type here:

Let me know if you need help with this or if you were able to fix this?
Best,
Elisa

I am still having this issue. It’s been going on for a few weeks now. I know the rate limit should be fine, but I am still experiencing 10 minute delays with deletes with the above conditions.

Any updates? Issue is still persisting. I see others with this issue since 2019.

I don’t have direct experience with deletion rate limits, but I did notice a blog post talking about “lock-key” identifiers that are a separate form of rate limiting, which also has an example of deleting users. Are you able to get a specific error message for this HTTP status code?

I am getting 429 Too Many Requests.

Hey @mha
Could you please open a support ticket here:

And direct it to me, with a link to this post and I will take it from there!
Cheers,
Elisa

@MultiplayerSession :slight_smile: Thanks for chiming in!