# Join URL for meeting registrant

**URL:** <https://devforum.zoom.us/t/join-url-for-meeting-registrant/390>\
**Category:** API and Webhooks\
**Created:** [October 2, 2017, 1:09pm UTC](https://devforum.zoom.us/t/join-url-for-meeting-registrant/390 "2017-10-02T13:09:20Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aleksandr\_Fofanov](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@Aleksandr\_Fofanov](https://devforum.zoom.us/u/Aleksandr_Fofanov)\
**Post date:** [October 2, 2017, 1:09pm UTC](https://devforum.zoom.us/t/join-url-for-meeting-registrant/390/1 "2017-10-02T13:09:20Z")

</div>

Hey,

When we [register a user for meeting](https://zoom.github.io/api/#meeting-registration), we pass his email, first name and last name to endpoint and in case of success we get a unique **join\_url** for this registrant. No problems here. However, when registrant opens this url, Zoom application launches and for some reason it doesn’t pick up passed info (email and name) from URL (I mean the token in URL). By picking up the info I mean automatic authentication and name setup in Zoom app. This perfectly works with [start\_url of the meeting](https://zoom.github.io/api/#get-meeting-info)&nbsp;- Zoom app automatically authenticate the host of the meeting and sets their&nbsp;name in the App. I expected the same behavior for **join\_url** for meeting registrant. Well, at least their name should be&nbsp;set in the app and it should&nbsp;not ask registrant to enter their&nbsp;name on app launch (in case of a fresh Zoom app installation). Otherwise it is not clear why registration for a meeting is needed and what is its purpose.&nbsp;Is this a bug or expected behavior?

Thanks.

---

<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:** [October 3, 2017, 5:33pm UTC](https://devforum.zoom.us/t/join-url-for-meeting-registrant/390/2 "2017-10-03T17:33:39Z")

</div>

Hi Alexksandr,

I just tested this and got the expected behavior. Are you logged into the zoom client when you click the join url with token? need to be logged out, as not to use your user.

---

<div class="post-metadata">

**Author:** ![Aleksandr\_Fofanov](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@Aleksandr\_Fofanov](https://devforum.zoom.us/u/Aleksandr_Fofanov)\
**Post date:** [October 4, 2017, 4:02am UTC](https://devforum.zoom.us/t/join-url-for-meeting-registrant/390/3 "2017-10-04T04:02:11Z")

</div>

Hi Joshua, thanks for your answer.

I’ve created a [simple python script](https://pastebin.com/ncP2scBF) to simplify testing. It outputs meeting start url for host and join url for registrant.&nbsp;You will need python 3 and requests lib to run it, and also&nbsp;set your api key and credentials in the script.

Here is also a [demonstration of the behavior I described](http://recordit.co/QmtyrkuW0x). As you can see I’m not logged in on [zoom.us](http://zoom.us) and in the app and launch the app from incognito window in chrome. I also tested in on Mac and Linux and different browsers, so it is not OS or browser specific.

---

<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:** [October 9, 2017, 4:06pm UTC](https://devforum.zoom.us/t/join-url-for-meeting-registrant/390/4 "2017-10-09T16:06:56Z")

</div>

Alex,

&nbsp;

Not sure I follow, in your video you visit the join url (with token) and the meeting starts, no auth required. What is the behavior you’re expecting?

---

<div class="post-metadata">

**Author:** ![Aleksandr\_Fofanov](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@Aleksandr\_Fofanov](https://devforum.zoom.us/u/Aleksandr_Fofanov)\
**Post date:** [October 10, 2017, 3:59am UTC](https://devforum.zoom.us/t/join-url-for-meeting-registrant/390/5 "2017-10-10T03:59:08Z")

</div>

Joshua,

I expect the same behavior as Webinars have.

1. User registered for webinar with email, first\_name, last\_name
2. Zoom API returns join url for this registrant
3. When this join url opened by registrant, Zoom app automatically sets their&nbsp;name in the app to that&nbsp;used on registration for webinar.

With Zoom Meetings&nbsp;the behavior is&nbsp;different:

1. User registered for meeting&nbsp;with email, first\_name, last\_name
2. Zoom API returns join url for this&nbsp;registrant
3. When this&nbsp;join url opened by registrant, Zoom App doesn’t set&nbsp;their name in the app (in case of fresh Zoom app installation it will also ask user to enter&nbsp;their name).

The video I attached above demonstrates this: Zoom uses my name (aleksandr.fofanov) in the app, but should use ‘Test User’ instead (as written in python script above).

---

<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:** [October 10, 2017, 6:28pm UTC](https://devforum.zoom.us/t/join-url-for-meeting-registrant/390/6 "2017-10-10T18:28:35Z")

</div>

Alex,

&nbsp;

I don’t experience the same behavior. I&nbsp;would double check what you are passing to the register endpoint. try dumping full request/response to debug

&nbsp;

 ![](https://support.zoom.us/hc/user_images/iinsYM5CSfyTSp-uT0CHEw.png)

---

<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:** [October 11, 2017, 7:22pm UTC](https://devforum.zoom.us/t/join-url-for-meeting-registrant/390/7 "2017-10-11T19:22:36Z")

</div>

I’m unable to reproduce

Create

 ![](https://support.zoom.us/hc/user_images/zh-dyw9NjtlB8SQZsuXVpw.png)

Register:

 ![](https://support.zoom.us/hc/user_images/Yr-DOHhZRsVL4_qLQtyv_g.png)

&nbsp;

Join:

 ![](https://support.zoom.us/hc/user_images/U9gKUVycMuRXoZTITsEnZA.png)

---

<div class="post-metadata">

**Author:** ![Aleksandr\_Fofanov](https://avatars.discourse-cdn.com/v4/letter/a/7c8e57/32.png) [@Aleksandr\_Fofanov](https://devforum.zoom.us/u/Aleksandr_Fofanov)\
**Post date:** [October 12, 2017, 3:08am UTC](https://devforum.zoom.us/t/join-url-for-meeting-registrant/390/8 "2017-10-12T03:08:45Z")

</div>

Joshua,

Create:

 ![](https://support.zoom.us/hc/user_images/_pWx0uZIh99TRtlb06tExA.png)Register:

 ![](https://support.zoom.us/hc/user_images/zAcAU5BMDSRrSu7gEdKOTA.png)And it still doesn’t work for me.

I noticed the difference in the urls that zoom generates for you and for me. Your urls have [success.zoom.us](http://success.zoom.us) as the domain and my is just [zoom.us](http://zoom.us), not sure if it makes any difference.

Joshua, I sent you my credentials and host\_id to your email. Could you please try with them?

---

<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:** [October 12, 2017, 6:03pm UTC](https://devforum.zoom.us/t/join-url-for-meeting-registrant/390/9 "2017-10-12T18:03:08Z")

</div>

The success subdomain is just our vanity url, someone in marketing picked success because [zoom.zoom.us](http://zoom.zoom.us) looks weird. Ex. other companies have vanity urls like [uber.zoom.us](http://uber.zoom.us) or [tupperware.zoom.us](http://tupperware.zoom.us) - must none company accounts are just [zoom.us](http://zoom.us).

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 5:19pm UTC](https://devforum.zoom.us/t/join-url-for-meeting-registrant/390/10 "2020-08-21T17:19:19Z")

</div>

Closed on August 21, 2020, 5:19pm UTC


