# Meeting Participant User ID value

**URL:** <https://devforum.zoom.us/t/meeting-participant-user-id-value/7886>\
**Category:** API and Webhooks\
**Created:** [February 5, 2020, 12:47am UTC](https://devforum.zoom.us/t/meeting-participant-user-id-value/7886 "2020-02-05T00:47:19Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![alastair.chin](https://avatars.discourse-cdn.com/v4/letter/a/f04885/32.png) [@alastair.chin](https://devforum.zoom.us/u/alastair.chin)\
**Post date:** [February 5, 2020, 12:47am UTC](https://devforum.zoom.us/t/meeting-participant-user-id-value/7886/1 "2020-02-05T00:47:19Z")

</div>

**Description**  
I am using [Get Meeting Participants Reports](https://marketplace.zoom.us/docs/api-reference/zoom-api/reports/reportmeetingparticipants) to get participant data from Zoom meetings via their meetinguuid.  
I was looking for further documentation on **user id** which I have assumed would fit the formatting of int64 or bigint (or even a varchar of length eight).

What I know from the given documentation under the participants array is it is a locally unique identity attribute and (I assume) could return null or different results if the user was a ‘guest’ (not a Zoom user under the associated account)

**Error**  
For one meeting (MeetingUUID = ‘KLp6/dd/SFaDAHW5j4a4vQ==’) the result contains three participants with a datetime added to the end of the userid (see screenshot).  
I was wondering if there was further information or a case to this as I have not encountered this with any other meetings

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

**Which Endpoint/s?**  
[https://api.zoom.us/v2/report/meetings/KLp6%2Fdd%2FSFaDAHW5j4a4vQ%3D%3D/participants?page\_size=300](https://api.zoom.us/v2/report/meetings/KLp6%252Fdd%252FSFaDAHW5j4a4vQ%253D%253D/participants?page_size=300)  
(I double encoded the meeting UUID)

**Screenshots (If applicable)**  
Result:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/2X/d/df2e1108247c2dde37c47783da4a863d2f1c36db.png)

---

<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:** [February 5, 2020, 5:23pm UTC](https://devforum.zoom.us/t/meeting-participant-user-id-value/7886/2 "2020-02-05T17:23:56Z")

</div>

Hey @alastair.chin, thanks for the detailed post!

Although rare, I have seen this issue before:

> [@Invalid characters in user\_name when receiving event notifications](https://devforum.zoom.us/t/invalid-characters-in-user-name-when-receiving-event-notifications/6123):
>
> Sometimes we see a large number of invalid characters in the user\_name field in the event notifications we receive from Zoom. This happens occasionally and is not easily reproducible. See a sample event notification below ( host\_id and account\_id intentionally Xed out): zoom event request: {“event”:“meeting.sharing\_started”,“payload”:{“object”:{“uuid”:“PQJnznlcTHWMByal4bv5PA==”,“participant”:{“id”:"",“user\_id”:“16778240”,“user\_name”:“Xiw\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u00…

> [@Weird user\_name is webhook](https://devforum.zoom.us/t/weird-user-name-is-webhook/7418):
>
> In the meeting.sharing\_\* webhooks, we noticed a rather unsual value for the user\_name. Is this expected? I have plenty of examples and just seems to be these webhooks. "participant": { "id": "", "sharing\_details": { "content": "desktop", "date\_time": "2020-01-08T16:19:44Z", "file\_link": "", "link\_source": "", "source": "" } , "user\_id": "16778240", "user\_name": "063,1,0|2020-01-08 16:08:04:720,3,0|2020-01-08 16:01:45:928,1,0|2020-01-08 16:01:45:928,1,0|2020-01-08 16:01:23:349,3,0|2020-…

We will look into this and get back to you with an update. (ZOOM-112804)

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![rex](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rex/32/684_2.png) [@rex](https://devforum.zoom.us/u/rex)\
**Post date:** [April 24, 2020, 5:56pm UTC](https://devforum.zoom.us/t/meeting-participant-user-id-value/7886/3 "2020-04-24T17:56:27Z")

</div>

@tommy Any update on ZOOM-112804? I am getting the same invalid user\_id that was reported in Feb in April.

“user\_id”: “02020-04-02 17:02:02:040”

When I call v2/report/meetings/:meetinguuid/participants

---

<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 28, 2020, 6:54pm UTC](https://devforum.zoom.us/t/meeting-participant-user-id-value/7886/4 "2020-04-28T18:54:32Z")

</div>

Hey @rex,

Thanks for sharing the details, we will investigate and keep you updated.

May I ask the meetingUUID?

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![rex](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rex/32/684_2.png) [@rex](https://devforum.zoom.us/u/rex)\
**Post date:** [April 28, 2020, 7:14pm UTC](https://devforum.zoom.us/t/meeting-participant-user-id-value/7886/5 "2020-04-28T19:14:51Z")

</div>

@tommy thanks for following up. I am not sure it is safe to post the meetind uuid in public. I sent the details to Zoom support:

[https://support.zoom.us/hc/requests/4730168](https://support.zoom.us/hc/requests/4730168)

I hope you have access to that.

The response was:

> What you are seeing in the is by design in our system. Upon checking, we found that the meeting failed over. We add the date after the value of user\_id to mark (indicate) the meeting failed over.

But my question was:

> What do you mean when a meeting fails over? How does that occur?
> 
> Also it’s not documented. But also can the user id be separated from the time stamp? Like with a pipe character so we can still obtain the user id?

Also, what is the status of ZOOM-112804?

---

<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, 5:33pm UTC](https://devforum.zoom.us/t/meeting-participant-user-id-value/7886/6 "2020-05-04T17:33:49Z")

</div>

Hey @rex,

You can also private message me the meeting uuid on this forum.

> [@rex](#):
>
> What do you mean when a meeting fails over? How does that occur?

I am not sure how this occurs, seems like there is an edge case in our system. We are investigating.

> [@rex](#):
>
> Also it’s not documented. But also can the user id be separated from the time stamp? Like with a pipe character so we can still obtain the user id?

No, when this issue happens, the user ID is not present in the timestamp.

> [@rex](#):
>
> Also, what is the status of ZOOM-112804?

We are still investigating the issue.

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![rex](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rex/32/684_2.png) [@rex](https://devforum.zoom.us/u/rex)\
**Post date:** [May 4, 2020, 6:47pm UTC](https://devforum.zoom.us/t/meeting-participant-user-id-value/7886/7 "2020-05-04T18:47:11Z")

</div>

> [@tommy](#):
>
> No, when this issue happens, the user ID is not present in the timestamp.

But in our API results we do see the userid being there with the datetime appended. I will PM you.

---

<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 7, 2020, 6:19pm UTC](https://devforum.zoom.us/t/meeting-participant-user-id-value/7886/8 "2020-05-07T18:19:15Z")

</div>

Thanks @rex,

I will reply to your private message!

-Tommy

---

<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, 9:06pm UTC](https://devforum.zoom.us/t/meeting-participant-user-id-value/7886/9 "2020-08-21T21:06:38Z")

</div>

Closed on August 21, 2020, 9:06pm UTC



---

<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:** [September 8, 2020, 4:55pm UTC](https://devforum.zoom.us/t/meeting-participant-user-id-value/7886/10 "2020-09-08T16:55:36Z")

</div>

Hey @rex, @alastair.chin,

This will be fixed in our October release. 🙂

Thanks,  
Tommy
