Sam17
(Sam)
December 6, 2025, 7:13pm
1
I am getting a strange issue whereby maybe once every few weeks or so my app webhook gets disconnected due to failure to call.
I have two apps that communicate to the same endpoint on the same server, only one fails, the one which adds a custom header.
If I revalidate it will work for a time, maybe a few weeks again but will eventually fail again and block my webhooks.
Zoom does not give me a date or time or even status code that the webhook returned a failure so quite hard for me to track down.
What could be causing this?
1 Like
hi @Sam17
Thanks for reporting this issue!
I have not seen this issue on my end. Can you please verify that you are using the right Secret token associated with your app
1 Like
Sam17
(Sam)
December 22, 2025, 8:29pm
3
I can verify the ULR just fine and since I last verified it about a week ago, so I know it works.
It is just maybe once every few weeks zoom will suddenly disconnect my callback on this app and not the other, the only difference being the token.
1 Like
Interesting.
Can you please document once this happens again, by saving the response headers in your payload once you get it andd also the date when this happens and reach out back to me?
Unfortunately our Webhook logs don’t go back more than 7 days back
1 Like
Sam17
(Sam)
March 17, 2026, 8:30pm
5
I actually documented it this time. I got a fail for my new app and the log I possess looks like
{
“method”: “POST”,
“headers”: {
“x-forwarded-for”: “xxxx”,
“x-forwarded-proto”: “https”,
“x-forwarded-port”: “443”,
“host”: “xxxxx”,
“x-amzn-trace-id”: “Root=1-69b96028-7c0585101b2c36807d4998b7”,
“content-length”: “110”,
“x-zm-request-id”: “236735b0_e868_49d0_8a03_0e770a8c6585”,
“x-zm-signature”: “v0=6986cfb4dc4de0f9609372aadddeee5d2935c3a2cdac7760941a915fc3eeda26”,
“x-zm-request-timestamp”: “1773756455”,
“traceparent”: “00-71ab36af232bdab91926ef441a1d4fd1-85fd849ec7e347f7-00”,
“zm-trace-upstream”: “Meeting_Web_marketplace”,
“content-type”: “application/json; charset=utf-8”,
“user-agent”: “Zoom Marketplace/1.0a”
},
“body”: “{“payload”:{“plainToken”:“xxx”},“event_ts”:1773756455923,“event”:“endpoint.url_validation”}”,
}
As you can se it is just not calling with the extra header, but if I take one form a short while earlier it does
Sam17
(Sam)
March 17, 2026, 8:31pm
6
That log was from today at 14:07pm UTC