I don't think that's documented, or even fixed. With Central being dynamic, using micro-services, the web hook could come from anywhere.
Webhooks are used for cloud-to-cloud communication most of the times, and I have not seen many times used to reach out to internal. As an example, for ClearPass there is a service 'Skyhook', specifically to receive webhooks on a system that is on-premises. But it's specific for ClearPass.
If you really would like to run the webhook to internal, I would just configure it and see where it's originating from, then allow that and monitor/hope that it won't change; but expect it to change given the nature of webhooks.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------