API Change Log in February 2026

This topic lists the APIs updated in this release.

New MRT APIs

Table 1: New MRT APIs

Method

Path

Description

Monitoring > Access Points

GET

/network-monitoring/v1/bssids

This API is used to fetch the list of BSSIDs associated with a customer. Each BSSID in the response includes details such as the device serial number, device name, and MAC address. It also provides information about the radio number, radio MAC address, BSSID, WLAN name, operating band, and site details.

GET

/network-monitoring/v1/aps

This API is used to fetch a list of access point.

GET

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

This API is used to fetch details of a specified access point.

GET

/network-monitoring/v1/aps/{serial-number}/cpu-utilization-trends

This API is used to fetch CPU utilization information for a specified access point.

GET

/network-monitoring/v1/aps/{serial-number}/memory-utilization-trends

This API is used to fetch memory utilization information for a specified access point.

GET

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

This API is used to fetch a list of access point ports.

GET

/network-monitoring/v1/aps/{serial-number}/ports/{port-index}/collisions-trends

This API is used to fetch the port collision error for the specified access point.

GET

/network-monitoring/v1/aps/{serial-number}/ports/{port-index}/crc-trends

This API is used to fetch the port CRC errors for the specified access point.

GET

/network-monitoring/v1/aps/{serial-number}/ports/{port-index}/frames-trends

This API is used to fetch the port frame trends for the specified access point.

GET

/network-monitoring/v1/aps/{serial-number}/ports/{port-index}/throughput-trends

This API is used to fetch the port throughput trends for the specified Access Point.

GET

/network-monitoring/v1/aps/{serial-number}/power-consumption-trends

This API is used to fetch the power consumption information for the specified access point.

GET

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

This API is used to fetch the list of access point radios.

GET

network-monitoring/v1/aps/{serial-number}/radios/{radio-number}/channel-quality-trends

This API is used to fetch the quality information for the specified access point radio.

GET

/network-monitoring/v1/aps/{serial-number}/radios/{radio-number}/channel-utilization-trends

This API is used to fetch the channel utilization information for the specified access point radio.

GET

/network-monitoring/v1/aps/{serial-number}/radios/{radio-number}/frames-trends

This API is used to fetch the transmission information for the specified access point radio.

GET

network-monitoring/v1/aps/{serial-number}/radios/{radio-number}/noise-floor-trends

This API is used to fetch the noise floor information for the specified access point radio.

GET

/network-monitoring/v1/aps/{serial-number}/radios/{radio-number}/throughput-trends

This API is used to fetch the throughput trend for the specified access point radio.

GET

/network-monitoring/v1/aps/{serial-number}/throughput-trends

This API is used to fetch the throughput trend for the specified access point.

GET

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

This API is used to fetch the list of access point tunnels.

GET

/network-monitoring/v1/aps/{serial-number}/tunnels/{tunnel-id}

This API is used to fetch a specific tunnel details for an access point.

GET

/network-monitoring/v1/aps/{serial-number}/tunnels/{tunnel-id}/jitter-trends

This API is used to fetch the jitter trend for the specified access point tunnel.

GET

/network-monitoring/v1/aps/{serial-number}/tunnels/{tunnel-id}/latency-trends

This API is used to fetch the latency trend for the specified access point tunnel.

GET

/network-monitoring/v1/aps/{serial-number}/tunnels/{tunnel-id}/mos-trends

This API is used to fetch the MOS score trend for the specified access point tunnel.

GET

/network-monitoring/v1/aps/{serial-number}/tunnels/{tunnel-id}/packet-loss-trends

This API is used to fetch the packet loss trend for the specified access point tunnel.

GET

/network-monitoring/v1/aps/{serial-number}/tunnels/{tunnel-id}/throughput-trends

This API is used to fetch the throughput trend for the specified access point tunnel.

GET

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

This API is used to fetch the list of access point WLANs.

GET

/network-monitoring/v1/aps/{serial-number}/wlans/{wlan-name}/throughput-trends

