# Delayed webhook events **URL:** \ **Category:** API and Webhooks\ **Created:** [October 16, 2025, 6:26pm UTC](https://devforum.zoom.us/t/delayed-webhook-events/138096 "2025-10-16T18:26:28Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![mcbalto](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mcbalto/32/33022_2.png) [@mcbalto](https://devforum.zoom.us/u/mcbalto)\ **Post date:** [October 16, 2025, 6:26pm UTC](https://devforum.zoom.us/t/delayed-webhook-events/138096/1 "2025-10-16T18:26:29Z")
Hi, we are noticing that zoom phone webhook events are coming in very delayed. in the below example it seemed to have come in 5 minutes late. The payload phone number and names are redacted. It came into our system at 2025-10-03T15:05:01.838024+00:00 but according to the payload the event happened at 2025-10-03T14:59:59Z. Is it possible to confirm on zoom side this is what happened? If so, is there anything we can do about it? ```auto {"event":"phone.caller_connected","payload":{"account_id":"MvDtKKBIQiqBDvuGE3Vx6Q","object":{"call_id":"068dfe4d827b319ffbc","caller":{"name":"redacted","extension_id":"L2iwaHU8SByLcamq2vZq3Q","extension_type":"user","user_id":"YVsC43EpSk6dyFUbzDGQuA","timezone":"America/New_York","extension_number":1122,"phone_number":"+12489701111","device_id":"a3e7343395a2e4437754a655beab5807a35ef4339e25679d544a81e37f1e47da","device_type":"Windows_Client(6.6.1.15968)","device_name":"APR-FRMG-6003","connection_type":"voip"},"callee":{"extension_type":"pstn","extension_number":12485089817,"phone_number":"+12485082222","connection_type":"pstn_off_net"},"ringing_start_time":"2025-10-03T14:59:36Z","connected_start_time":"2025-10-03T14:59:59Z"}},"event_ts":1759503599540} ``` ---
**Author:** ![mcbalto](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mcbalto/32/33022_2.png) [@mcbalto](https://devforum.zoom.us/u/mcbalto)\ **Post date:** [October 23, 2025, 2:58pm UTC](https://devforum.zoom.us/t/delayed-webhook-events/138096/2 "2025-10-23T14:58:11Z")
hi @elisa.zoom is there a way we can get this looked at? thanks ---
**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:** [October 23, 2025, 3:33pm UTC](https://devforum.zoom.us/t/delayed-webhook-events/138096/3 "2025-10-23T15:33:02Z")
Hi @mcbalto Thanks for reaching out to us and sorry to hear you are having issues receiving events. Our logs only go back 7 days, do you happen to have a more recent event so I can escalate this with our Engineering team please ---
**Author:** ![mcbalto](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mcbalto/32/33022_2.png) [@mcbalto](https://devforum.zoom.us/u/mcbalto)\ **Post date:** [October 23, 2025, 6:33pm UTC](https://devforum.zoom.us/t/delayed-webhook-events/138096/4 "2025-10-23T18:33:57Z")
@elisa.zoom this one came in 5 mins later than it should. the event time here is 10:19:40am CST but it hit our system at 10:24:47 > {“event”:“phone.caller\_ended”,“payload”:{“account\_id”:“MvDtKKBIQiqBDvuGE3Vx6Q”,“object”:{“call\_id”:“068f652f927b0073d7f”,“caller”:{“name”:“Jack A”,“extension\_id”:“KSDDDNkCQ9upBVnRcinrvQ”,“extension\_type”:“user”,“user\_id”:“P0NBfvZzRqSNhAW1y1CQEw”,“timezone”:“America/New\_York”,“extension\_number”:1153,“phone\_number”:“+1248\*\*\*\*\*\*\*”,“device\_id”:“c657662a571b19ae21e5d73faf6edba56f4d1cca582a3b35d7fbec8c9878679f”,“device\_type”:“Windows\_Client(6.5.12.14128)”,“device\_name”:“APR-AAD-1026”,“connection\_type”:“voip”},“callee”:{“extension\_type”:“pstn”,“extension\_number”:14047322130,“phone\_number”:“+1404\*\*\*\*\*\*\*”,“connection\_type”:“pstn\_off\_net”},“ringing\_start\_time”:“2025-10-20T15:19:21Z”,“call\_end\_time”:“2025-10-20T15:19:39Z”,“connected\_start\_time”:“2025-10-20T15:19:35Z”,“handup\_result”:“Call connected”}},“event\_ts”:1760973580195} ---
**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:** [October 23, 2025, 7:35pm UTC](https://devforum.zoom.us/t/delayed-webhook-events/138096/5 "2025-10-23T19:35:21Z")
Thanks for sharing this. I will get back to you with an update soon @mcbalto ( ZSEE-183902 internal ticket number just for reference) ---
**Author:** ![Velvet](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/velvet/32/52895_2.png) [@Velvet](https://devforum.zoom.us/u/Velvet)\ **Post date:** [October 24, 2025, 6:57am UTC](https://devforum.zoom.us/t/delayed-webhook-events/138096/6 "2025-10-24T06:57:43Z")
thanks for sharing this information ---
**Author:** ![mcbalto](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mcbalto/32/33022_2.png) [@mcbalto](https://devforum.zoom.us/u/mcbalto)\ **Post date:** [October 30, 2025, 1:45pm UTC](https://devforum.zoom.us/t/delayed-webhook-events/138096/7 "2025-10-30T13:45:55Z")
hi @elisa.zoom , any updates on this? thanks ---
**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:** [October 30, 2025, 6:57pm UTC](https://devforum.zoom.us/t/delayed-webhook-events/138096/8 "2025-10-30T18:57:53Z")
Hi @mcbalto Thanks for your patience here! I do have an update for you, our Engineering team confirmed the following: We sent the webhook first time at 2025-10-20 15:19:39 but the webhook was not successfully sent and we recevied the status is -7 meaning usually caused by network jitter. This most likely happens at customer’s side. So we sent it again after 5 mins according to our [re-try policy](https://developers.zoom.us/docs/api/webhooks/#unsuccessful-delivery). This time the event was succesfully delivered ---
**Author:** ![mcbalto](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mcbalto/32/33022_2.png) [@mcbalto](https://devforum.zoom.us/u/mcbalto)\ **Post date:** [October 30, 2025, 7:46pm UTC](https://devforum.zoom.us/t/delayed-webhook-events/138096/9 "2025-10-30T19:46:37Z")
Are there any indications like error messages or status codes that zoom received when attempting to send the payload? we don’t have any issues with webhooks in other systems @elisa.zoom ---
**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:** [October 30, 2025, 8:57pm UTC](https://devforum.zoom.us/t/delayed-webhook-events/138096/10 "2025-10-30T20:57:52Z")
Hi @mcbalto Yes, as I mentioned, our Engineering team said they recevied a -7 status which is caused by a network jitter. We recently introduced this endpoint: Get webhook logs > **[Marketplace APIs](https://developers.zoom.us/docs/api/marketplace/#tag/app/get/marketplace/apps/%7BappId%7D/webhook_logs)** > > The Marketplace APIs allow developers to access data related to their app and its usage in the marketplace. You should be able to audit your logs using this endpoint