# Deauthorization notification for published app once on staging

**URL:** <https://devforum.zoom.us/t/deauthorization-notification-for-published-app-once-on-staging/67148>\
**Category:** App Submission\
**Created:** [April 6, 2022, 6:56pm UTC](https://devforum.zoom.us/t/deauthorization-notification-for-published-app-once-on-staging/67148 "2022-04-06T18:56:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JagLoop99](https://avatars.discourse-cdn.com/v4/letter/j/51bf81/32.png) [@JagLoop99](https://devforum.zoom.us/u/JagLoop99)\
**Post date:** [April 6, 2022, 6:56pm UTC](https://devforum.zoom.us/t/deauthorization-notification-for-published-app-once-on-staging/67148/1 "2022-04-06T18:56:46Z")

</div>

## Using this template helps us debug your issues more effectively 🙂

**Description**  
We have a published zoom app. We use the production credentials on our production, and staging for our staging environment. We test changes on staging and submit the app for approval on production.

However for the Deauthorization notification, there is only one endpoint. This make it hard to test that feature on staging. What is the best practice to test that on staging after we published to production

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
Oauth

**Which Endpoint/s?**  
Deauthorization notification, endpoint-url

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [April 13, 2022, 4:51pm UTC](https://devforum.zoom.us/t/deauthorization-notification-for-published-app-once-on-staging/67148/2 "2022-04-13T16:51:19Z")

</div>

Hi @JagLoop99

Thanks for reaching out to the Zoom Developer Forum, I am happy to help here!  
I was able to reach out to our Marketplace team to get more information about this topic.

- There is no staging environment for published apps
- The work around is to submit an UPDATE request: the changes are pushed to prod in that case
- Some devs change the de-authorization endpoint using an update request (we automatically approve that), then as explained previously with an update request, the changes are pushed to prod
- The devs confirm the app works as expected
- If it is, they submit the scope changes of the de-authorization process back to the staging environment

Hope this helps!  
Elisa

---

<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:** [May 14, 2022, 2:51am UTC](https://devforum.zoom.us/t/deauthorization-notification-for-published-app-once-on-staging/67148/3 "2022-05-14T02:51:48Z")

</div>

Closed on May 14, 2022, 2:51am UTC

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