This API is used to fetch the throughput trend for the specified access point WLAN.

Monitoring > Clients

GET

/network-monitoring/v1/clients

This API is used to fetch the list unified clients.

GET

/network-monitoring/v1/clients-topn-usage

This API is used to fetch the top N clients by usage.

GET

/network-monitoring/v1/clients-trend

This API is used to fetch the client's trend.

GET

/network-monitoring/v1/clients/{mac-address}

This API is used to fetch details for the specified client.

GET

/network-monitoring/v1/clients/{mac-address}/mobility-trail

This API is used to fetch the wireless client mobility details for the specified client.

Monitoring > Devices

GET

/network-monitoring/v1/devices

This API is used to fetch a list of devices.

PATCH

/network-monitoring/v1/devices/{serial-number}

This API is used to update the device notes of the specified device.

DELETE

/network-monitoring/v1/devices/{serial-number}

This API is used to delete a device by serial number.

Monitoring > FloorPlan

GET

/network-monitoring/v1/sitemaps-summary/{site-id}

This API is used to fetch a list of non-associated and non-deployed APs for a site.

POST

/network-monitoring/v1/sitemaps/{site-id}/network-devices-deployed

This API is used to place devices on a floor plan for a specific floorId.

GET

/network-monitoring/v1/sitemaps/{site-id}/network-devices-deployed

This API is used to fetch a list of devices placed on the floor plan. GeoMetry is not supported; only x and y are returned in meters in geoMetryRelative

POST

/network-monitoring/v1/sitemaps/{site-id}/network-devices-undeploy

This API is used to remove devices from the floor plan without disassociating them from the floor.

POST

/network-monitoring/v1/sitemaps/{site-id}/network-devices-assigned

This API is used to assigned or unassigned device from the floor. Only devices that are in an unassigned state are eligible for assignment.

GET

/network-monitoring/v1/sitemaps/{site-id}/network-devices-assigned

This API is used to fetch a list of devices that have been assigned to the floor.

GET, POST, or DELETE

/network-monitoring/v1/sitemaps/{site-id}/network-devices-planned

These APIs are used to fetch, place, or delete planned devices on the floor plan for a specific floorId, with geometryRelative specified in meters.

GET

/network-monitoring/v1/catalogue-aps

This API is used to fetch a list of real device (AP) information for planning.

POST

/network-monitoring/v1/sitemaps/{site-id}/floors

This API is used to create a new floor with FloorMapInput information. Optionally, pass buildingId to create a floor under a specific building.

GET, PUT, or DELETE

/network-monitoring/v1/sitemaps/{site-id}/floors/{floor-id}

This API is used to create, update, or remove a floor from a building using floorId. After removing floor, if building has no floors building also will be removed from site.

POST

/network-monitoring/v1/sitemaps/{site-id}/floors/{floor-id}/scale

This API is used to scale FloorMap. There are 2 ways. Using AnchorGeometry is one way, and using from, 'to' and distance is another way. To scale floor, at least one of input must be present.

GET, or PUT

/network-monitoring/v1/sitemaps/{site-id}/floors/{floor-id}/image

These APIs are used to fetch, or update the FloorMap Image of a given floor.

GET

/network-monitoring/v1/sitemaps/{site-id}/buildings

This API is used to fetch building and floor information created under a given site.

DELETE, PUT

/network-monitoring/v1/sitemaps/{site-id}/buildings/{building-id}

This API is used to delete or update a building and floors under this building. This action also removes floor entities such as devices, walls, region, boundary.

POST

/network-monitoring/v1/sitemaps/{site-id}/import

This API is used to import floors using third party / central / airwave files (supported files are ZIPand ESX).

GET

/network-monitoring/v1/sitemaps/{site-id}/import/{id}

This API is used to fetch the import status for a given site.

GET

/network-monitoring/v1/wall-types

This API is used to fetch a list of wall types, including both standard walls and custom walls.

POST, PUT, or DELETE

/network-monitoring/v1/wall-types

