Devices are any Network device managed or monitored by Juniper Mist. It can be * Wireless Access Points * Juniper Switch (EX, QFX) * Juniper WAN Gateway (SRX, SSR) * Mist Edges * Other or 3rd party devices, like Cradlepoint Devices
Juniper Mist AI Orgs Devices 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 Devices. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes
10 operations
across 10 paths,
and defines 57 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.
10 operations10 paths57 schemas10 GET
Metadata
The identity and technical contract details declared by the specification.
Juniper Mist AI Orgs Devices 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 10
Across 10 paths, the API surfaces 10 operations — 10 GET. Each is listed below with its method, path, parameters, and response codes.
Orgs Devices 10
Devices are any Network device managed or monitored by Juniper Mist. It can be Wireless Access Points Juniper Switch (EX, QFX) Juniper WAN Gateway (SRX, SSR) Mist Edges Other or 3…
The contract defines 57 schemas that model the data the API accepts and returns. The most detailed are ap_search (36 properties), device_event (30 properties), gateway_search (27 properties), switch_search (24 properties). Each schema is shown below with its type and property counts.
response_device_search_results
array
response_config_history_search_item_wlans
array
response_config_history_search_item_radio
object
2 properties2 required
strings
array
response_device_events_search
object
6 properties5 required
count_org_devices_mxtunnel_status
string
enum: down, up
timestamp
number
Epoch (seconds)
response_config_history_search_item_radios
array
search_org_devices_mxtunnel_status
string
enum: down, up
device_event
object
30 properties3 required
device_type
string
enum: ap, gateway, switch
response_device_search
object
6 properties5 required
response_http401
object
1 property
ap_radio_mac_radio_macs
array
response_count
object
6 properties6 required
response_org_devices
object
1 property1 required
device_type_switch
string
Device Type. enum: switch
switch_search
object
24 properties1 required
response_config_history_search_results
array
org_device
object
2 properties2 required
device_type_with_all
string
ap, switch, gateway, router, all, default is ap. Supports comma-separated values for multiple types (e.g., type=switch,gateway)
ap_search_wlans
array
response_device_config_cmd
object
1 property1 required
ap_radio_macs
array
response_device_search_results_items
device_search_radius_stat
object
4 properties
org_devices
array
ha_cluster_node_enum
string
only for HA. enum: node0, node1
device_search_radius_stats
object
Property key is the RADIUS server IP Address
org_devices_events_count_distinct
string
enum: ap, apfw, model, orgid, siteid, text, timestamp, type
