API Change Log in March 2026

This topic lists the APIs updated in this release.

New MRT APIs

Table 1: New MRT APIs

Method

Path

Description

Monitoring > Application Visibility

GET

/network-monitoring/v1/applications

 

This API is used to fetch applications accessed in a site by all clients or by a specific client

Monitoring > Client Onboarding

GET

/network-monitoring/v1/client-onboarding-score

This API fetches the connectivity score for different stages of the wireless client onboarding process. If the site-id value is null, the API returns the cumulative connectivity score at the global level.

The type filter is used to specify the wireless client onboarding stage. The supported filter types include:

  • assoc—Displays the percentage breakdown of wireless client association outcomes, categorized as successful, delayed, and failed.

  • auth—Displays the percentage breakdown of wireless client authentication outcomes, categorized as successful, delayed, and failed.

  • dhcp—Displays the percentage breakdown of wireless client DHCP outcomes, categorized as successful, delayed, and failed.

  • dns—Displays the percentage breakdown of initial DNS attempt outcomes after DHCP assignment, categorized as successful, delayed, and failed.

If the type filter value is set to null or empty, then the API call response pulls information for all stages.

Monitoring > Firewall Session

GET

/network-monitoring/v1/site-firewall-sessions

This API is used to fetch blocked or denied sessions logs from access points, AOS-CX switches, and gateways in a site.

GET

/network-monitoring/v1/client-firewall-sessions

This API is used to fetch the information of the firewall sessions logs. The logs are from access points, AOS-CX switches, and gateways in a site based on the given client MAC and filter.

GET

/network-monitoring/v1/firewall-clients

This API is used to fetch the list of clients from access points, AOS-CX switch, and gateways in a site based on the filter.

Monitoring > Switch

GET

/network-monitoring/v1/switches/{serial-number}/vsx

This API is used to fetch the Virtual Switching Extension (VSX) configuration, and operational details for the specified switch. If the switch does not support VSX or VSX is not configured, the API call returns a 200 response with an empty VSX object (all fields null).

Notification > Insights

GET

/network-notifications/v1/insights

This API is used to fetch an insight at the site level or a list of insights at the global level. If the site-id value is null, the API returns the list of recommended insights along with recommendation id (id) at the global level.

Based on the input values for the site ID (site-id) and recommendation ID (id), the API response displays insight information as follows:

  • If the site-id is defined and id is not defined, the response returns the complete list of insights at the site level.

  • If both site-id and id are defined, the response returns details for the specified recommendation at the site level.

  • If site-id and id is not defined, the response returns the complete list of insights at the global level.

Notification > Alerts

POST

/network-notifications/v1/alerts/clear

This API updates the state of the list of alerts specified in the request body by marking them as cleared. This removes them from the list of active alerts.

POST

/network-notifications/v1/alerts/defer

This API is used to defer one or more active alerts for a specified duration. When an alert is deferred, the selected alerts are not displayed in the active alerts list until the deferred period expires

POST

/network-notifications/v1/alerts/active

This API is used to move the deferred alerts back to the active state before the configured defer duration expires. The specified alerts are displayed in the active alerts list

POST

/network-notifications/v1/alerts/priority

This API is used to update the priority of the specified alert based on the details provided in the request body.

GET

/network-notifications/v1/alerts/classification

This API is used to fetch the list of alerts based on the classification criteria detail specified in the request body.

Alerts can be classified using the following attributes:

  • Severity

  • Status

  • Category

  • Device Type

  • Priority

  • Impacted Devices

  • Impacted Sites

GET

/network-notifications/v1/alerts/async-operations

The API is used to fetch the status of the update operations such as active, defer, priority, and classification.

Services > Location

POST

/network-services/v1/ap-ranging-scans

This API is used to start an AP ranging scan.

GET

/network-services/v1/sitemaps/{site-id}/floors/{floor-id}/ap-ranging-scans

This API is used to fetch a list of scan statuses for AP ranging scans that were triggered on this floor-id.

