API Change Log in January 2026

Monitoring > Live Upgrade

This API is used to fetch the access point upgrade information organized in a hierarchy from the configuration scope from which the upgrade was initiated.

This API is used to fetch the gateway upgrade information organized in a hierarchy from the configuration scope from which the upgrade was initiated.

This API is used to fetch the access point or gateway upgrade information in a flat format keyed by device serial number.

Services > Webhooks

This API is used to fetch a list of webhooks and their associated receiver details, such as the endpointURL, authentication mechanism, and the createdAt and updatedAt timestamps.

This API is used to create a new webhook using details of the receiver such as the endpoint URL and the authMechanis

These APIs are used to fetch, update, or delete the webhook details for the specified webhook ID such as the endpointURL and the authMechanism along with createdAt and updatedAt timestamps.

In the PUT call, all the request body parameters should be provided to update the Webhook.

In the PATCH call, one or multiple parameters in the body can be used to update the Webhook.

This API is used to rotate the HMAC key for an existing webhook.

Services > Location Analytics

This API is used to fetch visitor and client trend data for a tenant, either across all sites or for a specific site, within a specified time range.

This API is used to fetch the insights for each site of a tenant for a given time range.

Monitoring > Topology

This API is used to fetch information about the topology and device relations information for a specific site ID.

This API is used to fetch the details of an unmanaged device associated to the specified site.

This API is used to fetch the list of all isolated devices for a specific site. An isolated device is a device that does not have any relation with other devices in the same site.

The Neighbors API call response must include a complete list of all neighbors, along with the Site ID associated with each neighbor.

MSP > MSP

This API is used to fetch the list of tenants associated with an MSP account. Tenants list includes details such as tenant name, tenant CID, sites count, devices count with health status, alerts count, etc.

Monitoring > Clients

This API is used to fetch details of a specific client, based on the query parameters provided. Client detail includes name, status, health, etc.

This API is used to fetch details of a specific wireless client mobility detail.

Monitoring > Switch

This API fetches the list of all switches and provides information for each switch such as serial number, MAC address, model, software version, firmware version, IPv4 address, IPv6 addresses, etc.

This API is used to fetch the interface trends for the specified switch serial associated to a specific site. The interface trends include rx bytes, tx bytes, discards, giants, errors, runts, collision.

This API is used to fetch the hardware trends for a serial for a specific site. The hardware trends include cpu utilization, memory utilization, POE available, POE consumption and total power available.

Firmware Policy > Firmware Compliance

These APIs are used to fetch, create, update, or delete the firmware policy for devices.

To view the firmware details of a device, execute the API:

[GET] /network-services/v1alpha1/firmware-details.

Interfaces > Gw Port Profile

This API is used to fetch a list of gateway port profiles configured. A port profile can be used to configure Ethernet interface. Same profile can be applied to multiple interfaces and avoids repeating same configuration for interfaces.

These APIs are used to fetch, configure, update, or delete the parameters related to a specific gateway port profile.

System > Gw System

This API is used to fetch the list of gateway device system level configurations. The system level configurations include timezone settings, LCD settings, device VLAN settings, common firewall settings, AAA global timers, RADIUS or TACACS client settings, and other system settings.

These APIs are used to fetch, create, update, or delete the parameters related to the specified gateway system profile.

High Availability > Gw Cluster

This API is used to fetch the list of gateway cluster configuration.

These APIs are used to fetch, create, update, or delete the parameters related to the specified gateway cluster profiles.

Gateway Clustering Orchestration > Gw Cluster Intent

This API is used to fetch the list of gateway cluster mode configuration.

These APIs are used to fetch, create, update, or delete the parameters related to the specified gateway cluster intent profiles.

Central NAC Service > DPP Registration

This API is used to fetch the list of all Device Provisioning Protocol (DPP) registrations

This API is used to register a new DPP URI.

This API is used to update an existing DPP registration.

This API is used to delete a DPP registration.

Monitoring > Access Points

The softwareVersion is updated to firmwareVersion for the APIs listed under Monitoring > Access Points.

The response body of this API has been enhanced to include the following statistics for access points:

• publicIpv4—IPv4 address assigned to a device, server, or network interface that can be reached directly from the internet. It is an IPv4 address visible outside your private network

• lastRebootReason—Information about the reason for the last reboot.

• clusterId—Information about the cluster ID to which the Access Points is assigned.

• device_group_id—Information about the group ID to which the AP is assigned.

• deviceGroupName—Name of the device group to which the AP is assigned.

Services > Location

The path for Start an AP ranging scan API is updated from [POST] /network-services/v1alpha1/sitemaps/{site-id}/floors/{floor-id}/ap-ranging-scans/start to [POST] /network-services/v1alpha2/ap-ranging-scans

The POST /network-services/v1alpha1/ap-ranging-scans API is used to start an AP ranging scan for the given floor-id. AP ranging scans facilitate using automatic AP placement within the Floorplan manager as it allows the system to collect inter-AP ranging information in a shorter time frame. A Wi-Fi network outage is caused on executing the API call.

These APIs are updated to include Role-Based Access Control (RBAC) information for the asset tracking APIs. The RBAC data is read-only.

Monitoring > Clients

Monitoring > Switch

The APIs listed under Alias are updated to support the ALIAS_IPV4_SYSTEM_VLAN type for gateway system profile.

Central NAC > Cda Portal Skin Profile

In the request body, skinId parameter is updated to skin-id.

Central NAC > Cda Message Provider

In the request body, providerId parameter is updated to provider-id.

Central NAC > Cda Authz Policy

In the request body, policyId parameter is updated to policy-id.

Central NAC > Cda Portal Overrides Profile

In the request body, overrideId parameter is updated to override-id.

Central NAC > Cda Portal Profile

In the request body, portalId parameter is updated to portal-id.

Central NAC > Cda Auth Profile

In the request body, authProfileId parameter is updated to auth-profile-id.

Config Management > Config Checkpoint

In the request body, persona parameter is updated to device-function.

Extensions > Extension Vsphere

In the request body, persona parameter is updated to device-function.

High Availability

The following parameters are updated in the response body for the APIs listed under High Availability.

• persona is updated to device-function

• object_type is updated to object-type

• scope_id is updated to scope-id

• view_type is updated to view-type

Named Object

In the request body, persona parameter is updated to device-function.

Miscellaneous

The following APIs under Miscellaneous are updated:

• APIs listed under Switch Profiles, Switch Chassis, Packet Capture, Db Observer, Hardware Module Profile, Remote Management, and Feature Pack are moved under System.

• APIs listed under Mirror, Mirror Endpoint and Static MAC are moved under Interface.

• APIs listed under Ip Routing are moved under Routing & Overlays.

Scope Management > Site Collections

Site Collection IDs created using the Site Collections API can now be assigned during role-based policy creation.

Monitoring > Access Points

[GET] /network-monitoring/v1alpha2/aps

Monitoring > Gateways

[GET] /network-monitoring/v1alpha2/gateways

[GET] /network-monitoring/v1alpha2/gateways/{serial-number}

[GET] /network-monitoring/v1alpha2/gateways/{serial-number}/tunnels

[GET] /network-monitoring/v1alpha2/gateways/{serial-number}/tunnels/{tunnel-name}

Monitoring > FloorPlan

API listed under Monitoring > Location Services is removed.

[GET] /network-services/v1alpha1/wifi-clients-locations

Services > WIDS

Not available

Not available

System > Ddns Http

Not available