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:
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?
-
Configuration
Where exactly should we configure the production deauthorization URL? Is this separate from Event Subscriptions, and does changing it require another app review? -
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. -
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. -
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? -
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.