A webhook is an HTTP-enabled callback. Basically, it is a web-based URL to which data is POSTed when an event occurs. In Momentum 4.x, there are multiple events which can cause a webhook to be called; for example, when a message is injected. The data in the POST to the webhook URL is JSON-encoded and includes various details about the event or events which triggered the webhook. Webhooks are configured in the Momentum web-based UI
To test a webhook, you need two things. First, you need to cause an event to happen which can trigger a webhook call. The easiest way to do this is probably to inject a message.
Second, you need to have an HTTP endpoint which will be called by the webhook using an HTTP POST. One quick-and-easy way to create such an endpoint is with Webhook.site. This free website allows you to create a temporary URL which can receive POSTs and show you what was sent to that URL. To set up an endpoint, go to http://webhook.site. Click on the "New URL" on the upper right corner of the page. This would give you a permanent unique URL that would be your webhook endpoint. That's it!
If you have successfully enabled webhooks post-install, Momentum should be pushing out the events as they happen. Do a simple test by injecting a message and observing if
Webhooks must be configured in the text based configuration file /opt/msys/app/webhooks-api/config/webhooks.json
Endpoint unable to accept JSON package
Authentication on the endpoint fails
JSON package too large
RabbitMQ process stalls on node
NOT cluster aware