These APIs are used to create, update or delete wall types, including both standard walls and custom walls.

GET

/network-monitoring/v1/sitemaps/{site-id}/floors/{floor-id}/walls

This API is used to fetch all the walls which are drawn on the floor.

POST, PUT, or DELETE

/network-monitoring/v1/sitemaps/{site-id}/floors/{floor-id}/walls

These APIs are used to create, update, or delete walls on the floor.

GET

/network-monitoring/v1/sitemaps/{site-id}/floors/{floor-id}/zones

This API is used to fetch a list of zones for a floor.

POST, PUT, or DELETE

/network-monitoring/v1/sitemaps/{site-id}/floors/{floor-id}/zones

These APIs are used to create, update, or delete zones for a floor.

Monitoring > Gateways

GET

/network-monitoring/v1/gateways

This API is used to fetch a list of gateways.

GET

/network-monitoring/v1/gateways/{serial-number}

This API is used to fetch the details of the specified gateway.

GET

/network-monitoring/v1/gateways/{serial-number}/cpu-utilization-trends

This API is used to fetch CPU utilization trend for the specified gateway.

GET

/network-monitoring/v1/gateways/{serial-number}/dhcp_clients

This API is used to fetch the DHCP leases present in the DHCP pool for the specified gateway.

GET

/network-monitoring/v1/gateways/{serial-number}/dhcp_pools

This API is used to fetch the DHCP pools configured on the gateway.

GET

/network-monitoring/v1/gateways/{serial-number}/hardware-temperature-trends

This API is used to fetch the gateway hardware temperature trends.

GET

/network-monitoring/v1/gateways/{serial-number}/lan-tunnels-health-summary

This API is used to fetch the summary of gateway LAN tunnels health.

GET

/network-monitoring/v1/gateways/{serial-number}/memory-utilization-trends

This API is used to fetch the gateway memory utilization trends.

GET

/network-monitoring/v1/gateways/{serial-number}/ports

This API is used to fetch a list of gateway ports.

GET

/network-monitoring/v1/gateways/{serial-number}/ports/{port-number}

This API is used to fetch gateway port detail.

GET

network-monitoring/v1/gateways/{serial-number}/ports/{port-number}/frames-errors-trends

This API is used to fetch gateway port frames errors trend for the specified gateway port.

GET

/network-monitoring/v1/gateways/{serial-number}/ports/{port-number}/frames-packets-trends

This API is used to fetch gateway port frames packets trend for the specified gateway port.

GET

/network-monitoring/v1/gateways/{serial-number}/ports/{port-number}/frames-trends

This API is used to fetch gateway port frames trend for the specified gateway port.

GET

/network-monitoring/v1/gateways/{serial-number}/ports/{port-number}/throughput-trends

This API is used to fetch gateway port throughput trend for the specified gateway port.

GET

/network-monitoring/v1/gateways/{serial-number}/tunnels

This API is used to fetch the list gateway tunnels.

GET

/network-monitoring/v1/gateways/{serial-number}/tunnels/{tunnel-name}

This API is used to fetch details for the specified gateway tunnel.

GET

/network-monitoring/v1/gateways/{serial-number}/tunnels/{tunnel-name}/packets-trends

This API is used to fetch dropped packets trend for the specified gateway tunnel.

GET

/network-monitoring/v1/gateways/{serial-number}/tunnels/{tunnel-name}/status-trends

This API is used to fetch tunnel status trend for the specified gateway tunnel.

GET

/network-monitoring/v1/gateways/{serial-number}/tunnels/{tunnel-name}/throughput-trends

This API is used to fetch tunnel throughput trend for the specified gateway tunnel.

GET

/network-monitoring/v1/gateways/{serial-number}/uplinks

This API is used to fetch a list of gateway uplinks.

GET

/network-monitoring/v1/gateways/{serial-number}/uplinks/{link-tag}

This API is used to fetch details for the specified gateway uplink.

GET

