# Requiring Registration Not Working

**URL:** <https://devforum.zoom.us/t/requiring-registration-not-working/623>\
**Category:** API and Webhooks\
**Created:** [June 19, 2017, 8:24pm UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623 "2017-06-19T20:24:23Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![Raymond\_Lee](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/raymond_lee/32/11505_2.png) [@Raymond\_Lee](https://devforum.zoom.us/u/Raymond_Lee)\
**Post date:** [June 19, 2017, 8:24pm UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/1 "2017-06-19T20:24:23Z")

</div>

When I create a meeting and set option\_registration to ‘Y’, it still doesn’t require nor allow registration. So in that case, when I try to submit a registration for a user, it gives me an error of: “This meeting has not registration required.”&nbsp;

Registration for Webinars is working fine, but not Meetings.&nbsp;

I’m assuming I’m not setting some parameter correctly but in reading through I’m unsure what that could be.&nbsp;

Requests/Responses:&nbsp;

Create Meeting

REQUEST:&nbsp;

api\_key: XXXXX  
api\_secret: \*\*\*\*\*\*  
approval\_type: 0  
data\_type: XML  
duration: 60  
host\_id: b8vOIyDxSvy9zPD6BuJKmA  
option\_registration: Y  
registration\_type: 1  
start\_time: 2017-07-01T12:00:00Z  
timezone: America/New\_York  
topic: jul 1  
type: 2

RESPONSE:&nbsp;

\<?xml version=“1.0” encoding=“UTF-8”?\>  
\<result\>  
\<uuid\>BinHdl6KQaCOGQm+8ekFbw==\</uuid\>  
\<id\>459251713\</id\>  
\<host\_id\>b8vOIyDxSvy9zPD6BuJKmA\</host\_id\>  
\<topic\>jul 1\</topic\>  
\<password\>\</password\>  
\<h323\_password\>\</h323\_password\>  
\<status\>0\</status\>  
\<option\_jbh\>false\</option\_jbh\>  
\<option\_start\_type\>video\</option\_start\_type\>  
\<option\_host\_video\>true\</option\_host\_video\>  
\<option\_participants\_video\>true\</option\_participants\_video\>  
\<option\_cn\_meeting\>false\</option\_cn\_meeting\>  
\<option\_enforce\_login\>false\</option\_enforce\_login\>  
\<option\_enforce\_login\_domains\>\</option\_enforce\_login\_domains\>  
\<option\_in\_meeting\>false\</option\_in\_meeting\>  
\<option\_audio\>both\</option\_audio\>  
\<option\_alternative\_hosts\>\</option\_alternative\_hosts\>  
\<option\_use\_pmi\>false\</option\_use\_pmi\>  
\<type\>2\</type\>  
\<start\_time\>2017-07-01T12:00:00Z\</start\_time\>  
\<duration\>60\</duration\>  
\<timezone\>America/New\_York\</timezone\>  
\<start\_url\>[https://zoom.us/s/459251713?zpk=abagzhUPO6DU6en3fY65\_mUIm\_iYkoKVwYJuBTLApjU.BwcAAAFcwfP8lQAAH](https://zoom.us/s/459251713?zpk=abagzhUPO6DU6en3fY65_mUIm_iYkoKVwYJuBTLApjU.BwcAAAFcwfP8lQAAH) …

Register User:&nbsp;

REQUEST

api\_key:&nbsp;XXXXX  
api\_secret: \*\*\*\*\*\*  
data\_type: XML  
email: [myemail@gmail.com](mailto:myemail@gmail.com)  
first\_name: Sue  
last\_name: Hawkins  
id: 459251713

RESPONSE:&nbsp;

\<?xml version=“1.0” encoding=“UTF-8”?\>  
\<result\>  
\<error\>  
\<code\>404\</code\>  
\<message\>This meeting has not registration required.\</message\>  
\</error\>  
\</result\>

---

<div class="post-metadata">

**Author:** ![Joshua\_Woodward1](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/joshua_woodward1/32/1480_2.png) [@Joshua\_Woodward1](https://devforum.zoom.us/u/Joshua_Woodward1)\
**Post date:** [June 19, 2017, 8:43pm UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/2 "2017-06-19T20:43:58Z")

</div>

option\_registration is a&nbsp;boolean, pass “true” and see if that works.

---

<div class="post-metadata">

**Author:** ![Raymond\_Lee](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/raymond_lee/32/11505_2.png) [@Raymond\_Lee](https://devforum.zoom.us/u/Raymond_Lee)\
**Post date:** [June 19, 2017, 8:53pm UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/3 "2017-06-19T20:53:51Z")

</div>

Ah, that did it. Thanks.&nbsp;

---

<div class="post-metadata">

**Author:** ![gamebooker](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gamebooker/32/16841_2.png) [@gamebooker](https://devforum.zoom.us/u/gamebooker)\
**Post date:** [April 10, 2020, 1:44pm UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/4 "2020-04-10T13:44:35Z")

</div>

Hey Guys,

V2 Api is how this feature works. The option\_registration parameter is missing.

---

<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:** [April 11, 2020, 1:45am UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/5 "2020-04-11T01:45:58Z")

</div>

Hey @gamebooker,

Yes, for requiring registration, pass in `0` or `1` for the `approval_type` in the `settings` object when [creating a meeting.](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate)

 ![Screen Shot 2020-04-10 at 7.45.31 PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/4/4babcb4129293ceb020ee1f7082803660d2e4882.png)

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![dtzoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dtzoom/32/5948_2.png) [@dtzoom](https://devforum.zoom.us/u/dtzoom)\
**Post date:** [April 13, 2020, 11:54am UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/6 "2020-04-13T11:54:50Z")

</div>

@tommy My overall goal is simple: create a persistent meeting (basically runs forever) where the only people that can join are registrants that have been manually approved (via the API) So far, this seems impossible. Do you know of a way to achieve the goal I’ve stated?

I have a pro account and am attempting to emulate the desired behavior by creating a type 8 meeting that recurs daily with duration 24 hours and with approval\_type: 1 because type 3 meeting does not seem to support approval\_type 1 (it simply comes back as approval\_type:2. (I’ve tried setting registration\_type:2 but the value of registration\_type seems to be ignored when creating a meeting via the REST API (registration\_type does not even appear in the response).

---

<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:** [April 14, 2020, 7:22am UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/7 "2020-04-14T07:22:48Z")

</div>

Hey @dtzoom,

Can you share your request body and url so I can debug?

Have you tried using an [Instant Meeting](https://support.zoom.us/hc/en-us/articles/201362533-Meet-Now-vs-Scheduled-Meetings) with a password or [whitelisted domains](https://support.zoom.us/hc/en-us/articles/360037117472-Authentication-Profiles-for-Meetings-and-Webinars) instead of scheduling a meeting forever?

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![okzoomer](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/okzoomer/32/16226_2.png) [@okzoomer](https://devforum.zoom.us/u/okzoomer)\
**Post date:** [April 29, 2020, 5:51pm UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/8 "2020-04-29T17:51:10Z")

</div>

@tommy I am also running into the same issue:

I am trying to use the API to add registrants to a meeting that required registrants, but while testing I noticed that once a registrant has received the Zoom meeting link they could share that link with people who have not registered and those non-registered users could still join the meeting. Is this supposed to be the case? I thought that when a meeting was “registration required” it forced a user to join the meeting with the email that they registered with to prevent people from sharing private meeting links.

---

<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:** [May 4, 2020, 10:58pm UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/9 "2020-05-04T22:58:22Z")

</div>

Hey @okzoomer,

Yes, the unique url sent to registrants should be treated as a password and not be shared.

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![OregonDean](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/oregondean/32/10443_2.png) [@OregonDean](https://devforum.zoom.us/u/OregonDean)\
**Post date:** [June 12, 2020, 5:48pm UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/10 "2020-06-12T17:48:27Z")

</div>

While you cannot prevent someone from sharing the unique URL, there is a meeting option that allows only one device/connection from each unique URL. You can find the option (only in meetings requiring registration) under Registration Options --\> “Allow attendees to join from multiple devices”.

FWIW, I do not see the multiple device option as part of the Create Meeting options, nor is it returned as part of the Get Meeting API response.

Note … If allow multiple devices is not set (i.e. 1 device per unique URL), if the authorized user joins first they will grab the single slot, however, if they arrive after someone else has used the uniqueURL they will be prevent from joining. We find it important to be clear in follow-up and confirmation emails that the URL is unique and should not be shared.

---

<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 17, 2020, 8:37pm UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/11 "2020-06-17T20:37:32Z")

</div>

Hey @OregonDean,

Thanks for your comment! Others will find this helpful! 🙂

-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:** [July 16, 2020, 6:00pm UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/12 "2020-07-16T18:00:36Z")

</div>

I followed what you mentioned. Still I am able to join with the same URL using my mobile app but with different email ID.

I tried to set registrant status as “deny” after the user joins the meeting thinking that the URL will be invalid and no user will be able to join again with the same URL. But even that dint work.

@tommy @OregonDean would be a great help if you could suggest me any solution on this.

---

<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:** [July 21, 2020, 4:51pm UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/13 "2020-07-21T16:51:36Z")

</div>

Hey @naveen,

What do you mean different email ID?

Can you please provide steps to reproduce the issue?

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:** [July 22, 2020, 4:36am UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/14 "2020-07-22T04:36:58Z")

</div>

Hi @tommy

By different email ID I mean different users. Example:- I register as user01 and got the unique Join URL and joined the meeting. I deny user01’s registration. Now I pass this join URL to user02. Still, the user02 is able to join the meeting.

My second concern:- “Allow attendees to join from multiple devices” field is not available in Create meeting API. It is only available in Create Webinar API.

---

<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:** [July 23, 2020, 9:35pm UTC](https://devforum.zoom.us/t/requiring-registration-not-working/623/15 "2020-07-23T21:35:13Z")

</div>

Hey @naveen,

> [@naveen](#):
>
> I register as user01 and got the unique Join URL and joined the meeting. I deny user01’s registration. Now I pass this join URL to user02. Still, the user02 is able to join the meeting.

So you are saying after approving user1’s registration, and then denying it, the unique join\_url still works?

We are working on making the “Allow attendees to join from multiple devices” field available for the Create Meeting API. Stay updated here: [https://marketplace.zoom.us/docs/changelog](https://marketplace.zoom.us/docs/changelog)

Thanks,  
Tommy