# Customer\_key set by Android SDK is not reflected in API

**URL:** <https://devforum.zoom.us/t/customer-key-set-by-android-sdk-is-not-reflected-in-api/59218>\
**Category:** Android\
**Created:** [October 22, 2021, 12:12am UTC](https://devforum.zoom.us/t/customer-key-set-by-android-sdk-is-not-reflected-in-api/59218 "2021-10-22T00:12:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![june.glave](https://avatars.discourse-cdn.com/v4/letter/j/b782af/32.png) [@june.glave](https://devforum.zoom.us/u/june.glave)\
**Post date:** [October 22, 2021, 12:12am UTC](https://devforum.zoom.us/t/customer-key-set-by-android-sdk-is-not-reflected-in-api/59218/1 "2021-10-22T00:12:33Z")

</div>

**Description**  
I set the `customer_key` on my JoinMeetingOptions before joining the meeting, but in a later call to the Past Meeting Participants API ([https://api.zoom.us/v2/metrics/meetings/rLzrGqo+RiaO0pGLQvxNew==/participants?type=past](https://api.zoom.us/v2/metrics/meetings/rLzrGqo+RiaO0pGLQvxNew==/participants?type=past)), the participant record for the Android user had no `id` and their `customer_key` was blank, making it impossible to associate the user with ID we had set in the JoinMeetingOptions.

**Which Android Meeting SDK version?**  
5.7.1.1266

**To Reproduce(If applicable)**  
Steps to reproduce the behavior:

1. Schedule a Zoom meeting
2. Set the `customer_key` field on `JoinMeetingOptions`, then join the meeting with those options
3. End the meeting
4. Call the `metrics/meetings/{meetingUUID}/participants` API with the UUID of the meeting

Expected: The `customer_key` value set by the Android client appears in the `id` field for the participant’s record in the `metrics/meetings/{meetingUUID}/participants` response

Actual: The `customer_key` value set by the client does not appear in any field of the participant’s record.

**Screenshots**  
Screenshot of the API request with the missing `id` field:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/d/b/dba86a1566e6f67ff081b819627d0e2ffffaf830.jpeg)

**Smartphone (please complete the following information):**

- Device: Samsung Galaxy S9

**Additional context**  
The ability to associate Zoom meeting participants with IDs under our control is mission-critical. We will have to downgrade to a previous SDK version until a workaround is found or a version which fixes this issue is released.

---

<div class="post-metadata">

**Author:** ![jon.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jon.zoom/32/13495_2.png) [@jon.zoom](https://devforum.zoom.us/u/jon.zoom)\
**Post date:** [October 22, 2021, 5:12pm UTC](https://devforum.zoom.us/t/customer-key-set-by-android-sdk-is-not-reflected-in-api/59218/2 "2021-10-22T17:12:42Z")

</div>

Hi @june.glave, thanks for the post.

There were some issues with this field, but it should be working on the latest version of the SDK. Can you please try updating to the latest version? Let me know if you are still experiencing issues and we can investigate further.

Thanks!

---

<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:** [November 22, 2021, 3:13am UTC](https://devforum.zoom.us/t/customer-key-set-by-android-sdk-is-not-reflected-in-api/59218/3 "2021-11-22T03:13:11Z")

</div>

Closed on November 22, 2021, 3:13am UTC

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