API Change Log in April 2026

Monitoring > Gateways

This API is used to fetch gateway uplink performance trends for the selected probe based on timestamp range.

Monitoring > Client Onboarding

This API is used to fetch per-stage onboarding export data, including summary totals and the top five delayed or failed dimensions.

This API is used to fetch the top reasons for a specific status based on the onboarding stage.

This API is used to fetch the top grouped onboarding counts based on stage and status.

Notification > Alerts

This API is used to fetch the list of alerts configurations for a given scope. Each configuration defines the threshold rules, severity mappings, and settings for a specific alert type. Configurations may be locally defined or inherited from a parent scope.

Services > FCO Response Information

This API is used to fetch the Automated Frequency Coordination channel and EIRP data for the specific AP serial number.

Security > Internal User

This API is used to fetch the list of Internal User profiles.

The access point's local user database for RADIUS (employee) and captive portal (guest) access. The local database supports up to 512 users on APs. Use this API to retrieve the list of Internal User profiles.This is only applicable for AP.

Monitoring > Access Points

A new parameter, clientCount is added to the response body for these APIs. The clientCount parameter displays the total number of wireless clients connected to an Access Point. It is supported on Access Points running on firmware version AOS 10.8 and above, and AOS 8.12 and above.

Monitoring > Site Health

The Site Health, Site Device Health, and Site Client Health list APIs are updated with the following changes:

• These APIs now fetch up to 1000 entries per request.

• The default sorting for these API call is changed from site-id to sitename. This change prevents duplicate or missing site entries in the response body. Previously, when sorting by site-id, changes in site health could cause sites to shift across pages between paginated API calls due to small time gaps, resulting in inconsistent results.

• When these APIs are executed without a sort parameter, the default sorting used site name in ascending order.

Monitoring > Gateway

The API is updated to include the following enhancements:

• In the request body, new filter parameters are added, including: siteId, model, status, deployment, macAddress, siteName, deviceName, firmwareVersion, and serialNumber.

• In the request body, new sort parameters are added, including: siteId, model, status, deployment, macAddress, siteName, deviceName, firmwareVersion, and serialNumber.

• In the response body, model, siteName, clusterName fields are added.

In the response body, siteName and clusterName fields are added.

The API is updated to include the following enhancements:

• In the request body new filter parameters are added, including: tunnelName, status, mode, encapsulation, and tunnelType.

• In the request body new sort parameters are added, including: tunnelName, destinationIpAddress, sourceIpAddress, mode, vni, and encapsulation.

• In the response body, tunnelType field is added.

The API is updated to include the following enhancements:

• In the request body new filter parameters are added, including: speed, duplex, vlan, macAddress, and portType.

• In the request body new sort parameters are added, including: mtu, speed, duplex, and vlan.

• In the response body, macAddress, adminState, operState, connectorType, and portType fields are added.

In the response body, macAddress, adminState, operState, connectorType, and portType fields are added.

The API is updated to include wanStatus, linkStatus, and status fields in the response body.

Interfaces > Interface Ethernet

Services > Location