# Registration\_id missing on users join via link and authentication problem **URL:** \ **Category:** API and Webhooks\ **Created:** [April 20, 2021, 10:06am UTC](https://devforum.zoom.us/t/registration-id-missing-on-users-join-via-link-and-authentication-problem/48384 "2021-04-20T10:06:14Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![BCELT](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bcelt/32/15473_2.png) [@BCELT](https://devforum.zoom.us/u/BCELT)\ **Post date:** [April 20, 2021, 10:06am UTC](https://devforum.zoom.us/t/registration-id-missing-on-users-join-via-link-and-authentication-problem/48384/1 "2021-04-20T10:06:15Z")
This is my workflow. A new meeting is created via API with create\_meeting. I experimented both with registration\_type: 1 and registration\_type: 2 . In theory, all participants to the meeting are previously registered and receive a join link via email. They should be able to join the meeting by clicking on the link they receive via email. I don’t need a “waiting room”, I don’t need a “meeting password”, I don’t need them to be logged in zoom and I don’t understand why I’m required to select one of these options while my users have a valid token. But this is not the point. In many cases, I have many users without a valid “registrant\_id” field in the report\_meeting\_participants obtained after the meeting with the API. E.g. meeting 91583889681 by user has all its users without a registrant\_id. I don’t know why, I don’t have access to any kind of log and feedback. ---
**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\ **Post date:** [April 21, 2021, 9:20pm UTC](https://devforum.zoom.us/t/registration-id-missing-on-users-join-via-link-and-authentication-problem/48384/2 "2021-04-21T21:20:12Z")
Hi @BCELT, Thanks for reaching out about this. Can you ensure that you’re including the following query param in your request URL? `?include_fields=registrant_id` If this parameter isn’t included, this field will not be returned. Let me know—thanks! Will ---
**Author:** ![BCELT](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bcelt/32/15473_2.png) [@BCELT](https://devforum.zoom.us/u/BCELT)\ **Post date:** [April 22, 2021, 11:23am UTC](https://devforum.zoom.us/t/registration-id-missing-on-users-join-via-link-and-authentication-problem/48384/3 "2021-04-22T11:23:25Z")
Yes I’m including that parameter. The API includes “registrant\_id” _often_. It doesn’t _sometimes_, meaning for some entries. Can you look in your logs why registrant\_id is not present in the meeting I’ve provided you the id? ---
**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\ **Post date:** [April 23, 2021, 3:37pm UTC](https://devforum.zoom.us/t/registration-id-missing-on-users-join-via-link-and-authentication-problem/48384/4 "2021-04-23T15:37:04Z")
Hi @BCELT, Thanks for confirming. In checking the Meeting instances from 2021-04-06, I can see that many of these participants don’t appear to have been logged in to the Zoom client when they joined the meeting. Can you confirm that the users were logged in **and** joined using their registration URLs? Do you know how these participants are joining—is it possible they’re not using their unique registrant URLs, but perhaps a generic join url? Thanks, Will ---
**Author:** ![BCELT](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bcelt/32/15473_2.png) [@BCELT](https://devforum.zoom.us/u/BCELT)\ **Post date:** [April 28, 2021, 5:28am UTC](https://devforum.zoom.us/t/registration-id-missing-on-users-join-via-link-and-authentication-problem/48384/5 "2021-04-28T05:28:26Z")
I don’t know if they were logged in to zoom. How can I control that? Should they be? Why, if they have a valid link with unique registrant id? I would really like to avoid that if at all possibile. What I would like to happen is the following. - The user receives an email with the link. - They click on the link and they join. They should not need a zoom account and they shouldn’t be able to join otherwise. In theory I don’t distribute any “generic join url”. In theory, it shouldn’t even exists. Can’t you check what url - referral - was used to join the meeting? I’ve a working theory that the join url might be corrupted by some email clients, but I don’t really have any way to check it. ---
**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:** [April 28, 2021, 9:39pm UTC](https://devforum.zoom.us/t/registration-id-missing-on-users-join-via-link-and-authentication-problem/48384/6 "2021-04-28T21:39:48Z")
Hey @BCELT, When you’re calling the [Get Meeting Participants Report API](https://marketplace.zoom.us/docs/api-reference/zoom-api/reports/reportmeetingparticipants), are you using the Meeting ID or are you using the Meeting UUID? If you’re using the Meeting ID, I would try using the Meeting UUID just to ensure that you’re querying the correct instance of the meeting. If that doesn’t help, please send an email to [developersupport@zoom.us](mailto:developersupport@zoom.us) with a link to this thread. In that email, please include the request that you’re making to the [Get Meeting Participants Report API](https://marketplace.zoom.us/docs/api-reference/zoom-api/reports/reportmeetingparticipants) as well as the response that you’re seeing. I’ll use that information to find out why some users don’t have a registrant\_id. Thanks, Max ---
**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:** [May 29, 2021, 7:40am UTC](https://devforum.zoom.us/t/registration-id-missing-on-users-join-via-link-and-authentication-problem/48384/7 "2021-05-29T07:40:31Z")
Closed on May 29, 2021, 7:40am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.