# Erroneous status code from API

**URL:** <https://devforum.zoom.us/t/erroneous-status-code-from-api/10028>\
**Category:** API and Webhooks\
**Created:** [March 29, 2020, 6:10am UTC](https://devforum.zoom.us/t/erroneous-status-code-from-api/10028 "2020-03-29T06:10:05Z")\
**Posts on this page:** 11\
**Page:** 2

<div class="post-metadata">

**Author:** ![gourav.ims](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gourav.ims/32/4406_2.png) [@gourav.ims](https://devforum.zoom.us/u/gourav.ims)\
**Post date:** [June 20, 2020, 12:10pm UTC](https://devforum.zoom.us/t/erroneous-status-code-from-api/10028/21 "2020-06-20T12:10:10Z")

</div>

Hi

@abrams,  
I wish I could dust this off with the same smiley.  
However, our workload is live already and we need it fixed at the earliest.  
What we are doing is manually approve using admin portal whenever our students report the problem.  
Its embarrassing but we cannot help it.

We have given up on all the issues reported so far. I believe the API users are limited and zoom is concentrating on security fixes which I agree are most important.

@tommy,  
It happens to all meetings for students randomly.  
We have observed a few more things while approving the requests manually.  
The email ids field is case sensitive on the recording sign-up page but not for the API code at zoom.  
For example if by the API call I register someone with an email id somerandomemail@domain.in and on the sign-up for somebody registers with SOMERANDOEMAIL@DOMAIN.IN it doesnt consider them same and approvals is required separately for the sign-up.

Apart from this the issue still occurs randomly for random meetings even if the emails are used in lower case everywhere.  
For example, same student gets approved for most of the meetings but doesn’t get approved for one.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [June 23, 2020, 6:44am UTC](https://devforum.zoom.us/t/erroneous-status-code-from-api/10028/22 "2020-06-23T06:44:07Z")

</div>

Hey @gourav.ims, @abrams,

I will request prioritization on this - in my opinion this does fall under security features / enhancements, so I will see what I can do.

Our engineers need Meeting IDs that had this issue so they can check the logs to debug the issue. I will private message you requesting these.

In the meantime you could reverse the process and set registration to automatically approve, and then cancel registrants that you don’t have in your list.

> [@gourav.ims](#):
>
> We have observed a few more things while approving the requests manually.  
> The email ids field is case sensitive on the recording sign-up page but not for the API code at zoom.  
> For example if by the API call I register someone with an email id somerandomemail@domain.in and on the sign-up for somebody registers with SOMERANDOEMAIL@DOMAIN.IN it doesn’t consider them same and approvals is required separately for the sign-up.

Nice find, let me see if we can add a case insensitive check. (ZOOM-171840)

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [June 30, 2020, 4:35pm UTC](https://devforum.zoom.us/t/erroneous-status-code-from-api/10028/23 "2020-06-30T16:35:38Z")

</div>

Hey @gourav.ims,

> [@gourav.ims](#):
>
> For example if by the API call I register someone with an email id somerandomemail@domain.in and on the sign-up for somebody registers with SOMERANDOEMAIL@DOMAIN.IN it doesnt consider them same and approvals is required separately for the sign-up.

I just tested this, and you are able to call the [Add Meeting Registrant API](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingregistrantcreate) multiple times for the same users email, uppercase or lowercase, but the join\_url that is returned and sent to them via email is the same each time.

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![naveen](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/naveen/32/9743_2.png) [@naveen](https://devforum.zoom.us/u/naveen)\
**Post date:** [August 5, 2020, 6:24am UTC](https://devforum.zoom.us/t/erroneous-status-code-from-api/10028/24 "2020-08-05T06:24:37Z")

</div>

Hey @tommy

I am also facing the same issue. Could you please help me with a solution.  
meeting IDs which faced this issue: - **922 0635 8992** and **980 7886 7100**

> [@gourav.ims](#):
>
> **Description**  
> We are facing this issue from today where we are getting erroneous status code from zoom.  
> The Updating Recording Registrant’s Status API ([https://marketplace.zoom.us/docs/api-reference/zoom-api/cloud-recording/meetingrecordingregistrantstatus](https://marketplace.zoom.us/docs/api-reference/zoom-api/cloud-recording/meetingrecordingregistrantstatus)) returns 204 (which is success according to documentation). However, the approval remains in the pending state.  
> Surprisingly, the issue happens randomly when we are calling the API from our code as a step during a list of consecutive calls.  
> However, when we call it from postman as an individual call, it processes correctly.  
> It so happens that when we test it from code, if it fails it keeps failing randomly for a very large amount of time (the entire day for example). If it works it works for the entire day at times.
> 
> **Error**
> 
> - Affected API:  
> Updating Recording Registrant’s Status - [https://marketplace.zoom.us/docs/api-reference/zoom-api/cloud-recording/meetingrecordingregistrantstatus](https://marketplace.zoom.us/docs/api-reference/zoom-api/cloud-recording/meetingrecordingregistrantstatus)
> - Sample Meeting ID: XXXXXXXXXX
> - Sample API URL: /meetings/ **XXXXXXXXXX** /recordings/registrants/status
> - Sample Request Object:  
> {‘action’: ‘approve’, ‘registrants’: [{‘id’: ‘YYYYYYYYYYYYYYY’}]}
> - Response code:  
> 204
> - Issue:  
> We are getting status code 204 which as per the documentation indicates - “Registrant status updated.”, which is a success in this case.  
> However, the registrant is not approved when we check from our account on zoom.
> 
> **Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
> JWT
> 
> **Which Endpoint/s?**  
> /meetings/{meetingId}/recordings/registrants/status
> 
> **How To Reproduce (If applicable)**  
> Steps to reproduce the behavior:
> 
> 1. Request URL - /meetings/ **XXXXXXXXXX** /recordings/registrants/status  
> Headers - NA  
> Body - NA
> 2. See error - No error as such but the process doesn’t happen in spite of receiving success (204)
> 
> **Screenshots (If applicable)**  
> Not applicable. The details have been shared above.
> 
> **Additional context**  
> We have automated our flows since we have a huge volume.  
> Also, having manual approval set to “on” and approving only designated users help us secure our recordings.  
> It will seem very odd to see the approval pending message when students will click on the Play Recording button on our website. Also, it will be impossible for us to manually approve these.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [August 6, 2020, 6:55pm UTC](https://devforum.zoom.us/t/erroneous-status-code-from-api/10028/25 "2020-08-06T18:55:17Z")

</div>

Hey @naveen,

Thanks for letting us know, we are investigating the issue. (ZOOM-151205)

-Tommy

---

<div class="post-metadata">

**Author:** ![ycd](https://avatars.discourse-cdn.com/v4/letter/y/278dde/32.png) [@ycd](https://devforum.zoom.us/u/ycd)\
**Post date:** [April 19, 2022, 10:59pm UTC](https://devforum.zoom.us/t/erroneous-status-code-from-api/10028/26 "2022-04-19T22:59:14Z")

</div>

I am getting the same issue. Zoom api sucks, sorry. I hope we move away from zoom asap.

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [April 21, 2022, 10:21am UTC](https://devforum.zoom.us/t/erroneous-status-code-from-api/10028/27 "2022-04-21T10:21:15Z")

</div>

Sorry to hear about your experience, @ycd! May I know the exact error you are encountering? I am happy to help advise alternatives options and best practices.

---

<div class="post-metadata">

**Author:** ![ycd](https://avatars.discourse-cdn.com/v4/letter/y/278dde/32.png) [@ycd](https://devforum.zoom.us/u/ycd)\
**Post date:** [April 21, 2022, 3:27pm UTC](https://devforum.zoom.us/t/erroneous-status-code-from-api/10028/28 "2022-04-21T15:27:17Z")

</div>

That’s the problem. Zoom does not return an error! It just returns a 204, which is a success code, but the updates do not happen. This is VERY annoying.

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [April 22, 2022, 3:05pm UTC](https://devforum.zoom.us/t/erroneous-status-code-from-api/10028/29 "2022-04-22T15:05:09Z")

</div>

I understand your frustration and would like to help. Can you create a new topic and tag me in the post. Also please include the reproducible steps as well.

---

<div class="post-metadata">

**Author:** ![ycd](https://avatars.discourse-cdn.com/v4/letter/y/278dde/32.png) [@ycd](https://devforum.zoom.us/u/ycd)\
**Post date:** [April 25, 2022, 8:11pm UTC](https://devforum.zoom.us/t/erroneous-status-code-from-api/10028/30 "2022-04-25T20:11:16Z")

</div>

> **[Zoom Community](https://community.zoom.com/t5/Meetings/Update-user-settings-using-API/m-p/56303/highlight/true#M28755)**
>
> The Zoom Community: A collaborative place for customers to find solutions, ask questions, and connect with peers.

I tried tagging you in the comment. I dont know how to do it, I hope I tagged the right person.  
hope this helps. Taking 3 weeks to get an answer. Good going zoom!

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [May 12, 2022, 4:35am UTC](https://devforum.zoom.us/t/erroneous-status-code-from-api/10028/31 "2022-05-12T04:35:35Z")

</div>

@ycd,

Sorry for the long wait. I did not receive the tag notification, for future reference you can tag community members via the `@` symbol. By default, everyone who comments on the post will be listed. That aside tested this behavior on my end and can not reproduce the behavior. Can you let us know if you are still seeing the same behavior?

[Previous page](https://devforum.zoom.us/t/erroneous-status-code-from-api/10028.md?page=1)