/network-monitoring/v1/gateways/{serial-number}/uplinks/{link-tag}/throughput-trends

This API is used to fetch uplink throughput trend for the specified gateway uplink.

GET

/network-monitoring/v1/gateways/{serial-number}/uplinks/{link-tag}/wan-availability-trends

This API is used to fetch WAN availability trends for the specified gateway uplink.

GET

/network-monitoring/v1/gateways/{serial-number}/uplinks/{link-tag}/wan-compression-trends

This API is used to fetch WAN compression trends for the specified gateway uplink.

GET

/network-monitoring/v1/gateways/{serial-number}/uplinks/{vlan-id}/vpn-availability-trends

This API is used to fetch VPN availability trends for the specified gateway uplink.

GET

/network-monitoring/v1/gateways/{serial-number}/vlans

This API is used to fetch list Gateway VLANs.

GET

/network-monitoring/v1/gateways/{serial-number}/vlans/{vlan-id}

This API is used to fetch details for the specified gateway VLAN.

GET

/network-monitoring/v1/gateways/{serial-number}/vpn-availability-trends

This API is used to fetch VPN availability trends for the specified gateway VLAN.

GET

/network-monitoring/v1/gateways/{serial-number}/wan-availability-trends

This API is used to fetch WAN availability trends for the specified gateway VLAN.

GET

/network-monitoring/v1/gateways/{serial-number}/wan-tunnels-health-summary

This API is used to fetch summary of gateway WAN tunnel health.

Monitoring > Site Health

GET

/network-monitoring/v1/sites-health

This API is used to fetch a list of health information for each site, including devices, clients, critical alerts with count, along with their respective health and health reasons.

GET

/network-monitoring/v1/site-health/{site-id}

This API is used to fetch detailed health information for the requested site.

To get the site-id value use the GET /network-monitoring/v1/sites-health using the siteName filter.

GET

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

This API is used to fetch a list of sites with the number of poor, fair, and good performing devices for each site.

GET

/network-monitoring/v1/tenant-device-health

This API is used to fetch a health overview of devices categorized as poor, fair, or good performing, for each device type (e.g. Switches, Gateways, Access Points) under the customer.

GET

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

This API is used to fetch a list of sites with the number of poor, fair, and good health clients that are categorized as wired and wireless for each site.

GET

/network-monitoring/v1/tenant-client-health

This API is used to fetch a health overview of connected clients - categorized as poor, fair, or good performing, for each client type (e.g. Wired, Wireless) under the customer.

Monitoring > Switch

GET

/network-monitoring/v1/switch/topn-interface-trends

This API is used to fetch the Top-N switch interface trend details over a specified time period for a given site within a tenant account.

GET

/network-monitoring/v1/switches

This API is used to fetch a list of switches associated to a customer.

GET

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

This API is used to fetch current switch information for the specified serial number or stack ID.

GET

/network-monitoring/v1/stack/{serial-number}/members

This API is used to fetch current stack member details for the specified stack-id or conductor serial.

GET

/network-monitoring/v1/switches/{serial-number}/hardware-categories

This API is used to fetch detailed hardware information associated with the specified serial number or stack ID.

GET

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

This API is used to fetch a summary of link aggregation group (LAG) details for the specified serial number or stack ID.

GET

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

This API is used to fetch a list of interfaces for the specified serial number or stack ID.

GET

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

This API is used to fetch a list of VLANs for the specified serial number or stack ID.

GET

/network-monitoring/v1/switches/topn-interface-trends

This API is used to fetch top N Switches interface trends, rx bytes, tx bytes over a given time period.

GET

/network-monitoring/v1/switches/{serial-number}/interface-trends

This API is used to fetch interface trend data for a given site based on a serial number or stack ID.

GET

/network-monitoring/v1/switches/{serial-number}/hardware-trends

This API is used to fetch hardware trend data for a given site based on a serial number or stack ID.

GET

/network-monitoring/v1/switches/{serial-number}/interface-poe

This API is used to fetch interface PoE detail for a serial or stack ID for a specific site.

