# Registering somebody with API for a Cloud Recording

**URL:** <https://devforum.zoom.us/t/registering-somebody-with-api-for-a-cloud-recording/44973>\
**Category:** API and Webhooks\
**Tags:** webinar\
**Created:** [March 5, 2021, 2:54pm UTC](https://devforum.zoom.us/t/registering-somebody-with-api-for-a-cloud-recording/44973 "2021-03-05T14:54:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jahrralf](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jahrralf/32/30236_2.png) [@jahrralf](https://devforum.zoom.us/u/jahrralf)\
**Post date:** [March 5, 2021, 2:54pm UTC](https://devforum.zoom.us/t/registering-somebody-with-api-for-a-cloud-recording/44973/1 "2021-03-05T14:54:41Z")

</div>

**Description**

We have a cloud recording an want to collect who is watching it. Also we want to play back the recording in an iframe.

Because the registration form cannot be displayed in an iframe, we wanted to register the viewers with the API and directly redirect them to their recording URL. For this, we use the following API call:

> **[Create a Recording Registrant - Cloud Recording - Zoom API - API Reference](https://marketplace.zoom.us/docs/api-reference/zoom-api/cloud-recording/meetingrecordingregistrantcreate)**
>
> Cloud Recordings of past Zoom Meetings can be made on-demand. Users should be registered to view these recordings.
> 
> Use this API to register a user to g...

But in the end we only get a personalized (?) share\_url, which again leads to the registration form. What is this URL for if not for playback? Why would we register somebody with the API if not for being able to bypass the registration?

The meeting ID is **92278343819**

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

---

<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:** [March 8, 2021, 4:56pm UTC](https://devforum.zoom.us/t/registering-somebody-with-api-for-a-cloud-recording/44973/2 "2021-03-08T16:56:15Z")

</div>

Hey @jahrralf ,

Please provide steps to reproduce the issue so we can look into this further. 🙂

When you are creating the cloud recording registrant, [are you approving them](https://marketplace.zoom.us/docs/api-reference/zoom-api/cloud-recording/meetingrecordingregistrantstatus)?

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![jahrralf](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jahrralf/32/30236_2.png) [@jahrralf](https://devforum.zoom.us/u/jahrralf)\
**Post date:** [March 8, 2021, 5:49pm UTC](https://devforum.zoom.us/t/registering-somebody-with-api-for-a-cloud-recording/44973/3 "2021-03-08T17:49:17Z")

</div>

Hi!

Yes, they are approved automatically. Also we tried approving them through the API. The response did not change, it was as follows:

```auto
  array(4) =>
    [registrant_id] =>
      string(22) =>
        "OTmXknnVRGimvREDACTED"
    [id] =>
      integer(9227834REDACTED)
    [topic] =>
      string(51) =>
        "State of the IPO Market and Virtual Lessons Learned"
    [share_url] =>
      string(121) =>
        "https://REDACTED"

```

Opening this share URL brought us back to the registration. Going through the registration with the form played the video.

Thanks,

Ralf

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [March 9, 2021, 8:54pm UTC](https://devforum.zoom.us/t/registering-somebody-with-api-for-a-cloud-recording/44973/4 "2021-03-09T20:54:46Z")

</div>

Hey @jahrralf,

Thank you for providing additional information. I tested this with my account and saw the same behavior. I also noticed that the `share_url` returned by the API is missing some parameters that are included when you manually approve a registrant through the Zoom Web Portal.

When using a link from an email, the video was played as we expect. I’ve since reached out to our engineering team to see if they are able to confirm this as a bug and provide a fix. (ZOOM-254383)

I’ll be sure to keep you updated here as I have more information.

Thanks,  
Max

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [March 11, 2021, 2:08am UTC](https://devforum.zoom.us/t/registering-somebody-with-api-for-a-cloud-recording/44973/5 "2021-03-11T02:08:02Z")

</div>

Hey @jahrralf,

I’m happy to report that our engineering team confirmed this as a defect and will provide a fix in a future release. I don’t have an ETA on the issue just yet but I’ll keep you updated here.

Thanks,  
Max

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [April 10, 2021, 12:08pm UTC](https://devforum.zoom.us/t/registering-somebody-with-api-for-a-cloud-recording/44973/6 "2021-04-10T12:08:19Z")

</div>

Closed on April 10, 2021, 12:08pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.