GET

/network-services/v1/sitemaps/{site-id}/floors/{floor-id}/ap-ranging-scans/{scan-id}

This API is used to fetch the status of the AP ranging scan identified by the scan-id.

DELETE

/network-services/v1/sitemaps/{site-id}/floors/{floor-id}/ap-ranging-scans/{scan-id}

This API is used to stop a previously created AP ranging scan. Only scans in the PENDING state can successfully be stopped. Once a scan has transitioned to the SCHEDULED or SCANNING states, the user will need to wait for the scan to complete before the network can be restored.

GET

/network-services/v1/asset-tags

This API is used to fetch a list of Asset Tags. Each Asset Tag in the returned list includes metadata details and last known location.

GET

/network-services/v1/asset-tags/{asset-tag-id}

This API is used to fetch detailed information about the specified Asset Tag.

PUT, POST

/network-services/v1/asset-tags/{asset-tag-id}/metadata

This API is used to replace, create, or delete asset tag metadata.

Troubleshooting > Access Points

POST

/network-troubleshooting/v1/aps/{serial-number}/ping

This API is used to initiate a ping test on an AP.

GET

/network-troubleshooting/v1/aps/{serial-number}/ping/async-operations/{taskID}

This API is used to fetch the status and result of the asynchronous ping test initiated on the specified AP.

POST

/network-troubleshooting/v1/aps/{serial-number}/traceroute

This API is used to initiate an asynchronous traceroute test on the specified AP.

GET

/network-troubleshooting/v1/aps/{serial-number}/traceroute/async-operations/{task-id}

This API is used to fetch the result of the asynchronous traceroute test initiated on the specified AP.

POST

/network-troubleshooting/v1/aps/{serial-number}/speedtest

This API is used to initiate an asynchronous speed test on the specified AP.

GET

/network-troubleshooting/v1/aps/{serial-number}/speedtest/async-operations/{task-id}

This API is used to fetch the result of the asynchronous speed test initiated on the specified AP.

POST

/network-troubleshooting/v1/aps/{serial-number}/http

This API is used to initiate an asynchronous HTTP test on the specified AP.

GET

/network-troubleshooting/v1/aps/{serial-number}/http/async-operations/{task-id}

This API is used to fetch the result of the asynchronous HTTP test initiated on the specified AP.

POST

/network-troubleshooting/v1/aps/{serial-number}/https

This API is used to initiate an asynchronous HTTPs test on the specified AP.

GET

/network-troubleshooting/v1/aps/{serial-number}/https/async-operations/{task-id}

This API is used to fetch the result of the asynchronous HTTPs test initiated on the specified AP.

POST

/network-troubleshooting/v1/aps/{serial-number}/tcp

This API is used to initiate an asynchronous TCP test on the specified AP.

GET

/network-troubleshooting/v1/aps/{serial-number}/tcp/async-operations/{task-id}

This API is used to fetch the result of the asynchronous TCP test initiated on the specified AP.

POST

/network-troubleshooting/v1/aps/{serial-number}/getArpTable

This API is used to initiate an asynchronous test to get ARP table on the specified AP.

GET

/network-troubleshooting/v1/aps/{serial-number}/getArpTable/async-operations/{task-id}

This API is used to fetch the result of the asynchronous test to get the ARP table initiated on the specified AP.

POST

/network-troubleshooting/v1/aps/{serial-number}/nslookup

This API is used to initiate an asynchronous Nslookup test on the specified AP.

GET

/network-troubleshooting/v1/aps/{serial-number}/nslookup/async-operations/{task-id}

This API is used to fetch the result of the asynchronous Nslookup test on the specified AP.

POST

/network-troubleshooting/v1/aps/{serial-number}/aaa

This API is used to initiate an asynchronous AAA test on the specified AP.

GET

/network-troubleshooting/v1/aps/{serial-number}/aaa/async-operations/{task-id}

This API is used to fetch the result of the asynchronous AAA test on the specified AP.

