# Zoom Add Recording Registrant API **URL:** \ **Category:** Cloud Recordings\ **Created:** [August 6, 2024, 6:21am UTC](https://devforum.zoom.us/t/zoom-add-recording-registrant-api/115079 "2024-08-06T06:21:32Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![zoom.license1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zoom.license1/32/62138_2.png) [@zoom.license1](https://devforum.zoom.us/u/zoom.license1)\ **Post date:** [August 6, 2024, 6:21am UTC](https://devforum.zoom.us/t/zoom-add-recording-registrant-api/115079/1 "2024-08-06T06:21:32Z")
**API Endpoint(s)** ## Create a recording registrant POST /meetings/{meetingId}/recordings/registrants **Description** I am using Create a recording registrant.I noticed that the share URL provided in the response is accessible to other accounts. Even if I log in with a different account, I can still access the recording using this URL. This behavior is problematic as the registrant should be restricted to a single account. **Error?** **Request JSON:** ```auto { "email": "example@gmail.com", "first_name": "ABC", "last_name": "A", "status": "approved" } ``` **Response:** ```auto { "registrant_id": "w8GQ7pB5SlB0m8rhg", "id": 99261738162, "topic": "Zoom Meeting", "share_url": "https://zoom.us/rec/share/rQrC8iy0tNcWQfkd_rA9S7_SorjVjkhnwbNaeYacPEVRPFupJ6U9fLgIgRdH_L5c.fKz6cQ40k5qMOw4A?tk=mCVEF-4_m-uGXz6geBW4Q8gWxreJfX0HKzpYw8sjrk0.AG.6ofU32N7MGvnapxMZvvK89sO7MRwqS5iUuFOa0OEevd-4TjTgIfl2JAD7b0rWcL1paFV4VGs7rXld7R9WGGaDdmZZ65t59ZtvWlBg5McuQU6WbbaLwyvkM0FVIuzvjyVHdIduUSiPvZPd_afxpObFgP79XteWc0b3j06.__dXuA1t1XJFXohdex4XuQ.S3EeVkuvWB-O32Cs" } ``` **Meeting Creation JSON:** ```auto { "duration": 45, "start_time": "2024-08-02T19:30:00", "timezone": "Asia/Kolkata", "auto_recording": "cloud", "join_before_host": true, "settings": { "approval_type": 0 }, "type": 2, "meeting_authentication": true } ``` The API response status code is 200, but it is not working as expected. Please guide me on how to restrict access to the recording URL to a single account. Thankyou ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [August 7, 2024, 3:46pm UTC](https://devforum.zoom.us/t/zoom-add-recording-registrant-api/115079/2 "2024-08-07T15:46:14Z")
Hi @zoom.license1 Thanks for reaching out to us Allow me to do some testing on my end and will get back to you with an update Cheers, Elisa ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [August 12, 2024, 4:00pm UTC](https://devforum.zoom.us/t/zoom-add-recording-registrant-api/115079/3 "2024-08-12T16:00:34Z")
Hi @zoom.license1 Thanks for your patience here, I am trying to replicate this behavior but have been unable to. Can you confirm that you are creating the meeting via API using this request body ```auto { "duration": 45, "start_time": "2024-08-02T19:30:00", "timezone": "Asia/Kolkata", "auto_recording": "cloud", "join_before_host": true, "settings": { "approval_type": 0 }, "type": 2, "meeting_authentication": true } ``` And are you starting the meeting and recording it? and once it is a past meeting, you are making a POST request to create a registrant. ---
**Author:** ![zoom.license1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zoom.license1/32/62138_2.png) [@zoom.license1](https://devforum.zoom.us/u/zoom.license1)\ **Post date:** [August 13, 2024, 11:30am UTC](https://devforum.zoom.us/t/zoom-add-recording-registrant-api/115079/4 "2024-08-13T11:30:39Z")
Hi @elisa.zoom , Yes,I am creating the meeting throught API using same Request body and starting the meeting recording it and once its in past meeting and even the recording got completely saved in account I am creating registrant for it. **Meeting creation request body:** ```auto { "agenda": "Title", "default_password": false, "duration": 45, "start_time": "2024-08-13T16:30:00", "password": 123456, "timezone": "Asia/Kolkata", "auto_recording": "cloud", "join_before_host": true, "jbh_time": 10, "settings": { "approval_type": 0 }, "type": 2 } ``` **Add recording registrant request body** ```auto { "email": "abc@gmail.com", "first_name": "abc", "last_name": "d", "status":"approved" } ``` Thankyou ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [August 13, 2024, 2:55pm UTC](https://devforum.zoom.us/t/zoom-add-recording-registrant-api/115079/5 "2024-08-13T14:55:10Z")
@zoom.license1 Are you getting a response back when creating the recording registration? or are you just getting a 200 ok with no response body? ---
**Author:** ![zoom.license1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/zoom.license1/32/62138_2.png) [@zoom.license1](https://devforum.zoom.us/u/zoom.license1)\ **Post date:** [August 14, 2024, 3:59pm UTC](https://devforum.zoom.us/t/zoom-add-recording-registrant-api/115079/6 "2024-08-14T15:59:05Z")
Hi @elisa.zoom, Yes able to get the response like below but I noticed that the share URL provided in the response is accessible to other accounts. Even if I log in with a different account, I can still access the recording using this URL. This behavior is problematic as the registrant should be restricted to a single account. ```auto { "registrant_id": "w8GQ7pW9rBlB0m8rhg", "id": 1234567867, "topic": "Zoom Meeting", "share_url": "https://zoom.us/rec/share/rQrC8iy0tNcWQfkd_rA9S7_SorjVjkhnwbNaeYacPEVRPFupJ6U9fLgIgRdH_L5c.fKz6cQ40k5qMOw4A?tk=mCVEF-4_m-uGXz6geBW4Q8gWxreJfX0HKzpYw8sjrk0.AG.6ofU32N7MGvnapxMZvvK89sO7MRwqS5iUuFOa0OEevd-4TjTgIfl2JAD7b0rWcL1paFV4VGs7rXld7R9WGGaDdmZZ65t59ZtvWlBg5McuQU6WbbaLwyvkM0FVIuzvjyVHdIduUSiPvZPd_afxpObFgP79XteWc0b3j06.__dXuA1t1XJFXohdex4XuQ.S3EeVkuvWB-O32Cs" } ``` Thankyou ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [August 15, 2024, 6:22pm UTC](https://devforum.zoom.us/t/zoom-add-recording-registrant-api/115079/7 "2024-08-15T18:22:47Z")
@zoom.license1 Thank you I will send you a DM to get more information about this, please follow up there ---
**Author:** ![elz.zhu](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elz.zhu/32/66035_2.png) [@elz.zhu](https://devforum.zoom.us/u/elz.zhu)\ **Post date:** [January 1, 2025, 9:55pm UTC](https://devforum.zoom.us/t/zoom-add-recording-registrant-api/115079/8 "2025-01-01T21:55:30Z")
@elisa.zoom Are you able to share any updates about this issue? I’m also having this issue. The share\_url for a registrant can be shared with anyone to gain access to the recording without registering. They could just forward the registration approval email to others and the url in the email will work for anyone that tries. ---
**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\ **Post date:** [January 7, 2025, 5:12pm UTC](https://devforum.zoom.us/t/zoom-add-recording-registrant-api/115079/9 "2025-01-07T17:12:59Z")
Hi @elz.zhu Thanks for reaching out. When sharing the share\_url for a registrant with someone else, this other person should not be able to watch the recording, they should be getting a “You cannot view this recording. No permission” prompt I just tested this on my end ![Screenshot 2025-01-07 at 12.12.41 PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/e/6eeff82bd15d1394984eb500b74f4328174316ad.png)