API Change Log in April 2025

Monitoring > Access Points

This API is used to fetch information about the throughput trend data of an access point. The response includes the amount of data transmitted and received in bits per second for during a given period. If no timestamp range is specified in the filter, data for the last 3 hours will be returned by default.

This API is used to fetch a list of radios associated with a customer. Each radio in the returned list includes details such as serial number, device name, MAC address, band, status, and current statistics.

This API is used to fetch information about radio channel utilization that includes transmitting, receiving (rx), and Non-Wi-Fi interference utilization percentage. The API provides insights into how effectively radio channels are utilized.

This API is used to fetch information about channel quality for a radio, identified by radio numbers over a specified time period.

This API is used to fetch information about noise floor for a radio, identified by radio numbers over a specified time period.

This API is used to fetch information about the transmission trends of drops, and retries frames.

This API is used to fetch information about the CPU utilization of an AP for the time range specified in the startTime and endTime parameter.

This API is used to fetch information about the memory utilization of an AP for the time range specified in the startTime and endTime parameter.

This API is used to fetch information about power consumption trend data for a specified access point. The data is obtained based on the timestamp range provided in the filter. If no timestamp range is specified in the filter, data for the last 3 hours will be returned by default.

This API is used to fetch information about frame trends of a specific access point port that is linked to a particular site. It provides key metrics such as errors, drops, error percentage, and drop percentage, for a given port index.

This API is used to fetch information about Cyclic Redundancy Check (CRC) frame trends of a specific access point port that is linked to a particular site. It provides key metrics such as CRC errors and percentage for a given port index.

This API is used to fetch information about collision data frame trends of a specific access point port that is linked to a particular site. It provides key metrics such as collision errors and percentage for a given port index.

This API is used to fetch information about throughput trend data for the specific access point, including transmitted(tx) and received(rx) data in bits per second. If no timestamp range is specified in the filter, data for the last 3 hours will be returned by default.

This API is used to fetch information about the throughput trend data for a specific radio of an access point, including transmitted and received data in bits per second. If no timestamp range is specified in the filter, data for the last 3 hours will be returned by default.

This API is used to fetch information about throughput trend data for a specific port of an access point, including transmitted and received data in bits per second. If no timestamp range is specified in the filter, data for the last 3 hours will be returned by default.

This API is used to fetch information about throughput trend data for a specific WLAN of an access point, including transmitted and received data in bits per second. If no timestamp range is specified in the filter, data for the last 3 hours will be returned by default.

Monitoring > IDPS

Monitoring > Site Health

This API is used to fetch information about the list of sites. The response includes information such as site-id's, health of the site, and overview of device, client and alerts-related to the specific site is displayed.

This API is used to fetch information about a specific site health.

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

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

Monitoring > Gateways

This API is used to fetch the list of VLANs configured in the specified gateway.

This API is used to fetch information about a specific VLAN configured in a specified gateway.

This API is used to fetch a list of wired interfaces present in the specified gateway based on the query parameters provided.

This API is used to fetch information about the tunnel configured in a specific gateway.

This API is used to fetch the list of tunnels present in a specified cluster based on the query parameters provided.

This API is used to fetch the list of gateway members present in the specified cluster based on the query parameters provided.

This API is used to fetch about the leader of gateway cluster. It provides gateway-related details such as MAC address, name, status, software Version, etc.

This API is used to fetch information on VLANs categorized as good or poor, either for the entire cluster or for individual gateways within the cluster.

This API is used to fetch information about the gateways in a cluster, including their peers and any VLAN mismatches.

Reporting > Reporting

This API is used to check the health status of the network reporting service.

This API is used to fetch a list of user reports, based on the query parameters provided.

This API is used to create reports based on various filters, report periods, and scheduling options. The reports can be scheduled for one-time or recurring execution and sent via email in multiple formats.

These APIs are used to update or delete a user report with report-id. Report ID can be obtained by executing the GET /network-reporting/v1alpha1/reports (List Reports) API call.

This API is used to fetch a list of report run using the report ID. A report run includes details such as its report run ID, status, export information, start timestamp, and end timestamp.

This API is used to delete a specific report run with the report ID.