Monitoring > Topology

GET

/network-monitoring/v1/topology/{site-id}

This API is used to fetch the topology details for a specific site.

GET

/network-monitoring/v1/unmanaged-device/{mac-address}

This API is used to fetch information related to unmanaged device for a specific site and device mac.

GET

/network-monitoring/v1/isolated-devices/{site-id}

This API is used to fetch information related to isolated devices for a specific site.

GET

/network-monitoring/v1/neighbours/{serial-number}

This API is used to fetch information related to neighbor devices for a specific device serial number.

MSP > MSP

GET

/network-msp/v1/list-tenant

This API is used to fetch a list of tenants for an MSP. Tenants list includes details like tenant name, tenant CID, sites count, devices count with health status, alerts count, etc.

Notifications > Alerts

GET

/network-notifications/v1/alerts

This API is used to fetch a list of Alerts based on the query parameters provided. The alerts list includes details such as name, type, category, severity, status, etc.

Reporting > Reporting

GET, or PUT

/network-reporting/v1/reports

This API is used to fetch or update user reports.

GET

/network-reporting/v1/reports/{report-id}/report-runs

This API is used to fetch report execution history for a specific report ID.

Services > Firmware Management

GET

/network-services/v1/firmware-details

This API is used to fetch a list of device's firmware details such as firmware version, upgrade status, recommended version, firmware classification and last upgraded timestamp.

Services> Location Analytics

GET

/network-services/v1/location-analytics/trends

This API is used to fetch the trends of visitors and passerby for a tenant across all the sites or for a specific site within the given time range.

GET

/network-services/v1/location-analytics/sites/insights

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

Services > Webhooks

GET, or POST

/network-services/v1/webhooks

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

GET, PUT, PATCH, or DELETE

/network-services/v1/webhooks/{id}

This API is 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.

GET

/network-services/v1/webhooks/{id}/rotate-hmac-key

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

Troubleshooting > Events

GET

/network-troubleshooting/v1/events

This API is used to fetch a list of network events.

GET

/network-troubleshooting/v1/event-extra-attributes

This API is used to fetch attributes of the event.

GET

/network-troubleshooting/v1/event-filters

This API is used to fetch available filter options for network events.

New Configuration APIs

Table 2: New Configuration APIs

Method

Path

Description

Services > AirGroup Server

GET

/network-config/v1alpha1/airgroup-servers

This API is used to fetch the list of hosts that can act as AirGroup servers. The server can be restricted to specific role(s) and AP(s). You cannot configure both allowed-roles and disallowed-roles cannot be configured at the same time. One of role must be empty.

Maximum 20 roles can be configured. In APs, a maximum of 50 APs can be configured.

GET, POST, PATCH, or DELETE

/network-config/v1alpha1/airgroup-servers/{mac-address}

These APIs are used to fetch, create, update, or delete the parameters related to the specified AirGroup servers.

Miscellaneous > Overlay WLAN

GET

/network-config/v1alpha1/overlay-wlan

This API is used to fetch the list of all overlay WLAN services configuration.

GET, POST, PATCH, or DELETE

/network-config/v1alpha1/overlay-wlan/{profile}

These APIs are used to fetch, create, update, or delete the parameters related to the specified WLAN SSID profile name or wired-port profile name.

System > Config Assignment

GET

/network-config/v1alpha1/config-assignments

This API is used to configure scope mapping for profiles. Scope mapping defines the context in which a configured profile is applied, based on a combination of scope and device function. A scope specifies the subset of devices in the network infrastructure to which the profile applies. Supported scopes include:

  • Global

  • Site Collection

  • Site

  • Device Collection

  • Device

By using scope mapping, profiles can be applied at varying levels of granularity, from the entire network down to individual devices.

Example: A role profile can be applied at the Site scope (representing a geographical location such as a campus) or at the Device scope of specified devices with a Campus AP device function.

GET, POST, or DELETE

