We are developing a in client Zoom App using React and need some guidance on the following.
While in a meeting in the Zoom client I can right click on my tile and select rename. In here I can even use emoji’s like these
I would like to change this display name programmatically when our application is opened during a meeting but I cannot see a way to do this.
We can update the user’s Name and Surname in their profile via the API but these emoji’s don’t show up at all.
Is there a way to set the user’s display name in the context of a meeting using the Zoom App Client SDK?
We don’t have a method to change the display name of a user with a Zoom App or with the API. If this is something you would like to see in the future I recommend posting to our #feature-requests category
Thank you for the reply.
Is there any way to change any information regarding participants, that the user with my app installed can see, via the Zoom App SDK?
The idea is to make information from my app available, via the in client zoom app, to meeting participants that are already connected in my application for that I need to identify the meeting participants to find their profiles in my application. It currently looks like I will have to rely on Webhooks to get that info, is there a way to see a list which API’s I can call with a Zoom Apps access token?
Apologies I should have clarified that the method you suggested only returns the Display Name for the participant not the email address. A participant could change their display name to anything and it is therefore not a trustworthy way of matching the participant name to users connected to my logged in user. I would therefore require their email address to allow me to identify their profiles in my system correctly.
In terms of the API’s. Some methods returned with an error saying that it cannot be called with a Zoom Apps token. Should I be able to call something like List Meeting Participants with my Zoom App token?
When using the Get Meeting Participants function, you can use the participant UUID to uniquely identify participants across the meeting.
Thanks for sharing this detail. Can you share a screenshot of the error that you’re seeing? I’ll check with our team to see if I can get a list of APIs that are permissible and see if we can update our documentation.
Apologies for taking this long to respond. My attention was needed elsewhere and I am only now getting back to it.
The UUID does not serve my purpose as it changes between meetings. As far as I can see the only way I can identify two users connected in my application is if both have my Zoom app installed allowing me to read their current live meeting id’s and then associating them in my API layer.
As for the cannot call endpoint with Zoom App token error here you go.
I played around with many approaches. This was in response to /meetings/{meetingid}/registrants API call.
Where can I see which API’s are callable by App Type and Subscription Plan? Or can you maybe put me in contact with someone that can give me guidance on which App Type and Subscription plan to use?
You bring up a good point that we don’t offer an easy method to track users between meetings which is intentional. However, I think we could do a better job of exposing the same information in the SDK that we use within the RESTful API. I’m working with our team to see if this is something that we can fix going forward.
Likewise, it looks like our documentation on our RESTful APIs is missing details on what works and does not work with a Zoom Apps token. As a rule of thumb, any user-level APIs should be available but it looks like the API you are using is user-level.
To be clear, were you looking to list registrants or create a new registrant? As long as your user owns the meeting and you have added the meeting:read or meeting:write scopes you should be able to use either one.
I was just listing registrants for an existing meeting to see if it would work. I expected it to just return an empty list of registrants but instead it told me I could call that API with a Zoom Apps token.
I was able to reproduce this issue on my end and reached out to our product team for more information on why this is happening. I’ll be sure to keep you posted.
