Thank you for your patience @h_yamada! It looks like we are still working to roll out the customer_key feature to all platforms so you may see a blank customer_key when using the Zoom Client right now.
However, when implemented, the customer_key should be set the same way as with other clients such as the Web SDK. That is, it is generated by the client and passed to our DB so that it can be consumed via API and reports.
I hope that helps! Let me know if you have any questions.
My apologies, I almost forgot, thank you for your patience.
I spoke with our team and learned that the customer key cannot be used with the Client. When a user is not logged in an joins a meeting, we don’t have a method to track that user throughout a meeting. This is by design to follow security and privacy policies.
Can you please help me with creating a sample first at your end and then reply to us about what should we use.
I hope you can understand the urgency and why we are constantly following up on this issue. Zoom API has failed to give us a way to track our participants. Please help us and ask your team to pick this issue soon because I am following up for more than a year now.
First, I’ll say that I absolutely hear you - this has been an issue for quite some time. I know this has been a blocker for your team and I’m excited to help get this working for you ASAP.
Further, I’ll have to apologise for offering in correct information earlier. After further discussion with our team, they corrected their last statement and indicated that the correct value to use is customerKey as you were using.
They indicated that they meeting will need to end before this information is available via API. A good way to check for testing is through the Dashboard. Otherwise, you can use an webhook event.
If that’s not helpful, please send an email to firstname.lastname@example.org with a link to this thread. In that email, please include the full endpoint URL that you’re using when calling the participant API.