GET

/network-troubleshooting/v1/aps/{serial-number}/show-commands

This API is used to fetch the most commonly used or top show commands supported on a specified AP.

POST

/network-troubleshooting/v1/aps/{serial-number}/showCommands

This API is used to initiate an asynchronous show command test on a specified AP.

GET

/network-troubleshooting/v1/aps/{serial-number}/showCommands/async-operations/{task-id}

This API is used to fetch the result of the asynchronous show command test on a specified AP.

POST

/network-troubleshooting/v1/aps/{serial-number}/reboot

This API is used to initiate a Reboot operation on the specified Access Point.

POST

/network-troubleshooting/v1/aps/{serial-number}/rebootSwarm

This API is used to initiate a Reboot operation on the entire Swarm, triggered via its current conductor AP. The {serial-number} must be the serial of the Swarm's active conductor.

POST

/network-troubleshooting/v1/aps/{serial-number}/locate

This API is used to initiate a locate (e.g., blinking LED) operation on the specified Access Point.

POST

/network-troubleshooting/v1/aps/{serial-number}/disconnectUserAll

This API is used to initiate a disconnect action for all users connected to the specified Access Point.

POST

/network-troubleshooting/v1/aps/{serial-number}/disconnectUserByMacAddress

This API is used to initiate a disconnect action for a specific user connected to the specified Access Point, identified by their MAC address.

POST

/network-troubleshooting/v1/aps/{serial-number}/disconnectUserByNetwork

This API is used to initiate a disconnect action for all users connected to a specific network (SSID) on the specified Access Point.

GET

/network-troubleshooting/v1/aps/{serial-number}/list-tasks

This API is used to fetch a list of all active or recently completed asynchronous operations for the specified AP, grouped by test name.

Troubleshooting > CX Switches

POST

/network-troubleshooting/v1/cx/{serial-number}/ping

This API is used to initiate an asynchronous ping test on the specified AOS-CX switch.

GET

/network-troubleshooting/v1/cx/{serial-number}/ping/async-operations/{task-id}

This API is used to fetch the status and results of the asynchronous CX switch Ping test initiated on the specified AOS-CX switch.

POST

/network-troubleshooting/v1/cx/{serial-number}/traceroute

This API is used to initiate an asynchronous traceroute test on the specified AOS-CX switch.

GET

/network-troubleshooting/v1/cx/{serial-number}/traceroute/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous traceroute test initiated on the specified AOS-CX switch.

POST

/network-troubleshooting/v1/cx/{serial-number}/poeBounce

This API is used to initiate an asynchronous PoE bounce test on the specified AOS-CX switch.

GET

/network-troubleshooting/v1/cx/{serial-number}/poeBounce/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous PoE bounce test initiated on the specified AOS-CX switch.

POST

/network-troubleshooting/v1/cx/{serial-number}/portBounce

This API is used to initiate an asynchronous port bounce test on the specified AOS-CX switch.

GET

/network-troubleshooting/v1/cx/{serial-number}/portBounce/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous port bounce test initiated on the specified AOS-CX switch.

POST

/network-troubleshooting/v1/cx/{serial-number}/cableTest

This API is used to initiate an asynchronous cable test on the specified AOS-CX switch.

GET

/network-troubleshooting/v1/cx/{serial-number}/cableTest/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous cable test initiated on the specified AOS-CX switch.

POST

/network-troubleshooting/v1/cx/{serial-number}/http

This API is used to initiate an asynchronous HTTP test on the specified AOS-CX switch.

GET

/network-troubleshooting/v1/cx/{serial-number}/http/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous HTTP test initiated on the specified AOS-CX switch.

POST

/network-troubleshooting/v1/cx/{serial-number}/aaa

This API is used to initiate an asynchronous AAA test on the specified AOS-CX switch.

GET

/network-troubleshooting/v1/cx/{serial-number}/aaa/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous AAA test initiated on the specified CX switch.

GET