/network-config/v1alpha1/config-assignments/{scope-id}/{device-function}/{profile-type}/{profile-instance}

These APIs are used to fetch, create, or delete the configuration assignment by scope-id, device-function, profile-type, profile-instance.

Config Management > Config Checkpoint

GET

/network-config/v1alpha1/config-checkpoint

This API is used to fetch the configuration elements for configuration checkpoints.

GET, PATCH, or DELETE

/network-config/v1alpha1/config-checkpoint/{name}

These APIs are used to fetch, update, or delete the configurations related to the specified checkpoint.

Config Management > Persona Assignment

POST

/network-config/v1alpha1/persona-assignment/{device-function}

This API is used to create device list to device function mapping.

Config Management > Persona Mapping

GET

/network-config/v1alpha1/device-persona-mapping

This API is used to fetch device type to device function mapping.

GET

/network-config/v1alpha1/device-persona-mapping/{device-type}

This API is used to fetch the list of device type to device function mapping.

Scope Management > Device Groups

GET

/network-config/v1/device-groups

This API is used to fetch the list of device-groups.

Scope Management > Hierarchy

GET

/network-config/v1/hierarchy

This API is used to fetch the hierarchy of the given scopeId and its scopeType.

Scope Management > Site Collections

POST

/network-config/v1/site-collection-add-sites

This API is used to add one or more available sites to existing site-collection.
DELETE

/network-config/v1alpha1/site-collection-remove-sites

This API is used to remove one or more available sites from the existing site collection.
GET /network-config/v1/site-collections This API is used to fetch information about all site collections.
POST /network-config/v1/site-collections This API is used to create site collection with or without sites associated. To create empty site-collection (without any site associated) do not pass siteIds list.
PUT /network-config/v1/site-collections This API is used to update the site collection name and description based on the scopeId.

Scope Management > Site
GET /network-config/v1/sites This API is used to fetch information about all sites, based on the query parameters provided. Each site in the returned list includes details like the scopeId, scopeName, collectionId, collectionName, deviceCount, image, the address parameters and geolocation.
POST /network-config/v1/sites This API is used to create site with address, geo coordinates (optional) and image (optional). Image needs to be uploaded first before referencing it here.
PUT /network-config/v1/sites This API is used to update name, address, geo coordinates or image for existing site based on its scopeId. Image needs to be uploaded first before referencing it here.
DELETE /network-config/v1/sites/bulk This API is used to delete one or more existing sites using a bulk delete operation.

Modified APIs

MRT APIs

Table 3: Modified MRT APIs

Method

Description

Monitoring > Access Points

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

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

The response body of the API is updated to include the following access point and radio statistics.

The apStats includes:

  • cpuUtilization—Displays the percentage of CPU utilized by the specified access point.

  • memoryUtilization—Displays the percentage of memory utilized by the specified access point.

    • The radioStats includes:

  • noisefloor—Displays the noise floor data in dBm for each supported band.

  • channelUtilization—Displays the total channel utilization as a percentage for each supported band.

GET /network-monitoring/network-monitoring/v1/aps

 

In the request body siteName, and firmwareVersion parameters are added to the filter list.

Monitoring > Topology

GET /network-monitoring/v1alpha2/neighbours/{serial-number}

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

Monitoring > Gateways

GET /network-monitoring/v1alpha1/gateways/{serial-number}/lan-tunnels/{tunnel-name}/throughput-trends

GET /network-monitoring/v1alpha1/gateways/{serial-number}/wan-tunnels/{tunnel-name}/throughput-trends

Instead of fetching the LAN tunnels and WAN tunnels responses separately, the following API fetches both sets of information using a single API.

GET /network-monitoring/v1/gateways/{serial-number}/tunnels/{tunnel-name}/throughput-trends

GET /network-monitoring/v1alpha1/gateways/{serial-number}/lan-tunnels/{tunnel-name}/status-trends

GET /network-monitoring/v1alpha1/gateways/{serial-number}/wan-tunnels/{tunnel-name}/status-trends

