API Change Log in May 2026

This topic lists the APIs updated in this release.

New MRT APIs

Table 1: 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

Table 2: 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

Table 3: Modified 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:

  • uptime

  • wlan_count

  • subnet_mask

  • mesh_role

GET /network-monitoring/v1/aps/{serial-number}

This API is enhanced to include the following parameters in the response body:

  • radio_type

  • subnet_mask

  • mesh_role

  • current_uplink_inuse

  • client_count

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:

  • The sitename parameter is added to the filter.

  • Based on the start and end timestamp range specified in the request body, the samplingIntervalInMinutes value is automatically set as follows:

    • 5 minutes — when the timestamp range is up to 1 day

    • 180 minutes (3 hours) — when the timestamp range is more than 1 day

Notifications > Insights

GET /network-notifications/v1/insights

The following are the enhancements to the source recommendations API:

  • The id parameter is updated to insight-id.

    To get the insight-id execute the GET /network-notifications/v1/insights API without entering any insight-id or site-id. This will fetch the list of source recommendations at a global level.

  • Pagination functionality is added for the source recommendations API. Pagination parameters includes limit, offset and sort.

  • The message field in the response body is removed.

Monitoring > Client Onboarding

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

These APIs are enhanced with the following update:

  • The type parameter is changed to stage.

  • The ID parameter is updated to version.

  • The view-type parameter is added that supports the following

    • DEFAULT

    • BY_CLIENT

    • BY_ATTEMPTS

GET /network-monitoring/v1/client-onboarding-stage/export

These APIs are enhanced with the following update:

  • The type parameter is changed to stage.

  • The ID parameter is updated to version.

  • The view-type parameter is added.

GET /network-monitoring/v1/client-onboarding-stage/reasons

These APIs are enhanced with the following update:

  • The type parameter is changed to stage.

  • The ID parameter is updated to version.

  • The view-type parameter is added.

  • The count parameter is added. It displays the top grouped counts for onboarding by stage and status. The count displays, topclients, topaccessdevices, band, topwlans, topreasons, and topservers.

GET /network-monitoring/v1/client-onboarding-stage/count

These APIs are enhanced with the following update:

  • The type parameter is changed to stage.

  • The ID parameter is updated to version.

  • The view-type parameter is added.

Configuration APIs

Table 4: Modified Configuration APIs

Method

Description

Gateway Clustering Orchestration > Gw Cluster Intent

The APIs under GW Cluster Intent are updated to support the following parameters:

  • The device-type parameter is added to the request body. This parameter supports BRANCH_GW, MOBILITY_GW, and VPNC. If the device-type parameter is not specified MOBILITY_GW is set as a default value.

  • The default-gateway-mode parameter is added to the request body to Enable or disable one-to-one-redundancy mode for auto cluster profiles.

    When this parameter is enabled, only two gateways are allowed in the cluster profile: one gateway is assigned the leader role, while the other remains in standby mode.

  • The uplink-tracking parameter is used to enable or disable uplink tracking for auto cluster profiles. This is applicable only for BRANCH_GW device-type with default-gateway-mode enabled.

  • The uplink-sharing parameter is used to enable or disable uplink sharing for auto cluster profiles. This is applicable only for BRANCH_GW device-type with default-gateway-mode enabled.

  • The coa-vrrp supports only VLAN for BRANCH_GW device-type.

  • The coa-enable parameter refers to Change of Authorization (CoA). If coa-vrrp is not defined and coa-enable is set to true, for BRANCH_GW device-type the system automatically selects the coa-vrrp value from the controller IP VLAN if available. For other device-type you must configure the coa-vrrp 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

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.