Findings from live testing on a Cloud Key Gen2 Plus running Network 11.0.81 (October 2026). They may differ on other versions. Where a finding explains a design choice in a tool, it says so.
rememberMe flag: false is 2 hours,
true is 30 days. The server uses false and logs in again once on a 401.x-updated-csrf-token if it ever changes.403).423 Locked while the file is being built; poll until it returns 200 (about 90 s).batch-delete route with a JSON array of ids (204), not a DELETE.wan2 interface of a one-WAN site,
or MAC addresses it has never seen in a client group), so the tools validate more strictly than the console.firewall-app-blocks. Every write is a POST of the complete array: an entry without
_id is created, one with its _id is updated, one left out is deleted, and [] deletes everything. The UI sends one request
for all the changes made before Apply, so the tool does too.[] for the lists that do not apply.ALWAYS, EVERY_DAY, EVERY_WEEK, ONE_TIME_ONLY, CUSTOM. All-day shapes for daily and one-time
schedules, a network block for specific applications, and the mapping from application ids to the DPI lists are not verified.simple_app_block firewall policy for each block (origin_id is the block’s _id); the tool checks for it
after applying.scripts/app_block_live_check.py (dry run and --run, all checks passed): create, schedule change,
rename, category switch, several changes in one request, rollback replay, and restoring the original set exactly. The items above
marked not verified are still open.POST cmd/devmgr with the device MAC (set-locate, unset-locate, restart with
reboot_type: "hard", adopt with client: "web"). There is no soft reset. Remove is POST cmd/sitemgr with a list of MACs
and cmd: "delete-device".PUT rest/device/{_id} with the device _id, not the MAC. Partial bodies are
accepted: {"disabled": true}, or {"name": ..., "mgmt_network_id": ...}, changed the device without the rest of the form.
The _id changes after a remove and re-adopt, so the tool always reads it live.POST cmd/devmgr with
cmd: "upgrade-external", the device MAC and the image url. Revert takes the URL from fw-revert-options
(previous_firmware_url). The console answers rc: ok with empty data as soon as the upgrade starts.scripts/device_live_check.py on a small switch with two clients: locate on and off, rename and back
(a partial PUT carrying only the name), LED override off and back, disable then enable (the device reconnected), and a hard
restart (seen leaving and returning). Remove and adopt have also been run live (as two separate runs on the same switch) and
passed. Removing a device drops its saved settings, so the script snapshots them first and restores the name, LED, SNMP and STP
priority after adopt. A re-adopted switch comes back on a dynamic management address, not its previous static one; the
script lists that, and the per-port settings, as not restored.object-oriented-network-config resource. QoS limits are stored in kbit/s.Invalid QoS rule objective, HTTP 400). The
traffic object tool switches both off when the mode becomes PRIORITIZE and refuses to set one in that mode.qos-rules). An update must send the whole rule including _id and
index; bursts are OFF, SHORT or LONG; the console drops port_matching_type from a client source but keeps
it on an application destination, so the tool does not send it on the source.cloudflare and google and clears the custom list. A custom entry is a DNS stamp.dhcpd_dns_1 to dhcpd_dns_4.batch-reorder; deletion uses batch-delete._id, but system-defined ones have a composite id: the
source zone UUID, the destination zone UUID and the index run together (2147483647 for the default block,
30000 and up for system allow rules). Fetching one policy by id works only for custom policies; a composite id
returns 404 (checked November 2026). Read system policies from the list instead.name without display_name.Enabled QoS or traffic objects on real traffic; overlapping enabled QoS rules; firewall policies on real zone pairs;
switch storm-control units; WAN identity changes; data retention writes on consoles not in manual mode.
Site Manager (api.ui.com) operations are built from the official v1.0.0 spec and tested against a fake, not yet
against the live service.