Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Webhook Messages

SUMMARY Get familiar with the message format and the payloads for various webhook topics.

Message Format

Each webhook topic can have a slightly different format.

Most webhooks have the following structure where the event_details are the payload of events, as follows:

Payload Structure

All webhook messages are in JavaScript object notation (JSON) format and include the following information in the header, which describes the configuration of the message itself. The header information appears before the payload in the message. If you configure a custom header in the webhook configuration, it also appears here.

Infrastructure Payload Examples

For the full list of Webhooks samples, see API Sample Webhooks. This will show you sample webhook messages that the Mist Cloud sends for each of the given webhooks topics.

The following are just some of the webhook samples, starting with the infrastructure webhooks.

Alert

This alert (alarm) example displays a detected rogue AP, the count (number of times Juniper Mist detected it), and the AP and the basic service set identifier (BSSIDs) that detected it.

Audit

This example is an audits alert indicating that John Doe updated a device. It shows the organization (org_id) and site (site_id) the device belongs to.

Client Join

This client-join message displays the MAC address of the client that joined. It also displays the associated connection details the instant a client joins a wireless network.

Client Sessions

The client-sessions payload displays detailed information regarding the entire session from a client to a single AP.

Device Events

The device-events payload displays details about the device experiencing the event with the reason.

Device Updowns

The device-updowns webhook is a subset of the device-events webhook. It sends only the basic information of the device and reason (type) it went down.

Juniper Mist Edge Events

The mxedge-events webhook payload can contain basic information about an event occurring on an individual Juniper Mist Edge device similar to device-events.

Location Payload Examples

The next group is the Location webhooks, which are available only for sites (not organizations).

Location Coordinates

The location webhook payload correlates client information to a location on a map (floorplan) uploaded to Juniper Mist. An accurately scaled map and use of the SDK client are requirements for this webhook.

Occupancy Alerts

The occupancy-alerts webhook displays information about specific zones if they exceed the configured occupancy_limit.

RSSI Zone

The rssizone webhook payload displays devices that have exceeded a configured minimum RSSI threshold across a site.

SDK Client Scan Data

The SDK Client Scan Data webhook payload displays specific data about a client that isn’t available without installing an application (using the SDK) on the client itself.

Virtual Beacon Entry and Exit Event

The vbeacon webhook is triggered when a mobile device running the Juniper Mist SDK is entering or exiting the area defined by a virtual beacon.

Zone Entry and Exit Events

The zone webhook is triggered when a device enters or exits a defined zone.