API Change Log in May 2026
This topic lists the APIs updated in this release.
New MRT APIs
|
Method |
Path |
Description |
|---|---|---|
|
Monitoring > Devices |
||
|
POST |
/network-monitoring/v1/device-notes |
This API is used to update the bulk serial numbers and adds a note to provide information about the specific device. |
|
GET |
/network-monitoring/v1/device-notes-async-operations/{id} |
This API is used to fetch the status of the note operation (POST /network-monitoring/v1/device-notes). |
|
Notifications > Insights |
||
|
GET |
/network-notifications/v1/insights-schema |
This API is used to fetch the JSON schema definition for one or all available insights and the count of Insights available. If insight-id is provided, the API returns only the schema for that specific insight. If insight-id is is not entered, then the API returns schemas for all available insights as a JSON string. |
New Configuration APIs
|
Method |
Path |
Description |
|---|---|---|
|
Application Experience > DAP |
||
|
GET |
/network-config/v1/dap |
This API is used to fetch the list of configured Dynamic Application Prioritization (DAP) global profiles. DAP is an application-aware QoS feature that dynamically optimizes traffic handling based on individual application requirements. Unlike traditional QoS methods that treat all traffic within a classification equally, Dynamic Application Prioritization adjusts network behavior per application. It automatically tunes advanced RF parameters, such as uplink scheduling, to meet the SLA (Service Level Agreement). |
|
GET, POST, PATCH, or DELETE |
/network-config/v1/dap/{name} |
These APIs are used to fetch, create, or update the parameters related to a specific Application Prioritization (DAP) global profile. |
|
Application Experience > DAP SLA |
||
|
GET |
/network-config/v1/dap-sla |
This API is used to fetch the list of configured Dynamic Application Prioritization (DAP) SLA profiles. SLA profile allows you to configure some SLA parameters such as latency, and jitter, based on which some specific applications can be optimized. A total of 32 the SLA profile numbers can be configured. |
|
GET, POST, PATCH, or DELETE |
/network-config/v1/dap-sla/{name} |
These APIs are used to fetch, create, or update the parameters related to a specific Dynamic Application Prioritization (DAP) SLA profile. |
|
Application Experience > DAP Application |
||
|
GET |
/network-config/v1/dap-application |
This API is used to fetch the list of configured Dynamic Application Prioritization (DAP) application profile. One DAP SLA profile must be configured under the DAP application profile to indicate how to optimize this application. |
|
GET, POST, PATCH, or DELETE |
/network-config/v1/dap-application/{name} |
These APIs are used to fetch, create, or update the parameters related to a specific DAP application profile. |
Modified APIs
MRT APIs
|
Method |
Description |
|---|---|
|
Monitoring > Access Points |
|
|
GET /network-monitoring/v1/aps |
This API is enhanced to include the following parameters in the response body:
|
|
GET /network-monitoring/v1/aps/{serial-number} |
This API is enhanced to include the following parameters in the response body:
|
|
GET /network-monitoring/v1/aps/{serial-number}/tunnels GET /network-monitoring/v1/aps/{serial-number}/tunnels/{tunnel-id |
These APIs are enhanced to include the crypto_type parameter in the response body. |
|
GET /network-monitoring/v1/top-aps-by-wireless-usage GET /network-monitoring/v1/top-aps-by-wired-usage GET /network-monitoring/v1/top-aps-by-usage GET /network-monitoring/v1/aps/{serial-number}/throughput-trends GET /network-monitoring/v1/aps/{serial-number}/cpu-utilization-trends GET /network-monitoring/v1/aps/{serial-number}/memory-utilization-trends GET /network-monitoring/v1/aps/{serial-number}/power-consumption-trends GET /network-monitoring/v1/radios/{radio-number}/throughput-trends GET /network-monitoring/v1/radios/{radio-number}/channel-utilization-trends GET /network-monitoring/v1/radios/{radio-number}/channel-quality-trends GET /network-monitoring/v1/aps/{serial-number}/radios/{radio-number}/noise-floor-trends GET /network-monitoring/v1/aps/{serial-number}/radios/{radio-number}/frames-trends GET /network-monitoring/v1/aps/{serial-number}/ports/{port-index}/throughput-trends GET /network-monitoring/v1/aps/{serial-number}/ports/{port-index}/frames-trends GET /network-monitoring/v1/aps/{serial-number}/ports/{port-index}/crc-trends GET /network-monitoring/v1/aps/{serial-number}/ports/{port-index}/collisions-trends GET /network-monitoring/v1/aps/{serial-number}/tunnels/{tunnel-id}/throughput-trends GET /network-monitoring/v1/aps/{serial-number}/tunnels/{tunnel-id}/packet-loss-trends GET /network-monitoring/v1/aps/{serial-number}/tunnels/{tunnel-id}/mos-trends GET /network-monitoring/v1/aps/{serial-number}/tunnels/{tunnel-id}/jitter-trends GET /network-monitoring/v1/aps/{serial-number}/tunnels/{tunnel-id}/latency-trend GET /network-monitoring/v1/aps/{serial-number}/wlans/{wlan-name}/throughput-trends GET /network-monitoring/v1/wlans/{wlan-name}/throughput-trends |
The trend and statistics APIs are updated with the following enhancements:
|
|
Notifications > Insights |
|
|
GET /network-notifications/v1/insights |
The following are the enhancements to the source recommendations API:
|
|
Monitoring > Client Onboarding |
|
|
GET /network-monitoring/v1/client-onboarding-score |
These APIs are enhanced with the following update:
|
|
GET /network-monitoring/v1/client-onboarding-stage/export |
These APIs are enhanced with the following update:
|
|
GET /network-monitoring/v1/client-onboarding-stage/reasons |
These APIs are enhanced with the following update:
|
|
GET /network-monitoring/v1/client-onboarding-stage/count |
These APIs are enhanced with the following update:
|
Configuration APIs
|
Method |
Description |
|---|---|
|
Gateway Clustering Orchestration > Gw Cluster Intent |
The APIs under GW Cluster Intent are updated to support the following parameters:
|
|
Miscellaneous > Overlay Wlan |
The APIs under Overlay WLAN are updated to support configuration of site-specific clusters terminating on BGWs. The gw-cluster-list parameter now includes support for SITE_CLUSTER_BGW. |
|
Central NAC > Cda Authz Policy POST /network-config/v1alpha1/authz-policies/{policy-id} |
A new attribute ATTR_ARUBA_SIMULTANEOUS_USE, is added to enhance the API. This attribute is listed under rule > enf-profile > radius-profile (radius profile object) > defined-attr. |
|
System > System Info The hostname-alias parameter is removed from the APIs listed under System Info. |
|
|
[POST} network-config/v1alpha1/system-info |
This API is modified for the hostname parameter to take direct value instead of fetching value from hostname-alias. Previously, the hostname parameter value could either be user-defined or you could assigned the hostname-alias value. The hostname-alias value was derived from the ALIAS_HOSTNAME parameter configured through the Alias API call. Now, the hostname-alias parameter has been removed, and users must explicitly define the hostname parameter value. |
|
Named Object > Alias The ALIAS_HOSTNAME is removed from the APIs listed under Alias |
|
Deprecated APIs
|
Deprecated API |
Alternate APIs |
|---|---|
|
All alpha MRT APIs (v1alpha1, and v1alpha2) are marked as deprecated. You must use the corresponding v1 APIs. |
|