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

For configuration, set the dedicated deauthorization URL under Production → App Listing → Links & Support, at the bottom. This setting is separate from Event Subscriptions. For a published app, submit the change through Send Updates for review. Saving the field alone does not update the production callback.

You can request verification 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. That distinction doesn’t establish an exemption allowing join URLs to be retained.

Recall.ai also offers a Meeting Bot API for bot-based meeting capture.