# Inconsistency with the Zoom Recording Webhook API

**URL:** <https://devforum.zoom.us/t/inconsistency-with-the-zoom-recording-webhook-api/137192>\
**Category:** API and Webhooks\
**Tags:** webhooks, recording, api\
**Created:** [September 9, 2025, 4:44am UTC](https://devforum.zoom.us/t/inconsistency-with-the-zoom-recording-webhook-api/137192 "2025-09-09T04:44:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sanket](https://avatars.discourse-cdn.com/v4/letter/s/57b2e6/32.png) [@sanket](https://devforum.zoom.us/u/sanket)\
**Post date:** [September 9, 2025, 4:44am UTC](https://devforum.zoom.us/t/inconsistency-with-the-zoom-recording-webhook-api/137192/1 "2025-09-09T04:44:02Z")

</div>

#### We have identified an inconsistency with the Zoom Recording Webhook that requires your attention.

For the following meeting IDs:

- **85750316412**

- **84371061977**

During each of these meetings, the recording was stopped while the session was still live and then restarted. This resulted in two separate recordings for each meeting. However, we observed that the webhook API was triggered only for the most recent recording and not for the earlier one.

Previously, the webhook functioned correctly even when the recording was stopped and restarted during the same meeting. In such cases, two separate recordings were generated, and webhook API were triggered for both. Over the past month, however, we have consistently encountered this issue where the webhook is only triggered for the latest recording.

This inconsistency is critical, as it impacts our ability to process and track recordings accurately. We kindly request that this matter be investigated and resolved at the earliest possible time.

Thank you for your continued support.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [September 10, 2025, 1:32pm UTC](https://devforum.zoom.us/t/inconsistency-with-the-zoom-recording-webhook-api/137192/2 "2025-09-10T13:32:03Z")

</div>

Hi @sanket  
Thanks for reaching out to us and reporting this behavior.  
Allow me to run some test on my end and I will get back to you with an update soon

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [September 10, 2025, 5:00pm UTC](https://devforum.zoom.us/t/inconsistency-with-the-zoom-recording-webhook-api/137192/3 "2025-09-10T17:00:18Z")

</div>

Hi @sanket  
I’m not aware of any recent changes to the Recording webhook, but I did some testing and noticed that I only received one `recording.completed` webhook for my meeting, even though I stopped the recording once. However, in the payload for that `recording.completed` event, I did receive all the files associated with the meeting specifically, I received two recordings differentiated by their `recording_start` and `recording_end` fields.

Are you seeing different behavior on your end?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [September 14, 2026, 8:37am UTC](https://devforum.zoom.us/t/inconsistency-with-the-zoom-recording-webhook-api/137192/4 "2026-09-14T08:37:12Z")

</div>

Closed on September 14, 2026, 8:37am UTC

This topic was automatically closed 368 days after the last reply. New replies are no longer allowed.