# Webhook is calling in every child account

**URL:** <https://devforum.zoom.us/t/webhook-is-calling-in-every-child-account/81977>\
**Category:** API and Webhooks\
**Tags:** webhooks\
**Created:** [January 23, 2023, 7:02pm UTC](https://devforum.zoom.us/t/webhook-is-calling-in-every-child-account/81977 "2023-01-23T19:02:43Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ostadappbd](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ostadappbd/32/44820_2.png) [@ostadappbd](https://devforum.zoom.us/u/ostadappbd)\
**Post date:** [January 23, 2023, 7:02pm UTC](https://devforum.zoom.us/t/webhook-is-calling-in-every-child-account/81977/1 "2023-01-23T19:02:43Z")

</div>

I’ve a master account / owner account and under that account I’ve 19 more zoom accounts. All are Pro Plan.  
Recently I’ve configured Zoom Webhooks and noticed If I configure the webhook only in owner account by creating a Webhook Only app, it’s not getting the webhook notifications of other 19 child accounts, it’s only getting the notification from master zoom account or, the account which is the owner of that Webhook Only app.

So, I’ve decided to create 19 Webhook Only app in other 19 zoom accounts. And, I did that. So, now I’m getting notifications from my total 20 zoom accounts.

But the problem is, if account 1 throws a notification, all my 20 webhooks are getting the same notification!! Why is that? Is there any way to receive all 20 account webhook notifications in just 1 webhook url.

NB: I’m handling my webhook response properly and sending 200 response code after processing the webhook notification. But, still all the 20 webhook endpoints are getting the same notification, which is like a brute force attack in my server!

---

<div class="post-metadata">

**Author:** ![rarev](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rarev/32/38939_2.png) [@rarev](https://devforum.zoom.us/u/rarev)\
**Post date:** [January 23, 2023, 8:11pm UTC](https://devforum.zoom.us/t/webhook-is-calling-in-every-child-account/81977/2 "2023-01-23T20:11:20Z")

</div>

Hey @ostadappbd,

I can certainly see the issue there!

Allow me to do some testing on my end, I have some thoughts, but I haven’t tested this out yet. Once I do, I’ll get back to you.

Thanks!

---

<div class="post-metadata">

**Author:** ![ostadappbd](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ostadappbd/32/44820_2.png) [@ostadappbd](https://devforum.zoom.us/u/ostadappbd)\
**Post date:** [January 24, 2023, 2:35am UTC](https://devforum.zoom.us/t/webhook-is-calling-in-every-child-account/81977/4 "2023-01-24T02:35:14Z")

</div>

Okay Ron. Please let me know as soon as you figure out the solution.

Thank you & regards.

---

<div class="post-metadata">

**Author:** ![ostadappbd](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ostadappbd/32/44820_2.png) [@ostadappbd](https://devforum.zoom.us/u/ostadappbd)\
**Post date:** [January 26, 2023, 8:37am UTC](https://devforum.zoom.us/t/webhook-is-calling-in-every-child-account/81977/5 "2023-01-26T08:37:17Z")

</div>

Hello Ron, just a reminder.  
Did you find out any solution?

---

<div class="post-metadata">

**Author:** ![rarev](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rarev/32/38939_2.png) [@rarev](https://devforum.zoom.us/u/rarev)\
**Post date:** [January 26, 2023, 7:13pm UTC](https://devforum.zoom.us/t/webhook-is-calling-in-every-child-account/81977/6 "2023-01-26T19:13:05Z")

</div>

Hi @ostadappbd,

Not yet still trying to narrow down what could be happening.

---

<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:** [January 30, 2024, 10:49am UTC](https://devforum.zoom.us/t/webhook-is-calling-in-every-child-account/81977/7 "2024-01-30T10:49:16Z")

</div>

Closed on January 30, 2024, 10:49am UTC

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