/network-troubleshooting/v1/cx/{serial-number}/show-commands

This API is used to fetch the most commonly used or top show commands supported on a specified AOS-CX switch.

POST

/network-troubleshooting/v1/cx/{serial-number}/showCommand

This API is used to initiate an asynchronous show command test on a specified AOS-CX switch.

GET

/network-troubleshooting/v1/cx/{serial-number}/showCommand/async-operations/{task-id}

This API is used to fetch the result of the asynchronous show command test on a specified AOS-CX switch.

POST

/network-troubleshooting/v1/cx/{serial-number}/locate

This API is used to initiate a locate (e.g., blinking LED) operation on the specified AOS-CX switch.

POST

/network-troubleshooting/v1/cx/{serial-number}/reboot

This API is used to initiate a Reboot operation on the specified AOS-CX switch.

GET

/network-troubleshooting/v1/cx/{serial-number}/list-tasks

This API is used to fetch a list of all active or recently completed asynchronous operations for the specified CX Switch, grouped by test name.

Troubleshooting > AOS-S Switches

POST

/network-troubleshooting/v1/aos-s/{serial-number}/ping

This API is used to initiate an asynchronous ping test on the specified AOS-S switch.

GET

/network-troubleshooting/v1/aos-s/{serial-number}/ping/async-operations/{task-id}

This API is used to fetch the status and results of the asynchronous ping test initiated on the specified AOS-S switch.

POST

/network-troubleshooting/v1/aos-s/{serial-number}/traceroute

This API is used to initiate an asynchronous traceroute test on the specified AOS-S switch.

GET

/network-troubleshooting/v1/aos-s/{serial-number}/traceroute/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous traceroute test initiated on the specified AOS-S switch.

POST

/network-troubleshooting/v1/aos-s/{serial-number}/poeBounce

This API is used to initiate an asynchronous PoE bounce test on the specified AOS-S switch.

GET

/network-troubleshooting/v1/aos-s/{serial-number}/poeBounce/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous PoE bounce test initiated on the specified AOS-S switch.

POST

/network-troubleshooting/v1/aos-s/{serial-number}/portBounce

This API is used to initiate an asynchronous port bounce test on the specified AOS-S switch.

GET

/network-troubleshooting/v1/aos-s/{serial-number}/portBounce/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous port bounce test initiated on the specified AOS-S switch.

POST

/network-troubleshooting/v1/aos-s/{serial-number}/cableTest

This API is used to initiate an asynchronous cable test on the specified AOS-S switch.

GET

/network-troubleshooting/v1/aos-s/{serial-number}/cableTest/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous cable test initiated on the specified AOS-S switch.

POST

/network-troubleshooting/v1/aos-s/{serial-number}/getArpTable

This API is used to initiate an asynchronous test to get ARP table on the specified AOS-S switch.

GET

/network-troubleshooting/v1/aos-s/{serial-number}/getArpTable/async-operations/{task-id}

This API is used to fetch the result of the asynchronous test to get the ARP table initiated on the specified AOS-S switch.

GET

/network-troubleshooting/v1/aso-s/{serial-number}/show-commands

This API is used to fetch the most commonly used or top show commands supported on a specified AOS-S switch.

POST

/network-troubleshooting/v1/aso-s/{serial-number}/showCommands

This API is used to initiate an asynchronous show command test on a specified AOS-S switch.

GET

/network-troubleshooting/v1/aso-s/{serial-number}/showCommands/async-operations/{task-id}

This API is used to fetch the result of the asynchronous show command test on a specified AOS-S switch.

POST

/network-troubleshooting/v1/aos-s/{serial-number}/reboot

This API is used to initiate a Reboot operation on the specified AOS-S switch.

POST

/network-troubleshooting/v1/aos-s/{serial-number}/locate

This API is used to initiate a locate (e.g., blinking LED) operation on the specified AOS-S switch.

GET

/network-troubleshooting/v1/aos-s/{serial-number}/list-tasks

