Webhook for meeting expiration


This is an interesting use case, however, I do not think we have webhooks for meeting expiration. However, here is a work around that you can implement:

  1. Subscribe to the meeting has been created / updated webhook
  2. Identify the meetings that are instant, by looking at the meeting type (1 for instant meeting)
  3. Create a logic at your end which invalidates the cache after 24 / 48 hours after the “created_at” field from the payload.

Let me know if this helps