# User.presence\_status\_updated scope requiremenets

**URL:** <https://devforum.zoom.us/t/user-presence-status-updated-scope-requiremenets/54310>\
**Category:** API and Webhooks\
**Created:** [July 16, 2021, 8:45pm UTC](https://devforum.zoom.us/t/user-presence-status-updated-scope-requiremenets/54310 "2021-07-16T20:45:40Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![patrick\_reclaim](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/patrick_reclaim/32/29252_2.png) [@patrick\_reclaim](https://devforum.zoom.us/u/patrick_reclaim)\
**Post date:** [July 16, 2021, 8:45pm UTC](https://devforum.zoom.us/t/user-presence-status-updated-scope-requiremenets/54310/1 "2021-07-16T20:45:40Z")

</div>

Can someone confirm what the scope requirements are for user.presence\_status\_updated? When we first built our app a few weeks back, it appears that user:read was all we needed and we have successfully received this webhook with just that scope.

But then we noticed some of our coworkers, who installed the in-dev integration more recently, weren’t getting the webhook. I started digging in and I was surprised to find that `user.presence_status_updated` is now documented to require user:read _and_ user:write.

What’s odd is that our marketplace settings won’t allow me to delete user:read because of the webhook, but they don’t have similar protection for user:write. That tells me something is perhaps in transition? Can anyone confirm if something is/has changed?

Thanks!

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [July 19, 2021, 4:38pm UTC](https://devforum.zoom.us/t/user-presence-status-updated-scope-requiremenets/54310/2 "2021-07-19T16:38:34Z")

</div>

Hi @patrick_reclaim,

Thank you for reaching out about this—while I don’t believe there have been any recent changes, can I kindly ask for the name of your app? I’m happy to take a closer look at your app and its configuration.

Thanks!  
Will

---

<div class="post-metadata">

**Author:** ![patrick\_reclaim](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/patrick_reclaim/32/29252_2.png) [@patrick\_reclaim](https://devforum.zoom.us/u/patrick_reclaim)\
**Post date:** [July 19, 2021, 5:08pm UTC](https://devforum.zoom.us/t/user-presence-status-updated-scope-requiremenets/54310/3 "2021-07-19T17:08:30Z")

</div>

Our production app is called “Reclaim.ai” but hasn’t yet been approved for marketplace listing. The main issue is the incongruity with this (when picking webhooks):

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/4/f/4ff54929715eb6e67258393d72686685422823e3.png)

---

<div class="post-metadata">

**Author:** ![patrick\_reclaim](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/patrick_reclaim/32/29252_2.png) [@patrick\_reclaim](https://devforum.zoom.us/u/patrick_reclaim)\
**Post date:** [July 19, 2021, 5:09pm UTC](https://devforum.zoom.us/t/user-presence-status-updated-scope-requiremenets/54310/4 "2021-07-19T17:09:05Z")

</div>

And this:

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

Note that the warning/tooltip is only there for `user:read` and not `user:write`.

In other words: the webhook UI suggests you need both scopes for the `user.presence_status_updated` event, but the scopes UI suggests you only need `user:read`.

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [July 20, 2021, 6:58pm UTC](https://devforum.zoom.us/t/user-presence-status-updated-scope-requiremenets/54310/5 "2021-07-20T18:58:42Z")

</div>

Hi @patrick_reclaim,

Thank you for clarifying—would it be possible to share the details of your coworkers, who installed the in-dev integration more recently, that weren’t getting the webhook? It does seem there could be some conflicting information here.

You can share these details with us directly at [developersupport@zoom.us](mailto:developersupport@zoom.us) and reference this thread.

Thanks,  
Will

---

<div class="post-metadata">

**Author:** ![patrick\_reclaim](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/patrick_reclaim/32/29252_2.png) [@patrick\_reclaim](https://devforum.zoom.us/u/patrick_reclaim)\
**Post date:** [July 20, 2021, 9:38pm UTC](https://devforum.zoom.us/t/user-presence-status-updated-scope-requiremenets/54310/6 "2021-07-20T21:38:07Z")

</div>

Turns out it was user error and we are able to receive the webhooks without the `user:write` scope. So really, I think this thread is simply a bug report: the “add features” section of the app definition (screenshot 1) incorrectly overstates the required scope.

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [July 21, 2021, 9:04pm UTC](https://devforum.zoom.us/t/user-presence-status-updated-scope-requiremenets/54310/7 "2021-07-21T21:04:52Z")

</div>

Hi @patrick_reclaim,

I see—thank you for clarifying. I will work with our team to make sure we can update the documentation on this.

Thanks again for your diligence in raising this with us,  
Will

---

<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:** [August 21, 2021, 7:05am UTC](https://devforum.zoom.us/t/user-presence-status-updated-scope-requiremenets/54310/8 "2021-08-21T07:05:50Z")

</div>

Closed on August 21, 2021, 7:05am UTC

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