- Getting Started
- Getting Started
- Design Guides and Best Practices
- Wi-Fi Design
- Mist Edge
- Wi-Fi Basics and Design Best Practices
- WiFi Design Guides
- Wi-Fi Assurance
- Wi-Fi Troubleshooting
- Wired Switching
- WAN Edge
- Mist Access Assurance
- Location Based Services
- Premium Analytics
- Security and Cloud Administration
- Product Updates
- Security Alerts
NOTE – Please note the API endpoint varies by cloud environment. Please refer to the cloud endpoint URLs document. There is a tool call Postman that can be used to interact with the API without getting into coding. It is a really good place to start. You can download it here. First you...
To find your org_id or site_id, simply navigate to the Organization -> Settings page (org_id) or the Organization -> Site Configuration -> <Site Name> (site_id). As depicted in the screenshots Alternatively, when you are logged into your Mist UI you can find them in the URL as shown. AP page is used as a reference.
The full list of HTTP response codes and definitions can be found here: https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Mist uses the following response codes: Status Description 200 OK 400 Bad Request. The API endpoint exists but its syntax/payload is incorrect, detail may be given 401 Unauthorized 403 Permission Denied 404 Not found. The API endpoint doesn’t exist or resource...
The diagram below conceptually describes how the Mist cloud API can be used to control remote Mist network infrastructure.
From the beginning Mist has been a 100% API company. The API contains a set of tools known as endpoints for building software and applications that communicate with the Mist cloud. The Dashboard API is a modern, RESTful API using HTTPS requests to a URL and JSON as a human-readable format. The API is available...
Mist Automation Bootcamp featuring ServiceNow, Netbox and Dartmouth