Juniper Mist AI Orgs Webhooks API
An Org Webhook is a configuration that allows real-time events and data from the Org to be pushed to a provided url.It enables the collection of information about various topics such as device events, alarms, and audits updates at the org level.The Webhook can be set up and customized using the Mist API, allowing users to receive and analyze specific data from a particular site.
Juniper Mist AI Orgs Webhooks API is one of 211 APIs that Juniper Mist AI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Orgs Webhooks. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 8 operations across 5 paths, and defines 28 schemas. It is described by OpenAPI 3.1.0, at version 2604.1.1.
Requests are made against 12 base URLs: https://api.mist.com, https://api.gc1.mist.com, https://api.ac2.mist.com, https://api.gc2.mist.com, https://api.gc4.mist.com, https://api.eu.mist.com, https://api.gc3.mist.com, https://api.ac6.mist.com, https://api.gc6.mist.com, https://api.ac5.mist.com, https://api.gc5.mist.com, https://api.gc7.mist.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 3
Juniper Mist AI Orgs Webhooks API declares
3 security schemes
for authenticating requests.
An API key is passed in the header as Authorization (apiToken).
It accepts HTTP basic authentication (basicAuth).
An API key is passed in the header as X-CSRFToken (csrfToken).
By default, every request must be authenticated.
apiToken— Like many other API providers, it’s also possible to generate API Tokens to be used (in HTTP Header) for authentication. An API token ties to a Admin with equa…basicAuth— While our current UI uses Session / Cookie-based authentication, it’s also possible to do Basic Auth.csrfToken— This protects the website against [Cross Site Request Forgery](https://en.wikipedia.org/wiki/Cross-siterequestforgery), all the POST / PUT / DELETE APIs needs…
Paths & Operations 8
Across 5 paths, the API surfaces 8 operations — 1 DELETE, 4 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
An Org Webhook is a configuration that allows real-time events and data from the Org to be pushed to a provided url. It enables the collection of information about various topics…
Schemas 28
The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are webhook (24 properties), webhook_delivery (14 properties), search_webhook_delivery (6 properties), response_count (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Juniper Mist AI 12
Other APIs Juniper Mist AI publishes across the network.