Instead of fetching the LAN tunnels and WAN tunnels responses separately, the following API fetches both sets of information using a single API.

GET /network-monitoring/v1/gateways/{serial-number}/tunnels/{tunnel-name}/status-trends

GET /network-monitoring/v1alpha1/gateways/{serial-number}/wan-tunnels/{tunnel-name}/packets-trends

GET /network-monitoring/v1alpha1/gateways/{serial-number}/lan-tunnels/{tunnel-name}/packets-trends

Instead of fetching the LAN tunnels and WAN tunnels responses separately, the following API fetches both sets of information using a single API.

GET /network-monitoring/v1/gateways/{serial-number}/tunnels/{tunnel-name}/packets-trends

GET /network-monitoring/v1alpha1/gateways/{serial-number}/lan-tunnels/{tunnel-name}/aggregated-usage

GET /network-monitoring/v1alpha1/gateways/{serial-number}/wan-tunnels/{tunnel-name}/aggregated-usage

Instead of fetching the LAN tunnels and WAN tunnels responses separately, the following API fetches both sets of information using a single API.

GET /network-monitoring/v1/gateways/{serial-number}/tunnels

GET /network-monitoring/v1/gateways/{serial-number}/tunnels/{tunnel-name}

GET /network-monitoring/v1alpha1/gateways/{serial-number}/uplinks/{link-tag}/aggregated-usage

 

Instead of fetching aggregated data, the following v1 API is used to fetch per-uplink information.

GET /network-monitoring/v1/gateways/{serial-number}/uplinks

GET /network-monitoring/v1/gateways/{serial-number}/uplinks/{link-tag}

GET /network-monitoring/v1alpha1/gateways/{serial-number}/ports/{port-number}/aggregated-usage

Instead of fetching aggregated data, the following v1 API is used to fetch per-port information.

GET /network-monitoring/v1/gateways/{serial-number}/ports

GET /network-monitoring/v1/gateways/{serial-number}/ports/{port-number}

Deprecated APIs

Table 4: Deprecated APIs

Deprecated API

Alternate APIs

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

Monitoring > Clients

The API path has been updated as part of the v1 release.

GET /network-monitoring/v1/clients/usage/topn

GET /network-monitoring/v1/clients-topn-usage

GET /network-monitoring/v1/clients/trends

GET /network-monitoring/v1/clients-trend

Removed APIs

Table 5: Removed APIs

Removed APIs

Alternate APIs

Monitoring > Gateways

GET /network-monitoring/v1alpha1/clusters/{cluster-name}/leader

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

Troubleshooting > AOS-S Switches

POST /network-troubleshooting/v1alpha1/aos-s/{serial-number}/showCommand

POST /network-troubleshooting/v1alpha1/aos-s/{serial-number}/showCommands

GET /network-troubleshooting/v1alpha1/aos-s/{serial-number}/showCommand/async-operations/{task-id}

GET /network-troubleshooting/v1alpha1/aos-s/{serial-number}/showCommands/async-operations/{task-id}

Troubleshooting > Access Points

POST /network-troubleshooting/v1alpha1/aps/{serial-number}/showCommand

POST /network-troubleshooting/v1alpha1/aps/{serial-number}/showCommands

GET /network-troubleshooting/v1alpha1/aps/{serial-number}/showCommand/async-operations/{task-id

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

Troubleshooting > CX Switches

POST /network-troubleshooting/v1alpha1/cx/{serial-number}/showCommand

POST /network-troubleshooting/v1alpha1/cx/{serial-number}/showCommands

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

GET /network-troubleshooting/v1alpha1/cx/{serial-number}/showCommands/async-operations/{task-id}

Troubleshooting > Gateways

POST /network-troubleshooting/v1alpha1/gateways/{serial-number}/showCommand

POST /network-troubleshooting/v1alpha1/gateways/{serial-number}/showCommands

GET /network-troubleshooting/v1alpha1/gateways/{serial-number}/showCommand/async-operations/{task-id

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