This API is used to fetch a list of all active or recently completed asynchronous operations for the specified AOS-S Switch, grouped by test name.

Troubleshooting > Gateways

POST

/network-troubleshooting/v1/gateways/{serial-number}/ping

This API is used to initiate an asynchronous ping test on the specified gateway.

GET

/network-troubleshooting/v1/gateways/{serial-number}/ping/async-operations/{task-id}

This API is used to fetch the status and results of the asynchronous ping test initiated on the specified gateway.

POST

/network-troubleshooting/v1/gateways/{serial-number}/pingSweep

This API is used to initiate an asynchronous PingSweep on the specified gateway.

GET

/network-troubleshooting/v1/gateways/{serial-number}/pingSweep/async-operations/{task-id}

This API is used to fetch the status and results of the asynchronous PingSweep task initiated on the specified gateway.

POST

/network-troubleshooting/v1/gateways/{serial-number}/traceroute

This API is used to initiate an asynchronous traceroute task on the specified gateway.

GET

/network-troubleshooting/v1/gateways/{serial-number}/traceroute/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous traceroute test initiated on the specified gateway.

POST

/network-troubleshooting/v1/gateways/{serial-number}/poeBounce

This API is used to initiate an asynchronous PoE bounce test on the specified gateway.

GET

/network-troubleshooting/v1/gateways/{serial-number}/poeBounce/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous PoE bounce test initiated on the specified gateway.

POST

/network-troubleshooting/v1/gateways/{serial-number}/portBounce

This API is used to initiate an asynchronous port bounce test on the specified gateway.

GET

/network-troubleshooting/v1/gateways/{serial-number}/portBounce/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous port bounce test initiated on the specified gateway.

POST

/network-troubleshooting/v1/gateways/{serial-number}/iperf

This API is used to initiate an asynchronous Iperf test on the specified gateway.

GET

/network-troubleshooting/v1/gateways/{serial-number}/iperf/async-operations/{task-id}

This API is used to fetch the status and result of the asynchronous Iperf test initiated on the specified gateway.

POST

/network-troubleshooting/v1/gateways/{serial-number}/http

This API is used to initiate an asynchronous HTTP test on the specified gateway.

GET

/network-troubleshooting/v1/gateways/{serial-number}/http/async-operations/{task-id}

This API is used to fetch the result of the asynchronous HTTP test initiated on the specified gateway.

POST

/network-troubleshooting/v1/gateways/{serial-number}/https

This API is used to initiate an asynchronous HTTPs test on the specified gateway.

GET

/network-troubleshooting/v1/gateways/{serial-number}/https/async-operations/{task-id}

This API is used to fetch the result of the asynchronous HTTPs test initiated on the specified gateway.

POST

/network-troubleshooting/v1/gateways/{serial-number}/getArpTable

This API is used to initiate an asynchronous test to get ARP table on the specified gateway.

GET

/network-troubleshooting/v1/gateways/{serial-number}/getArpTable/async-operations/{task-id}

This API is used to fetch the result of the asynchronous test to get the ARP table initiated on the specified gateway.

GET

/network-troubleshooting/v1/gateways/{serial-number}/show-commands

This API is used to fetch the most commonly used or top show commands supported on a specified gateway.

POST

/network-troubleshooting/v1/gateways/{serial-number}/showCommands

This API is used to initiate an asynchronous show command test on a specified gateway.

GET

/network-troubleshooting/v1/gateways/{serial-number}/showCommands/async-operations/{task-id}

This API is used to fetch the result of the asynchronous show command test on a specified gateway.

POST

/network-troubleshooting/v1/gateways/{serial-number}/disconnectClientAll

This API is used to initiate a disconnect action for all clients connected to the specified Gateway.

POST

/network-troubleshooting/v1/gateways/{serial-number}/disconnectClientByMacAddress

This API is used to initiate a disconnect action for a specific client connected to the specified Gateway, identified by its MAC address.

POST

