# Add/expose the "client\_type" parameter to the relatively new \`user.presence\_status\_updated\` webhook event \[simple request\]

**URL:** <https://devforum.zoom.us/t/add-expose-the-client-type-parameter-to-the-relatively-new-user-presence-status-updated-webhook-event-simple-request/7338>\
**Category:** Feature Requests\
**Created:** [January 4, 2020, 6:38pm UTC](https://devforum.zoom.us/t/add-expose-the-client-type-parameter-to-the-relatively-new-user-presence-status-updated-webhook-event-simple-request/7338 "2020-01-04T18:38:49Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![saro](https://avatars.discourse-cdn.com/v4/letter/s/b38774/32.png) [@saro](https://devforum.zoom.us/u/saro)\
**Post date:** [January 4, 2020, 6:38pm UTC](https://devforum.zoom.us/t/add-expose-the-client-type-parameter-to-the-relatively-new-user-presence-status-updated-webhook-event-simple-request/7338/1 "2020-01-04T18:38:50Z")

</div>

**Is your feature request related to a problem? Please describe.**

There’s not really a _problem_, but let me describe why it makes sense to do so in my opinion, and should not be hard to implement on the Zoom backend at all (since the `client_type` is already part of the `user.signed_in` event which fires right before opening the mobile app, etc.). Opening the mobile app triggers a `user.signed_in` event followed by a presence event: `user.presence_status_updated` to `Available` – also, because the Zoom app is (often) closed in the background or out of the active memory on your mobile device when you get a message and you have it set to send mobile notifications, there will be an automatic `user.signed_in`/`user.presence_status_updated` event. At first, this was a bit misleading because it looks like the user is actually active, but it’s simply the app having to sign-in to deliver the push notification. Having the `client_type` parameter (which is already on the `user.signed_in` event) as part of the payload to the `user.presence_status_updated` event makes a lot of sense because one can differentiate between such a state.

**Describe the solution you’d like**

Pretty simple 🙂 !

Add/expose the (already existent) `client_type` parameter in the `user.presence_status_updated` webhook event (which should not be hard to do at all).

**Describe alternatives you’ve considered**

There’s not much in the terms of alternatives; the only thing you can do is messy and cannot be fully reliable. You could monitor the `user.signed_in` event that fires right before the `user.presence_status_updated` event, get the `client_type` from the sign-in event, check if it’s `iphone` or `android`, and then add a threshold (because they fire right after one another). However, that’s really not a clean way to do it and adding the `client_type` parameter to the `user.presence_status_updated` event is the proper way to do it.

**Additional context**  
I can provide screenshots if necessary, but I think this simple feature request speaks for itself.

---

<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:** [January 6, 2020, 5:40pm UTC](https://devforum.zoom.us/t/add-expose-the-client-type-parameter-to-the-relatively-new-user-presence-status-updated-webhook-event-simple-request/7338/2 "2020-01-06T17:40:19Z")

</div>

Hey @saro, thanks for suggesting this feature request! 🙂

I have passed it on to the team and will keep you updated. (ZOOM-131365)

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![saro](https://avatars.discourse-cdn.com/v4/letter/s/b38774/32.png) [@saro](https://devforum.zoom.us/u/saro)\
**Post date:** [January 6, 2020, 9:36pm UTC](https://devforum.zoom.us/t/add-expose-the-client-type-parameter-to-the-relatively-new-user-presence-status-updated-webhook-event-simple-request/7338/3 "2020-01-06T21:36:19Z")

</div>

Thanks, @tommy! It would also be useful if the `user_name` parameter was included in the `user.presence_status_updated` event (right now there’s just the e-mail/account id). If you could pass that along as well that would be great. Cheers 🙂

---

<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:** [January 6, 2020, 9:49pm UTC](https://devforum.zoom.us/t/add-expose-the-client-type-parameter-to-the-relatively-new-user-presence-status-updated-webhook-event-simple-request/7338/4 "2020-01-06T21:49:26Z")

</div>

Just added that to the feature request! 🙂

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![saro](https://avatars.discourse-cdn.com/v4/letter/s/b38774/32.png) [@saro](https://devforum.zoom.us/u/saro)\
**Post date:** [February 3, 2020, 2:44pm UTC](https://devforum.zoom.us/t/add-expose-the-client-type-parameter-to-the-relatively-new-user-presence-status-updated-webhook-event-simple-request/7338/5 "2020-02-03T14:44:12Z")

</div>

Hey @tommy,

Hope you’re doing well. I was wondering if there was an update to this (it should be relatively simple to implement since the parameters are already existent and exposed in the `user.signed_in` endpoint). I know you guys release API updates monthly (AFAIK), so I was just wondering. Cheers!

---

<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 3, 2020, 5:38pm UTC](https://devforum.zoom.us/t/add-expose-the-client-type-parameter-to-the-relatively-new-user-presence-status-updated-webhook-event-simple-request/7338/6 "2020-02-03T17:38:42Z")

</div>

Hey @saro,

We are looking into your feature request! Like you said, this should be a relatively simple change.

I will keep you updated on a timeline.

Thanks,  
Tommy

---

<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 6, 2020, 4:32pm UTC](https://devforum.zoom.us/t/add-expose-the-client-type-parameter-to-the-relatively-new-user-presence-status-updated-webhook-event-simple-request/7338/7 "2020-02-06T16:32:55Z")

</div>

Hey @saro,

We have agreed to add the client\_type property to the `user.presence_status_updated` webhook.

The estimated timeline is sometime in Q2. Stay updated here: [https://marketplace.zoom.us/docs/changelog](https://marketplace.zoom.us/docs/changelog)

Thanks,  
Tommy

---

<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:** [March 4, 2020, 4:46pm UTC](https://devforum.zoom.us/t/add-expose-the-client-type-parameter-to-the-relatively-new-user-presence-status-updated-webhook-event-simple-request/7338/8 "2020-03-04T16:46:35Z")

</div>

Hey @saro,

This feature request will be included in our April release.

Thanks,  
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, 7:25pm UTC](https://devforum.zoom.us/t/add-expose-the-client-type-parameter-to-the-relatively-new-user-presence-status-updated-webhook-event-simple-request/7338/9 "2020-08-21T19:25:22Z")

</div>

Closed on August 21, 2020, 7:25pm UTC


