# Published user-managed General App: deauthorization setup, verification and data deletion

**URL:** <https://devforum.zoom.us/t/published-user-managed-general-app-deauthorization-setup-verification-and-data-deletion/147816>\
**Category:** API and Webhooks\
**Created:** [November 9, 2026, 1:53pm UTC](https://devforum.zoom.us/t/published-user-managed-general-app-deauthorization-setup-verification-and-data-deletion/147816 "2026-11-09T13:53:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Takvimera](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/takvimera/32/77805_2.png) [@Takvimera](https://devforum.zoom.us/u/Takvimera)\
**Post date:** [November 9, 2026, 1:53pm UTC](https://devforum.zoom.us/t/published-user-managed-general-app-deauthorization-setup-verification-and-data-deletion/147816/1 "2026-11-09T13:53:05Z")

</div>

Hello Zoom Developer Team,

We maintain Takvimera, an appointment scheduling application with a published, user-managed General App. Its OAuth integration works in production.

We are implementing deauthorization handling. We have not configured a deauthorization notification endpoint yet, so we do not have a sample notification.

We reviewed:

> **[Apps Webhooks - Apps - Zoom Developer Docs](https://developers.zoom.us/docs/api/marketplace/events/)**
>
> The Zoom Developer Platform is an open platform that allows third-party developers to build applications and integrations upon Zoom’s video-first unified communications platform.

The documentation mentions a deauthorization URL at the bottom of the Information tab, links to webhook verification, and describes payload.signature as a unique identifier for each uninstall event.

Could you clarify the following for the current General App configuration?

1. Configuration  
Where exactly should we configure the production deauthorization URL? Is this separate from Event Subscriptions, and does changing it require another app review?

2. Request verification  
Does app\_deauthorized use x-zm-signature and x-zm-request-timestamp, with HMAC-SHA256 over “v0:{timestamp}:{raw\_body}” and the production Secret Token from the Access page?  
Please confirm whether payload.signature is only an event identifier, rather than a cryptographic signature.

3. Retries  
For a retried notification, are the request timestamp and signature regenerated, or are the original values reused? We want replay protection without rejecting legitimate delayed retries.

4. User matching  
Should we match both payload.account\_id and payload.user\_id to identify the disconnected integration? Is user\_id alone guaranteed to be globally unique?

5. Data deletion  
We store Zoom meeting join URLs in appointment records. When a user uninstalls our app, must those stored join URLs also be deleted, in addition to OAuth tokens and Zoom profile identifiers? Do we need to delete the meetings themselves, or only the Zoom-derived data stored by our application?

We would appreciate confirmation from the Developer or Marketplace team before changing the working production integration.

Thank you.

---

<div class="post-metadata">

**Author:** ![amanda-recallai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amanda-recallai/32/44747_2.png) [@amanda-recallai](https://devforum.zoom.us/u/amanda-recallai)\
**Post date:** [November 12, 2026, 1:35am UTC](https://devforum.zoom.us/t/published-user-managed-general-app-deauthorization-setup-verification-and-data-deletion/147816/2 "2026-11-12T01:35:34Z")

</div>

For configuration, set the dedicated deauthorization URL under **[Production → App Listing → Links & Support](https://devforum.zoom.us/t/new-build-flow-cannot-find-deauthorization-notification-endpoint-url-field-for-oauth-app/111942/2)**[, at the bottom](https://devforum.zoom.us/t/new-build-flow-cannot-find-deauthorization-notification-endpoint-url-field-for-oauth-app/111942/2). This setting is separate from Event Subscriptions. For a published app, [submit the change through **Send Updates** for review](https://developers.zoom.us/docs/distribute/published-apps/updating/). Saving the field alone does not update the production callback.

You can [request verification](https://developers.zoom.us/docs/api/webhooks/) by computing `v0=` plus the hex HMAC-SHA256 of `v0:{x-zm-request-timestamp}:{raw_body}`, keyed with your app’s webhook Secret Token from **Features → Access**. Compare that with `x-zm-signature`. Use the original request body bytes. `payload.signature` is the uninstall event’s identifier, not the cryptographic signature. I’d use it for deduplication separately from authenticating each delivery.

For data deletion, I’d include saved join URLs in your cleanup inventory alongside tokens and Zoom profile identifiers. For data you need to delete, remove it from your app/database. According to earlier staff guidance, [the Zoom meetings themselves need not be deleted](https://devforum.zoom.us/t/deauthorisation-api/20055/2). That distinction doesn’t establish an exemption allowing join URLs to be retained.

Recall.ai also offers a [Meeting Bot API](https://www.recall.ai/product/meeting-bot-api?utm_source=zoom&utm_medium=forum_answer) for bot-based meeting capture.

---

<div class="post-metadata">

**Author:** ![Takvimera](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/takvimera/32/77805_2.png) [@Takvimera](https://devforum.zoom.us/u/Takvimera)\
**Post date:** [November 12, 2026, 5:53am UTC](https://devforum.zoom.us/t/published-user-managed-general-app-deauthorization-setup-verification-and-data-deletion/147816/3 "2026-11-12T05:53:11Z")

</div>

Thanks, Amanda. Could someone from the Zoom Developer or Marketplace team confirm these points? We also still need answers to two questions. (1) On retried deauthorization notifications, are `x-zm-request-timestamp` and `x-zm-signature` regenerated? (2) Should we match on both `account_id` and `user_id`?