/network-troubleshooting/v1/gateways/{serial-number}/halt

This API is used to initiate a halt (shutdown) operation on the specified gateway.

GET

/network-troubleshooting/v1/gateways/{serial-number}/list-task

This API is used to fetch a list of all active or recently completed asynchronous operations for the specified gateway, groups by test name.

New Configuration APIs

Table 2: New Configuration APIs

Method

Path

Description

Scope Management > Global

GET

/network-config/v1/global

This API is used to fetch the Global Scope ID.

Modified APIs

MRT APIs

Table 3: Modified MRT APIs

Method

Description

Services > Location

GET /network-services/v1/sites/{site-id}/device-locations

The query-time parameter is removed in the v1 version of the API.

Monitoring > Site Health

GET /network-monitoring/v1/sites-health

The API is enhanced to support filter and sort query parameters:

Filter query—The API response can be filtered using the siteId and siteName parameters.

Sort query—The API response can be sorted in ascending or descending order based on siteName, siteHealth, deviceHealth, and clientHealth.

GET /network-monitoring/v1/sites-device-health

The API is enhanced to support filter and sort query parameters:

Filter query—The API response can be filtered using the siteId and siteName parameters.

Sort query—The API response can be sorted in ascending or descending order based on siteName, deviceHealth, apHealth, switchHealth, gatewayHealth, and bridgeHealth.

GET /network-monitoring/v1/sites-client-health

The API is enhanced to support filter and sort query parameters:

Filter query—The API response can be filtered using the siteId and siteName parameters.

Sort query—The API response can be sorted in ascending or descending order based on siteName, clientHealth, wirelessClientHealth, and wiredClientHealth.

Configuration APIs

Table 4: Modified Configuration APIs

Method

Description

Interfaces > Interface Management

The ipv4-static-alias and ipv6-static-alias parameters are removed from the APIs listed under the Interface Management section.

Named Object > Alias

POST /network-config/v1/aliases/{name}

This API is updated to support configuration of a helper address alias. To configure the helper address alias, set the alias type to ALIAS_IPV4_ADDRESSES_WITH_VRF.

This API is also updated to support the configuration of gateway RADIUS server IP alias profile and RADIUS shared secret alias profile. The reference to these RADIUS alias profile is used to configure the authentication server profile. To configure these parameters, set the alias type parameter as follows:

  • RADIUS server IP alias profile—Set the alias type to ALIAS_AUTH_SERVER_ADDRESS.

  • RADIUS shared secret alias profile—Set the alias type to ALIAS_SECRET_VALUE.

 

Interfaces > Interface Vlan

POST /network-config/v1/vlan-interfaces/{id}

The API is updated to include the server-alias parameter under ipv4-relay. The server-alias represents the alias name assigned to the DHCP relay server and must be created using the POST /network-config/v1/aliases/{name} API call.

Interfaces > Sw Port Profile

POST /network-config/v1alpha1/sw-port-profiles/{profile-name}

This API is updated to support the configuration of flow-telemetry attributes.

Only COLLECTOR_LOCAL is supported as the exporter-type.

When flow telemetry is enabled, the following objects are automatically created and can be configured at the switch level. The list of configurable objects created is as follows:

  • ipfix-flow-record

  • ipfix-flow-exporter

  • ipfix-flow-monitor

  • traffic-insight

  • Interface Ethernet

Interfaces > Interface Ethernet

Interfaces can now be configured with switch flow telemetry attribute. Use the ipfix-flow-monitor-in parameter to configure IPv4 and IPv6 monitor.

Interfaces > Interface Portchannel

Port-channel interfaces can now be configured with the switch flow telemetry attribute.

Assignments > Config Assignment

APIs listed under System > Config Assignment section is moved to Assignments > Config Assignment.

Deprecated APIs

Table 5: Deprecated APIs

Deprecated API

Alternate APIs

All alpha MRT APIs (v1alpha1, and v1alpha2) are marked as deprecated. You must use the corresponding v1 APIs.