Mist API
★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingapiKey, basic974 EndpointsREST
For Agents
Manage Juniper Mist organizations, sites, access points, switches, WLANs, and client telemetry programmatically. Supports configuration templates, RF analytics, and Marvis insights for AI-driven network operations.
Use for: I want to list all sites in my Mist organization, Push a WLAN template to a specific site, Retrieve the current clients connected to an access point, Check whether a switch is online and reporting healthy
Not supported: Does not handle endpoint device management, identity provisioning, or generic ITSM ticketing - use for Juniper Mist cloud network operations only.
The Mist API is the cloud management interface for Juniper Mist, an AI-driven enterprise wireless, wired, and WAN platform. It exposes 974 endpoints across organizations, sites, devices (APs, switches, gateways), wireless LANs, location services, and the Marvis virtual network assistant. Use it to provision networks, push configuration templates, query client and device telemetry, manage RF settings, and run automation against multi-site deployments.
Install Jentic One Beta
Connect the Mist API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mist API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmist.com%2Fmist" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmist.com%2Fmist" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Mist API.
Provision sites, devices, and WLAN templates across an organization
Pull live client, device, and RF event streams for troubleshooting
Push wireless network configuration and security policies to APs
Query Marvis insights and run network actions on flagged anomalies
Manage administrators, MSP tenants, and role-based access scopes
Configure location services, virtual beacons, and zone analytics
Retrieve historical SLE metrics for capacity and performance reviews
Use Cases
Patterns agents use Mist API for, with concrete tasks.
★ Multi-Site Wireless Provisioning
Standardize WLAN configuration across hundreds of branch sites by pushing templates from a central Mist organization. Network operators define SSIDs, security profiles, and RF policies once, then bind them to site groups. The API supports bulk site creation, device claim, and template assignment so a new branch can come online without per-site manual work.
Create a new site in org {org_id}, claim three AP serial numbers to it, and bind WLAN template {tpl_id} to the site
Network Health Monitoring
Continuously poll Mist for device status, client SLE scores, and active alarms to feed an internal NOC dashboard. The API exposes per-AP, per-switch, and per-site metrics with hourly and daily aggregations so an agent can detect coverage gaps, capacity issues, and recurring connection failures before tickets are filed.
Pull all alarms with severity critical from the last 4 hours for org {org_id} and post a summary to the NOC channel
AI-Assisted Troubleshooting with Marvis
Use the Marvis endpoints to surface AI-derived root causes for failing clients, bad cables, or DHCP issues. An agent can ask Marvis a natural-language question about a site, retrieve the recommended action, and apply config changes through the same API without operator handoff.
Ask Marvis to identify the top three issues affecting site {site_id} in the last hour and return the recommended remediation actions
Agent-Driven Network Operations
AI agents discovered through Jentic call Mist endpoints to execute scoped operator tasks: rolling AP firmware, changing a guest passphrase, or temporarily relaxing a captive portal rule. Jentic isolates the API token in its credential vault so the agent receives only execution scope, never the raw secret.
Use Jentic to find the Mist operation for updating a WLAN passphrase and execute it for SSID guest at site {site_id}
Key Endpoints
974 endpoints — the mist api is the cloud management interface for juniper mist, an ai-driven enterprise wireless, wired, and wan platform.
METHOD
PATH
DESCRIPTION
GET
/api/v1/orgs/{org_id}/sites
List sites in an organization
GET
/api/v1/sites/{site_id}/devices
List devices at a site
GET
/api/v1/sites/{site_id}/clients
List active clients at a site
GET
/api/v1/orgs/{org_id}/alarms
List alarms across an organization
POST
/api/v1/orgs/{org_id}/wlans
Create a WLAN configuration
GET
/api/v1/const/ap_channels
List supported AP channels
GET
/api/v1/orgs/{org_id}/sites
List sites in an organization
GET
/api/v1/sites/{site_id}/devices
List devices at a site
GET
/api/v1/sites/{site_id}/clients
List active clients at a site
GET
/api/v1/orgs/{org_id}/alarms
List alarms across an organization
POST
/api/v1/orgs/{org_id}/wlans
Create a WLAN configuration
GET
/api/v1/const/ap_channels
List supported AP channels
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Mist by hand means handling its API token in the Authorization header, choosing the right regional host among api.mist.com, gc1, ac2, and gc2, and coding calls across a large endpoint surface yourself. Through Jentic you install once, import Mist from the API Directory, store the token once, and your agent calls it.
Permission scoping
Mist puts the org id and site id in the URL path (/api/v1/orgs/{org_id}/sites, /api/v1/sites/{site_id}/devices), so a rule can pin your agent to one org or site. You choose the operations it may call, so a write like creating a WLAN is not included unless you add it.
Credential isolation
Your Mist API token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list Mist sites' or 'push a WLAN template', and Jentic returns the matching Mist operation with its input schema and example so the agent calls the right endpoint without navigating the full endpoint surface.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Mist API through Jentic.
What authentication does the Mist API use?
The Mist API supports API token authentication via the Authorization header, HTTP basic auth, and a CSRF token for session flows. Most agent integrations use the API token. Through Jentic, the token is held in the credential vault and injected at execution time so agent code never sees the raw value.
Can I provision a new site and claim access points with the Mist API?
Yes. Create the site under an organization, then call the device claim endpoint with the AP serial numbers or claim codes. After claim you can bind a WLAN template, set RF policy, and the APs will pull configuration on connect.
What are the rate limits for the Mist API?
Mist applies per-token request budgets that vary by endpoint family. Configuration writes are stricter than read calls, and bulk telemetry pulls should use the streaming or paged endpoints rather than tight loops. Check the Mist developer portal for current numeric limits before running large batches.
How do I retrieve Marvis insights through Jentic?
Search Jentic for queries like marvis insights or query marvis assistant, load the schema for the matching Mist operation, and execute with the org or site identifier. Jentic returns the structured response so an agent can branch on the recommended action.
Does the Mist API cover wired switches and SD-WAN gateways?
Yes. The same API surface that manages access points also covers Juniper EX-series switches and SSR/Session Smart gateways once they are claimed into a site. You can push port profiles, query interface stats, and apply WAN edge templates.
How do I find a specific Mist endpoint as an agent?
Run a Jentic search such as list mist sites or update wlan template, then call execute on the returned operation. The 974-endpoint surface is large, so intent-based discovery is faster than browsing the spec.
Can I limit what my agent is allowed to do with the Mist API?
Yes. Because you self-host Jentic One, your own rules decide which Mist operations and credentials the agent may use. Mist carries the org id and site id in the URL path, such as /api/v1/orgs/{org_id}/sites and /api/v1/sites/{site_id}/devices, so you can pin an agent to a single organization or site. You also choose which operations it can call, so a write like creating a WLAN stays out of reach unless you explicitly allow it.
GET STARTED