Show the current CV-CUE API session: logged-in key/user, role, customer, timezone and allowed locations, plus the server base URL and version. Good first call to confirm connectivity.

CV-CUE server version, supported API module versions and server health. Use to check whether an endpoint/version is available on this server.

List the CV-CUE location hierarchy (folders and floors) as a flat list with id, type, parentId and full path. Location ids scope most other tools via location_id (data for the whole subtree is returned).

Get one location with its path and direct children.

Create a folder or floor location under a parent. Requires CVCUE_ENABLE_WRITES=true.

Delete a location AND all of its child locations. Irreversible. Requires CVCUE_ENABLE_WRITES=true and confirm=true.

List managed Arista APs (GET /manageddevices/aps) with status, model, firmware, IP, location and client count. Use cvcue_ap_health_summary for fleet-wide rollups and cvcue_get_ap for one AP.

Get full details for one managed AP (radios, wired interfaces, mesh, health) by MAC or name.

Fleet health rollup for managed APs: online/offline counts, breakdown by model, firmware, upgrade/config-push status, plus lists of offline APs and APs with problems (crashes, low power, tunnels down, config errors).

List Wi-Fi radios across managed APs (channel, width, tx power, noise, RF utilization, client count) — the RF view for channel/power analysis.

Reboot one or more managed APs (clients will be disconnected). Requires CVCUE_ENABLE_WRITES=true and confirm=true.

List Wi-Fi clients (GET /clients) with SSID, AP, signal, protocol, data rates, IP, username and OS. Defaults to currently connected clients.

Find a client by MAC, IP, username or device name (active or recently seen). Tries the most specific field first and returns all matches.

Rollup of currently connected clients: totals by SSID, AP, protocol/band, OS, vendor and signal-quality bucket, plus clients with poor performance.

Recent associations for a client (which APs/SSIDs it joined and when).

Force-disconnect (deauthenticate) a wireless client. The client may reconnect. Requires CVCUE_ENABLE_WRITES=true and confirm=true.

List SSID profiles (WLANs): SSID name, enabled, VLAN, security mode, guest, client isolation and where the profile was created. Use cvcue_get_ssid for the full configuration.

Full configuration of one SSID profile (security, network, QoS, firewall, portal...).

Live monitoring data per SSID/WLAN (GET /manageddevices/aps/wlans): which SSIDs are broadcast, on which bands, and how many APs/clients use them.

Delete an SSID profile. Fails if the profile is still referenced by a device template (check GET /deviceconfiguration/ssidprofiles/{templateid}/references). Requires CVCUE_ENABLE_WRITES=true and confirm=true.

Recent CV-CUE events/alerts (WIPS, performance, connectivity, system), newest first, with severity, category, type, summary and timestamps.

Summarize events in a time window: totals by severity, category and type, the most frequent summaries, and the latest high-severity events.

List APs detected by CV-CUE WIPS sensors by classification (rogue, external neighbor, uncategorized, authorized) with SSIDs, vendor, signal and clients.

WIPS overview: number of detected (non-managed) APs per classification, rogue APs with associated clients, top vendors and top SSIDs among rogues.

Key network health metrics for a location and each child location: connectivity success (association/auth/DHCP/DNS failures), performance (latency, retries, coverage, data rate), application experience and infrastructure health — the CV-CUE "Network Health" dashboard.

Client connection event logs reported by APs (association, authentication, DHCP, DNS, roaming...) — defaults to failures in the last 24h.

Consolidated AP/device event logs (reboots, crashes, config, upgrades), newest first.

One-shot client troubleshooting: current client record, recent associations, connection logs, failure events and CV-CUE inferences (root-cause hints) for a client MAC. Sections that fail (e.g. permissions) are reported inline.

List switches discovered via AP uplinks (LLDP): name, vendor, chassis id, number of APs/clients behind each, AP distribution by PoE and link speed.

List wired hosts seen on AP LAN ports (MAC, IP, VLAN, port, auth status, traffic).

List the CV-CUE API modules with operation counts (step 1 of API discovery).

Modules group related resources: session, locations, manageddevices (your APs), aps (all detected APs incl. rogues), clients, configuration (policies), deviceconfiguration (SSID/role/RADIUS profiles, device templates), events, troubleshooting, system, reports, analytics, switches, users, ... Pass a module name as module to cvcue_api_search.

Search CV-CUE API endpoints (step 2 of API discovery).

Matches every word of keyword against path, operationId, summary and description. Use cvcue_api_schema on a result before cvcue_api_execute.

Get parameters, request body and response schema for one endpoint (step 3 of API discovery). Component $refs are inlined up to ref_depth.

Execute ANY CV-CUE API call (step 4 of API discovery).

Paths are relative to the API base URL (…/wifi/api). Most list endpoints page with startindex (0-based offset) + pagesize, and accept locationid to scope results to a location subtree (see cvcue_list_locations).

Examples: GET /system/version GET /manageddevices/aps query_params={"pagesize": 20, "active": true} GET /clients/{macaddress}/associationhistory path_params={"macaddress": "AA:BB:CC:DD:EE:FF"} GET /troubleshooting/clientevents query_params={"fromtime": , "pagesize": 50}

Large responses: many GETs accept fields=[...] for a selective fetch (a field that doesn't support it fails with SELECTIVE_FETCH_OR_UPDATE_NOT_SUPPORTED_FOR_FIELD — drop that field and retry). /deviceconfiguration/devicetemplates is huge unless you pass modelspecific=false. Oversized results are refused with a shape preview.

Secret values (passphrases, RADIUS secrets...) come back as REDACTED. Never send that placeholder back in a write body — omit the field or supply the real value.

Non-GET calls require writes to be enabled for this connection.