# Passing values to Zoom when using OAuth

**URL:** <https://devforum.zoom.us/t/passing-values-to-zoom-when-using-oauth/62345>\
**Category:** API and Webhooks\
**Created:** [January 7, 2022, 9:12pm UTC](https://devforum.zoom.us/t/passing-values-to-zoom-when-using-oauth/62345 "2022-01-07T21:12:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cedricgidget](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@cedricgidget](https://devforum.zoom.us/u/cedricgidget)\
**Post date:** [January 7, 2022, 9:12pm UTC](https://devforum.zoom.us/t/passing-values-to-zoom-when-using-oauth/62345/1 "2022-01-07T21:12:41Z")

</div>

## Using this template helps us debug your issues more effectively 🙂

**Description**  
Hi, we are looking to store how long a given user from our application is in a Zoom meeting hosted by us. ([Authenticating with Zoom using own application](https://devforum.zoom.us/t/authenticating-with-zoom-using-own-application/59941)). We are looking at creating an OAuth app and sending user info/data to Zoom (their name and email), making a request for meeting participants, and then running a program to identify our users in the Zoom reports and store in our database how long they were in a Zoom meeting hosted by us.

Is it possible for us to send any additional information (for example, unique id for the user) to make it easier for us to identify them in the Zoom report? Their email might be sufficient to identify and match them in the report, but I want to check just in case.

Thanks!

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

**Which Endpoint/s?**  
[https://marketplace.zoom.us/docs/api-reference/zoom-api/reports/reportmeetingparticipants](https://marketplace.zoom.us/docs/api-reference/zoom-api/reports/reportmeetingparticipants)

[https://marketplace.zoom.us/docs/api-reference/zoom-api/dashboards/dashboardmeetingparticipants](https://marketplace.zoom.us/docs/api-reference/zoom-api/dashboards/dashboardmeetingparticipants)

**Additional context**  
Add any other context about the problem here.

---

<div class="post-metadata">

**Author:** ![donte.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/donte.zoom/32/24412_2.png) [@donte.zoom](https://devforum.zoom.us/u/donte.zoom)\
**Post date:** [January 13, 2022, 2:20am UTC](https://devforum.zoom.us/t/passing-values-to-zoom-when-using-oauth/62345/2 "2022-01-13T02:20:17Z")

</div>

Hi, @cedricgidget,

Thank you for posting in the Developer Forum. For your concern, please see this helpful Developer Forum Post and let me know if it helps:

> [@No way to identify a participant in the "meeting.participant\_joined" webhook](https://devforum.zoom.us/t/no-way-to-identify-a-participant-in-the-meeting-participant-joined-webhook/10973/2):
>
> Hey @s27_zoom, thanks for posting and using Zoom! Can you checkout my posts here and let me know if it helps: Thanks, Tommy

Best,  
Donte

---

<div class="post-metadata">

**Author:** ![cedricgidget](https://avatars.discourse-cdn.com/v4/letter/c/ac8455/32.png) [@cedricgidget](https://devforum.zoom.us/u/cedricgidget)\
**Post date:** [January 13, 2022, 4:03pm UTC](https://devforum.zoom.us/t/passing-values-to-zoom-when-using-oauth/62345/3 "2022-01-13T16:03:48Z")

</div>

Hi Donte,

Thank you, these resources are great! It seems like there may be several ways to do this.

The Zoom `user_id` seems useful, but I am a little confused about how to go about using in this use case.

In [Mapping join and leave of participants webhook events with users on our application - #6 by tommy](https://devforum.zoom.us/t/mapping-join-and-leave-of-participants-webhook-events-with-users-on-our-application/8116/6) , it seems like it is recommended to use the meeting registration:

> You could use [meeting registration](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingregistrantcreate) to create a unique join URL for all of your users. Then you can [map your users easier](https://marketplace.zoom.us/docs/api-reference/zoom-api/dashboards/dashboardmeetingparticipants) via the `registrant_id` and `user_id` .

However, our users would potentially be joining several Zoom meetings hosted by us and this approach seems like it is meant for registering a user for a specific meeting. It also seems like the `user_id` is temporary and just for the meeting. Using email might be the way to go, at least for reports for meetings, as it seems this would allow us to map which of our users attended a given meeting, but it seems like [this](https://devforum.zoom.us/t/unable-to-map-meeting-registrant-id-with-live-participant-id/6862/3) post you recommended that it is mentioned that it is possible to get the list of users who are in the meeting, which would be really great. However, it seems like this might require use of the registrant\_id and the registration endpoint, which I cannot tell if it would work for our use case.

Do you have any advice for going about this? Thanks!

---

<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:** [January 22, 2022, 2:13am UTC](https://devforum.zoom.us/t/passing-values-to-zoom-when-using-oauth/62345/4 "2022-01-22T02:13:21Z")

</div>

@cedricgidget If you wanted a list of users that were in the meeting, you can try using the [Get Past Meeting Participants API](https://marketplace.zoom.us/docs/api-reference/zoom-api//pastmeetingparticipants) which should provide you with the user’s email. I think in most cases that will be the best way to track users that have installed your app across meetings.

---

<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:** [February 21, 2022, 12:13pm UTC](https://devforum.zoom.us/t/passing-values-to-zoom-when-using-oauth/62345/5 "2022-02-21T12:13:50Z")

</div>

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