Testing Webhooks

By testing webhooks, you can verify the configuration process as well as inspect and parse the event messages you will receive from Mist. If you do not have a webhook receiver available to you, you can use a public, free service. Many such services enable you to receive and inspect the incoming webhook POST messages from Juniper Mist.

These public sites create a random URL that you can use on a temporary basis. The data that you received is ephemeral and is deleted as soon as you close your browser. Using one of these sites from your browser, you can identify parameter data from the message payloads to help create your workflow.

After you configure your webhook, you can trigger it and view those messages as they are received on the public webhook receiver.

Two of these free testing webhook receivers are:

These sites are not Juniper maintained and are to be used at your own risk.

Test end-to-end Connectivity

With webhooks, you can test end-to-end connectivity from your Mist Cloud instance to your defined webhook receiver to confirm that you are receiving the webhook and are able to process it. This is a webhook for testing that webhooks are working. It serves the same function as a ping would for testing network connectivity, but you're testing your webhook functionality. This validates that no devices (a firewall or router) are blocking communications between the two endpoints.

This can be done from the API by issuing a POST (from your REST client) to, in this case, your org, the configured webhook (id) as seen in this example:

A successful result looks like this:

To see how to send a ping event to a site webhook, see Ping Site Webhook.

To see how to send a ping event to an organization webhook, see Ping Org Webhook.