Mist

aid: mist
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/mist.png
name: Mist
description: Mist (Mist Systems), acquired by Juniper Networks and now Juniper Mist, is an AI-driven cloud platform for wireless,
  wired, and WAN networking. The Juniper Mist Cloud API is a RESTful HTTPS/JSON API organized around an Org -> Site -> Device
  hierarchy, giving programmatic access to configuration, inventory, client analytics (SLE), the Marvis virtual network assistant,
  location services, and real-time event webhooks. Mist was an early Lightspeed Venture Partners portfolio company (seed,
  2014) before its Juniper acquisition.
url: https://raw.githubusercontent.com/api-evangelist/mist/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- lightspeed-venture-partners
x-tier: profiled
x-tier-reason: enriched-from-portfolio-lead
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Networking
- Wireless
- Wi-Fi
- Cloud Management
- Artificial Intelligence
- Network Automation
- Location Services
- Webhooks
- Juniper
apis:
- aid: mist:mist-admins-api
  name: Mist Admins API
  description: 'Admin API calls can be used to create, manage or authenticate Mist administrators.


    To register administrators into an existing MSP account or Organization, please check: * [Invite Msp Admin](/#operations/inviteMspAdmin)
    * [Invite Org Admin](/#operations/inviteOrgAdmin)'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Admins
  properties:
  - type: OpenAPI
    url: openapi/mist-admins-api-openapi.yml
- aid: mist:mist-admins-login-api
  name: Mist Admins Login API
  description: 'Login Endpoints when using Login/Password authentication, with or without 2FA.


    If the Login/Password authentication is successful, Mist will add a `csrftoken` cookie that must be added into the later
    API Requests (please see [csrfToken (Custom Header Signature)]($h/__auth_CsrfToken))'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Admins Login
  properties:
  - type: OpenAPI
    url: openapi/mist-admins-login-api-openapi.yml
- aid: mist:mist-admins-login-oauth2-api
  name: Mist Admins Login - OAuth2 API
  description: "A Mist account can be linked to OAuth2 providers:\n1. First, login with your Mist account\n2. Obtain the Authorization\
    \ URL for Linking with [Get Oauth 2 Authorization Url for Login](/#operations/getOauth2AuthorizationUrlForLogin).\nAs\
    \ OAuth2 flow goes through provider's UI and back with the authorization code, there are two ways to get it:\n  * in JSON\
    \ response, more usable for developers. Simply don\\'t specify the `forward` parameter when obtaining the authorization\
    \ URL\n  * as GET parameter, for UI where the user flow can be continued. Specify the landing page/url of your choice\
    \ \n3. Obtain the authorization code by clicking / going through Authorization URL Link Mist Account against OAuth2 Provider\
    \ by using the authorization code"
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Admins Login - OAuth2
  properties:
  - type: OpenAPI
    url: openapi/mist-admins-login-oauth2-api-openapi.yml
- aid: mist:mist-admins-logout-api
  name: Mist Admins Logout API
  description: Logout Endpoints when using Login/Password authentication, with or without 2FA.
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Admins Logout
  properties:
  - type: OpenAPI
    url: openapi/mist-admins-logout-api-openapi.yml
- aid: mist:mist-admins-lookup-api
  name: Mist Admins Lookup API
  description: Admin Lookup API Call is mainly used by Web UIs to know if a user must be redirected to an SSO URL for login.
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Admins Lookup
  properties:
  - type: OpenAPI
    url: openapi/mist-admins-lookup-api-openapi.yml
- aid: mist:mist-admins-recover-password-api
  name: Mist Admins Recover Password API
  description: Endpoints used to trigger a password recovery and validate the token sent by email.
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Admins Recover Password
  properties:
  - type: OpenAPI
    url: openapi/mist-admins-recover-password-api-openapi.yml
- aid: mist:mist-constants-definitions-api
  name: Mist Constants Definitions API
  description: API Calls to retrieve constant values that can be used in different parts of the configuration
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Constants Definitions
  properties:
  - type: OpenAPI
    url: openapi/mist-constants-definitions-api-openapi.yml
- aid: mist:mist-constants-events-api
  name: Mist Constants Events API
  description: API Calls to retrieve the definitions of the Mist events. These definitions are providing example of the Webhook
    payloads
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Constants Events
  properties:
  - type: OpenAPI
    url: openapi/mist-constants-events-api-openapi.yml
- aid: mist:mist-constants-models-api
  name: Mist Constants Models API
  description: API Calls to retrieve the list of Hardware Models and their features
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Constants Models
  properties:
  - type: OpenAPI
    url: openapi/mist-constants-models-api-openapi.yml
- aid: mist:mist-installer-api
  name: Mist Installer API
  description: "In a typical enterprise, a separate group of people, Installers, are responsible for install new devices.\
    \ May it be a new installation (e.g. new stores), a replacement installation (e.g. replacing Cisco APs with Mist APs),\
    \ or addition (e.g. adding new APs for better coverage). Instead of granting them Admin/Write privilege, it's more desirable\
    \ to grant them minimum privileges to do the initial provisioning so they cannot read sensible information (e.g. PSK of\
    \ a WLAN), or change configs of running APs.\nAt a high level, Installer APs try to achieve the following:\n1. identifying\
    \ a device by MAC (that\\u2019\\ \ns what they see)\n2. they can only touch configurations of the devices they\\u2019\\\
    \nre installing\n3. allow the following configurations: \n  * name * site assignment \n  * device profile assignment \n\
    \  * map and location (x/y) assignment \n  * claim (if not already in the inventory) \n  * replace existing device with\
    \ the device being installed\n\n**Grace Period**\n\nGrace period provides a dynamic way to limit what devices / sites\
    \ installer can work on. Generally installers work on recent deployments - bringing up new sites, add newly claimed devices\
    \ to new / existing sites. They make mistakes, too, and may need to further tweak some of the parameters. Default grace\
    \ period is 7 days and can be set from 1 day to 365 days."
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Installer
  properties:
  - type: OpenAPI
    url: openapi/mist-installer-api-openapi.yml
- aid: mist:mist-msps-admins-api
  name: Mist MSPs Admins API
  description: An MSP Admin refers to a user who has access to the Juniper Mist managed service provider (MSP) portal and
    is responsible for managing and administering the network operations of multiple customer organizations and sites.
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - MSPs Admins
  properties:
  - type: OpenAPI
    url: openapi/mist-msps-admins-api-openapi.yml
- aid: mist:mist-msps-api
  name: Mist MSPs API
  description: MSP (Managed Service Provider) contains multiple Organizations.
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - MSPs
  properties:
  - type: OpenAPI
    url: openapi/mist-msps-api-openapi.yml
- aid: mist:mist-msps-inventory-api
  name: Mist MSPs Inventory API
  description: API Calls to locate a device across all the Organizations attached to the MSP account.
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - MSPs Inventory
  properties:
  - type: OpenAPI
    url: openapi/mist-msps-inventory-api-openapi.yml
- aid: mist:mist-msps-licenses-api
  name: Mist MSPs Licenses API
  description: 'Licenses are a type of service or access that customers can purchase for various features or services offered
    by a company.


    Subscriptions can have different statuses, such as active, expired, exceeded, or trial, depending on their validity and
    usage. The status of a subscription determines whether it is currently active and valid, has expired, has exceeded the
    allowed usage limit, or is in a trial period.


    Licenses can be activated using an activation code, and the activation process confirms the inputted code and activates
    the subscription.


    Licenses can be managed at the MSP level for organization attached to an MSP account, or directly at the [Organization
    level]($h/Orgs%20Licenses/_overview)'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - MSPs Licenses
  properties:
  - type: OpenAPI
    url: openapi/mist-msps-licenses-api-openapi.yml
- aid: mist:mist-msps-logo-api
  name: Mist MSPs Logo API
  description: Manage the Mist portal logo at the MSP level. This logo will be displayed instead of the Juniper Mist Logo
    for all the Organizations attached to this MSP account.
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - MSPs Logo
  properties:
  - type: OpenAPI
    url: openapi/mist-msps-logo-api-openapi.yml
- aid: mist:mist-msps-logs-api
  name: Mist MSPs Logs API
  description: 'Audit Logs are records of activities initiated by users, providing a history of actions such as accessing,
    creating, updating, or deleting resources or components at the MSP level.


    These logs allow superusers and network administrators to track and maintain a record of user actions, including who performed
    specific actions and when.


    Audit logs are useful for monitoring user activity, investigating security breaches, ensuring compliance with regulations,
    and tracing configuration changes in a network.


    They can be filtered and analyzed to view specific information and granular-level details of each event.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - MSPs Logs
  properties:
  - type: OpenAPI
    url: openapi/mist-msps-logs-api-openapi.yml
- aid: mist:mist-msps-marvis-api
  name: Mist MSPs Marvis API
  description: 'Marvis is an AI-driven, interactive virtual network assistant that streamlines network operations, simplifies
    troubleshooting, and provides an enhanced user experience.

    It offers real-time network visibility, comprehensive insights, and automation customized for your network.

    Marvis can proactively identify issues, interpret their impact, determine root causes, and recommend fixes.

    It consists of components such as Marvis Actions, Marvis Minis, Conversational Assistant, Marvis Client, and Marvis Query
    Language.


    Marvis API Calls at the MSP level can be used to quickly detect network issues on all the Organizations attached to the
    MSP account.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - MSPs Marvis
  properties:
  - type: OpenAPI
    url: openapi/mist-msps-marvis-api-openapi.yml
- aid: mist:mist-msps-org-groups-api
  name: Mist MSPs Org Groups API
  description: 'Org Groups a way to group Organizations together based on certain criteria.


    They can be used for easier management and organization of multiple organizations within the MSP portal.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - MSPs Org Groups
  properties:
  - type: OpenAPI
    url: openapi/mist-msps-org-groups-api-openapi.yml
- aid: mist:mist-msps-orgs-api
  name: Mist MSPs Orgs API
  description: 'An organization usually represents a customer - which has inventories, licenses.


    An Organization can contain multiple sites. A site usually represents a deployment at the same location (a campus, an
    office).'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - MSPs Orgs
  properties:
  - type: OpenAPI
    url: openapi/mist-msps-orgs-api-openapi.yml
- aid: mist:mist-msps-sles-api
  name: Mist MSPs SLEs API
  description: 'SLEs, or Service-Level Expectations, are metrics used to monitor and report on the user experience of a Wireless,
    Wired or Wan network.


    They are generated through data science and machine learning algorithms and provide insights into various aspects of the
    network, such as coverage, capacity, connectivity, and performance.


    Mist SLEs help identify when users do not have sufficient network quality, when they face issues with connecting or roaming
    between access points, and when there are problems on the wired network.


    SLEs API Calls at the MSP level can be used to retrieve the SLEs summary for each Organization attached to the MSP account.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - MSPs SLEs
  properties:
  - type: OpenAPI
    url: openapi/mist-msps-sles-api-openapi.yml
- aid: mist:mist-msps-sso-api
  name: Mist MSPs SSO API
  description: 'MSP SSO, or Single Sign-On, is a method of authentication that allows users to securely log in to multiple
    applications and websites with a single set of login credentials.


    It involves integrating the MSP portal with an Identity Provider (IdP) using the Security Assertion Markup Language (SAML)
    framework.


    This enables users to authenticate themselves through their corporate IdP, eliminating the need to remember separate passwords
    or enter credentials each time they access the MSP portal.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - MSPs SSO
  properties:
  - type: OpenAPI
    url: openapi/mist-msps-sso-api-openapi.yml
- aid: mist:mist-msps-sso-roles-api
  name: Mist MSPs SSO Roles API
  description: 'MSP SSO roles refer to the different functions assigned to users within a Single Sign-On (SSO) system.


    These roles determine the tasks and actions that users can perform within the SSO system. There are typically predefined
    roles and custom roles in an SSO system.


    Roles in SSO provide a well-defined separation of responsibility and visibility, allowing for granular-level access control
    on SSO objects.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - MSPs SSO Roles
  properties:
  - type: OpenAPI
    url: openapi/mist-msps-sso-roles-api-openapi.yml
- aid: mist:mist-msps-tickets-api
  name: Mist MSPs Tickets API
  description: 'Support tickets are a means for users to seek assistance and resolve issues they encounter with a product
    or service.

    They allow users to communicate their problems or questions to the Juniper Mist support team, who can then provide guidance,
    troubleshooting, or solutions.

    Support tickets typically include information such as the type of issue, relevant details, and any necessary attachments.


    Support Tickets API Calls at the MSP level can be used to retrieve the tickets for each Organization attached to the MSP
    account.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - MSPs Tickets
  properties:
  - type: OpenAPI
    url: openapi/mist-msps-tickets-api-openapi.yml
- aid: mist:mist-orgs-admins-api
  name: Mist Orgs Admins API
  description: "An org admin, or organization administrator, is a user with administrative privileges within a specific organization.\
    \ They have the authority to manage and oversee the operations and settings of that organization's portal.\n\n The different\
    \ types of access levels for an org admin include:\n * Super User: This role has full access to the MSP portal and all\
    \ tenant organizations. A super user\ncan manage other administrators and has the highest level of privileges.\n * Network\
    \ Admin: A network admin has limited access to the MSP portal. They can be granted access\nto all organizations or specific\
    \ organizations, with access to limited features in the organizations' portals. They are responsible for monitoring, verifying,\
    \ and troubleshooting the network within their assigned organizations.\n * Observer: An observer has view-only access\
    \ to limited features in the MSP portal. They can be granted\naccess to all organizations or specific organizations, with\
    \ view-only access to limited features in the organizations' portals. Observers monitor events in the network and bring\
    \ any issues to the attention of the network administrator for resolution.\n * Installer: An installer can be granted\
    \ access to all organizations or specific organizations, with\nonly the ability to install access points for these organizations.\
    \ They are responsible for setting up and installing access points in the network.\n * Helpdesk: A helpdesk user can be\
    \ granted access to all organizations or specific organizations,\nwith only helpdesk monitoring and workflow capabilities\
    \ for these organizations. They assist with monitoring and resolving issues reported by users within the organization.\n\
    \n These different access levels allow org admins to perform their specific roles and responsibilities\nwithin the MSP\
    \ portal while ensuring appropriate access and security measures are in place."
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Admins
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-admins-api-openapi.yml
- aid: mist:mist-orgs-advanced-anti-malware-profiles-api
  name: Mist Orgs Advanced Anti Malware Profiles API
  description: 'The "Advanced Anti-Malware" feature in Sky ATP is a comprehensive security solution that leverages multiple
    techniques to detect and prevent malware attacks. Here are the key components of this feature:

    * **Flow-Based Antivirus Policy**: The policy checks inbound and outbound traffic to stop malware, quarantine infected
    systems, prevent data exfiltration, and disrupt lateral movement.

    * **Machine Learning-Based Threat Detection**: Sky ATP uses machine learning to identify zero-day threats and detect malware
    that traditional antivirus software might miss.

    * **Integration with SRX Series Firewalls**: The SRX Series firewalls integrate with Sky ATP to block known malicious
    file downloads and outbound Command and Control (C&C) traffic. This integration ensures that malware is quickly identified
    and dropped before it can infect a host.

    * **Real-Time Threat Intelligence**: Sky ATP distributes third-party threat intelligence feeds to all ATP-subscribed SRX
    firewalls for immediate action, reducing the attack surface.


    These components collectively provide a robust and automated threat detection and remediation solution, simplifying cybersecurity
    infrastructure and processes for organizations.


    For more details, you can refer to the Juniper documentation on advanced anti-malware policy configuration.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Advanced Anti Malware Profiles
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-advanced-anti-malware-profiles-api-openapi.yml
- aid: mist:mist-orgs-alarm-templates-api
  name: Mist Orgs Alarm Templates API
  description: 'An Alarm Template is a set of Alarm Rules that could be applied to

    one or more sites (while each site can only pick one Alarm Template), or to the

    whole org.



    Once created, the Alarm template must be assigned with the `alarmtemplate_id` attribute to one of the following

    * the whole org with the [Update Org](/#operations/updateOrg) API Call

    * one or multiple sites with the [Update Site Info](/#operations/updateSiteInfo) API Call'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Alarm Templates
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-alarm-templates-api-openapi.yml
- aid: mist:mist-orgs-alarms-api
  name: Mist Orgs Alarms API
  description: Alarms are triggered based on certain events. Alarms could be configured using an Alarm Template.
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Alarms
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-alarms-api-openapi.yml
- aid: mist:mist-orgs-antivirus-profiles-api
  name: Mist Orgs Antivirus Profiles API
  description: "Antivirus profiles are used to define the content to scan for any malware and the action to be taken when\
    \ malware is detected. \nThese profiles can be assigned to Content Security policies to scan Web, file transfer, and e-mail\
    \ traffic. \nThe profiles help in ensuring that the network is protected from malicious content by specifying fallback\
    \ options and notification methods when malware is detected or when the antivirus system experiences errors.\n\n\nKey\
    \ Features of Antivirus Profiles:\n\n* Content Scanning: Defines the content to scan for malware.\n* Action on Detection:\
    \ Specifies the action to be taken when malware is detected.\n* Fallback Options: Configures actions to be taken when\
    \ the antivirus system encounters errors.\n* Notification Options: Sets up methods to notify users when a fallback occurs\
    \ or a virus is detected."
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Antivirus Profiles
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-antivirus-profiles-api-openapi.yml
- aid: mist:mist-orgs-ap-templates-api
  name: Mist Orgs AP Templates API
  description: 'AP Templates are defining Wi-Fi and AP settings that can be assigned to Access Points based on different types
    of rules.


    AP Templates must be assigned to one or multiple sites to be used.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs AP Templates
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-ap-templates-api-openapi.yml
- aid: mist:mist-orgs-api
  name: Mist Orgs API
  description: An organization usually represents a customer - which has inventories, licenses. An Organization can contain
    multiple sites. A site usually represents a deployment at the same location (a campus, an office).
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-api-openapi.yml
- aid: mist:mist-orgs-api-tokens-api
  name: Mist Orgs API Tokens API
  description: 'Org API token is a unique identifier used by an application to authenticate and access a service''s API.

    These tokens are used to authenticate requests made to the API server and ensure secure access to the API.


    They are not bound to any specific user and provide access to the organization as a whole.


    Organization tokens support different privileges and can only be used for the specific organization they are generated
    for.


    Rate limiting is done on an individual token basis, so if one token reaches its rate limit, it does not impact other tokens.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs API Tokens
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-api-tokens-api-openapi.yml
- aid: mist:mist-orgs-asset-filters-api
  name: Mist Orgs Asset Filters API
  description: 'An Asset Filter is a feature that allows users to define specific criteria or conditions to filter and display
    only certain assets based on their attributes or properties.


    This requires the Asset Visibility subscription.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Asset Filters
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-asset-filters-api-openapi.yml
- aid: mist:mist-orgs-assets-api
  name: Mist Orgs Assets API
  description: 'An Asset refers to any equipment or item that is being tracked and monitored using Bluetooth Low Energy (BLE)
    beacon tags.


    This requires the Asset Visibility subscription.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Assets
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-assets-api-openapi.yml
- aid: mist:mist-orgs-cert-api
  name: Mist Orgs Cert API
  description: 'API Calls to manage Organization Certificates.


    The certificates can be used bu Access Assurance, during the SSO/SAML Authentication, ...'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Cert
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-cert-api-openapi.yml
- aid: mist:mist-orgs-clients-marvis-api
  name: Mist Orgs Clients - Marvis API
  description: 'Marvis Invites can be generated for (and belongs to) an Org. They can be generated by an Admin of an Org and
    can be revoked at anytime.


    Marvis Clients are devices that have the Marvis Android Client installed on them and are connected to a Juniper Mist AP.


    They provide detailed data and telemetry about the client''s wireless connection, including information about roaming
    behavior, connection type, and wireless properties.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Clients - Marvis
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-clients-marvis-api-openapi.yml
- aid: mist:mist-orgs-clients-nac-api
  name: Mist Orgs Clients - NAC API
  description: NAC Clients are devices connected to the network and authenticated by Juniper Mist Access Assurance.
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Clients - NAC
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-clients-nac-api-openapi.yml
- aid: mist:mist-orgs-clients-sdk-api
  name: Mist Orgs Clients - SDK API
  description: 'SDK Clients are devices that have installed an application using the Mist Software Development Kit (SDK).


    These clients can provide specific data and information that is not available without the installation of the SDK application.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Clients - SDK
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-clients-sdk-api-openapi.yml
- aid: mist:mist-orgs-clients-wan-api
  name: Mist Orgs Clients - Wan API
  description: WAN Clients are devices connected to a Juniper SRX or SSX gateway monitor or managed by Mist
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Clients - Wan
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-clients-wan-api-openapi.yml
- aid: mist:mist-orgs-clients-wired-api
  name: Mist Orgs Clients - Wired API
  description: Wired Clients are Wired devices connected to a Juniper switch monitored or managed by Mist.
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Clients - Wired
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-clients-wired-api-openapi.yml
- aid: mist:mist-orgs-clients-wireless-api
  name: Mist Orgs Clients - Wireless API
  description: Wireless Clients are Wi-Fi devices connected to a Juniper Mist Access Point.
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Clients - Wireless
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-clients-wireless-api-openapi.yml
- aid: mist:mist-orgs-crl-api
  name: Mist Orgs CRL API
  description: 'CRLs, or Certificate Revocation Lists, are time-stamped lists that identify digital certificates that have
    been invalidated before their expiration date. They include information about the reasons for revocation and the entities
    that issued the certificates.


    CRLs are used to prevent the usage of compromised digital certificates and signatures.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs CRL
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-crl-api-openapi.yml
- aid: mist:mist-orgs-device-profiles-api
  name: Mist Orgs Device Profiles API
  description: 'While Templates / RF Templates / Network Templates / Gateway Templates provides powerful ways to control how
    a Device\''s configuration is derived for a Site. There are cases where you\''d like another level of control at the Org
    Level.

    A Device Profile contains a subset of Device\''s configurations you\''d like a device to have. It will be merged at runtime
    when we\''re provisioning an AP.'
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Device Profiles
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-device-profiles-api-openapi.yml
- aid: mist:mist-orgs-devices-aos-api
  name: Mist Orgs Devices - AOS API
  description: API Calls specific to AOS (Aruba Operating System) devices
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  tags:
  - Orgs Devices - AOS
  properties:
  - type: OpenAPI
    url: openapi/mist-orgs-devices-aos-api-openapi.yml
- aid: mist:mist-orgs-devices-api
  name: Mist Orgs Devices API
  description: 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
  humanURL: https://www.juniper.net/documentation/us/en/software/mist/automation-integration/
  baseURL: https://api.mist.com/api/v1
  

# --- truncated at 32 KB (137 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/mist/refs/heads/main/apis.yml