# Webhook for meeting expiration

**URL:** <https://devforum.zoom.us/t/webhook-for-meeting-expiration/75278>\
**Category:** API and Webhooks\
**Created:** [September 1, 2022, 6:32pm UTC](https://devforum.zoom.us/t/webhook-for-meeting-expiration/75278 "2022-09-01T18:32:12Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ojus.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ojus.zoom/32/734_2.png) [@ojus.zoom](https://devforum.zoom.us/u/ojus.zoom)\
**Post date:** [September 10, 2022, 4:55am UTC](https://devforum.zoom.us/t/webhook-for-meeting-expiration/75278/3 "2022-09-10T04:55:37Z")

</div>

Hi,

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

---

_[View the full topic](https://devforum.zoom.us/t/webhook-for-meeting-expiration/75278)._
