1. Documentation
  2. ›
  3. Automation
  4. ›
  5. Getting Started

Getting Started

How to generate a User API Token

First you will need to generate a User API Token. You can do it here and this will carry your permissions.  This is from the Mist API docs NOTE – There also exists an Org Token which has some features that might be more useful depending on your use case. User Token Token persists under...

How do I find my Org and Site ID?

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.

HTTPS Response Codes

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...

Mist API Architecture

The diagram below conceptually describes how the Mist cloud API can be used to control remote Mist network infrastructure.

Mist API Introduction

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...

Org API Token

In Juniper/Mist you can create 2 types of API tokens.  This article is specific to Org Tokens and their benefits. Org Token Token persists under the org Token is not bound to any specific user, meaning the access does not depend upon the user’s access to the org Token can only be used for that specific org...