Juniper Mist is deprecating the legacy site-level Marvis Insights API endpoint and its corresponding UI view — previously accessible under Monitor > Marvis Actions — in favor of the unified Alerts framework. Customers and integrations currently relying on this endpoint must migrate to the replacement Alerts endpoints before the End-of-Support date.

What is being deprecatedCopy Anchor Link

The following will not be supported after December 2026.

• API Endpoint GET /api/v1/sites/{site_id}/insights/marvis
• UI View—Analytics > Events

ReplacementsCopy Anchor Link

Customers should migrate to the following alerts API endpoints:

The UI view corresponding to the site-level Marvis Insights API endpoint will be incorporated under Monitor > Alerts.

Deprecation timelineCopy Anchor Link

Action requiredCopy Anchor Link

All customers and API integrations using GET /api/v1/sites/{site_id}/insights/marvis must complete the following before December 2026:

1. Migrate to GET /api/v1/sites/{site_id}/alarms/search (or the org-level equivalent) with equivalent query parameters.
2. Use GET /api/v1/const/alarm_defs to map legacy Marvis insight types to their corresponding alarm definitions.
3. For organizations managing alarm policies via API, switch to GET /api/v1/orgs/{org_id}/alarmtemplates for template management.
4. Test the new endpoint responses against your existing workflows and integrations prior to the end-of-support date.

02/2026 - Deprecation of the managed and disable_auto_config attributesCopy Anchor Link

To simplify device management in the Mist API, we have deprecated the following two attributes in the device configuration object (/api/v1/sites/{site_id}/devices/{device_id}) and the Org Inventory update calls (/api/v1/orgs/{org_id}/inventory), effective February 2026:

• managed — Previously used for adopted switches to indicate if they were managed by Mist (default: false). Setting this to true enabled Mist management for adopted switches.
• disable_auto_config — Previously used to disable the default behavior of cloud-ready switches being managed by Mist. Setting this to true meant the device would not be managed by Mist.

We have also merged these two attributes into mist_configured, as shown below:

• mist_configured: true — Configures the device to be managed by Mist.
• mist_configured: false — Means that Mist does not manage the device.

During the transition, the GET /api/v1/sites/{site_id}/devices/{device_id} object will return mist_configured: true/false along with managed (for adopted devices) and disable_auto_config (for claimed devices) for backward compatibility.

Please update your integrations to use mist_configured going forward.

11/2025 - Deprecation of the /summary endpointCopy Anchor Link

The following API endpoints will be deprecated in an upcoming release:

• Get Site Sle Summary, replaced by Get Site Sle Metric Summary Trend
• Get Site Sle Classifier Details, replaced by Get Site Sle Metric Classifier Summary Trend

09/2025 - API authentication update: Basic authentication to be deprecatedCopy Anchor Link

To enhance security and align with industry best practices, we will deprecate Basic Authentication for all use cases—including admin logins and scripts—effective September 2026. Before this date, all integrations must transition to token-based authentication to ensure uninterrupted access and support.

Why we are making this changeCopy Anchor Link

Basic authentication poses several security risks or limitation when using login/password authentication:

• No multi-factor authentication (MFA) support
• Credentials transmitted with every request (even over HTTPS)
• No scope limitations
• Vulnerable to credential theft and reuse

Industry security organizations (OWASP, NIST, CIS) strongly recommend token-based authentication as a more secure alternative.

Required actionsCopy Anchor Link

Before January 1, 2026, do the following:

1. Update all applications and integrations to use token-based authentication.
2. Remove basic authentication from your implementations.

Migration resourcesCopy Anchor Link

• Documentation: Mist API Tokens
• Support: Contact us at support@mist.com for assistance

Thank you for helping us maintain the security of the Juniper Mist platform.

04/2025 - Unpaginated APIs responses to be deprecatedCopy Anchor Link

Currently, the following API requests return an unpaginated, full list of inventory devices.

• GET /api/v1/orgs/:org_id/inventory - Get Org Inventory
• GET /api/v1/sites/:site_id/stats/devices - List Site Devices Stats

Starting from May 31, 2025, these API requests will fetch paginated responses to limit the size of the response. By default, the API response will fetch the first 100 entries in the list.

You can modify the number of entries in the response (range: 1 to 1000) by using the query parameter limit.

Currently, if you query this API directly when you have more than 100 devices in your organization inventory, we recommend that you update the scripts to handle the paginated responses.

For more information, see Pagination.

04/2025 - Virtual Chassis Device ID UpdateCopy Anchor Link

Starting with the April release, Virtual Chassis devices in Mist will now use a cloud-assigned virtual MAC address as the device ID, instead of the physical MAC address of the FPC0 member.

This enhancement ensures seamless connectivity even when the FPC0 member is replaced or renumbered.

Key benefits of this update:

• The virtual MAC address is not tied to any specific member device, allowing for easier replacement or renumbering of all members, including FPC0, without disrupting connectivity.

• Existing Virtual Chassis devices will continue to operate with FPC0 as the device ID unless the FPC0 is replaced or renumbered, at which point they will transition to the virtual MAC-enabled mode without impacting operations.

How to identify a virtual MAC-enabled Virtual Chassis:Copy Anchor Link

• Look for the Device MAC Address or ID. A MAC address starting with 020003 indicates that the Virtual Chassis is virtual MAC-enabled.

• More details one how to retrieve the Virtual Chassis Device ID from a Virtual Chassis member can be found in the Get Org Inventory API call description