Skip to main content

Dash HTTP API

Base path:

/api

Error format:

{ "code": "<string>", "message": "<string>" }

Request Conventions​

  • All /api responses, including authentication and routing errors, carry Cache-Control: no-store. The API body limit is 24 MiB, with smaller limits on some endpoints; size limits apply when a body is read.
  • Method names are case-sensitive. Dash implements GET, HEAD, POST, PUT, PATCH, and DELETE. Other methods, including OPTIONS and lowercase get, return 501 not_implemented. Implemented methods return 404 not_found for unknown paths or 405 method_not_allowed with Allow when an existing endpoint does not accept the method. GET APIs do not imply HEAD.
  • /api/version/ and admin module roots listed below also accept their forms without a trailing slash, without redirects. Node-ID PATCH and DELETE paths also accept trailing slashes; other endpoints do not automatically gain aliases.
  • JSON requests require a valid application/json media type; valid parameters are allowed. Invalid media types or parameters return 415 unsupported_media_type.
  • JSON field names are case-sensitive. Unknown fields are ignored unless an endpoint specifies stricter validation. Duplicate object keys and invalid UTF-8 are rejected. Clients must not depend on response whitespace, object-key order, or HTML-character escaping.
  • Node metrics must finish persistence within 5 seconds of server receipt. Authentication, body reading, and node-lock waits consume that budget. Expired reports return 503 service_unavailable without persisting metrics.

Authentication​

MethodUse
Admin passwordPOST /api/auth/login
refresh cookie + X-CSRF-TokenPOST /api/auth/refresh, POST /api/auth/logout
Authorization: Bearer <access_token>Admin APIs and optionally authenticated reads
X-Node-SecretNode reporting, node identity reads, and deploy asset downloads
upgrade_token queryTemporary deploy asset download grant issued only for legacy Node upgrades

Public and Optional Auth​

MethodPathAuthDescription
GET/api/version/NoneDash and bundled node version
GET/api/front/brandOptional BearerBrand info
GET/api/front/metricsOptional BearerCurrent front metrics
GET/api/front/groupsOptional BearerFront groups
GET/api/metrics/onlineOptional BearerOnline rate
GET/api/metrics/uptimeOptional BearerUptime for the latest 45 calendar days
GET/api/metrics/uptime/dayOptional Bearer24 hourly rates for one calendar day
GET/api/metrics/historyOptional BearerHistory metrics
GET/api/statistics/accessOptional BearerAnonymous access settings
GET/api/statistics/traffic/settingsOptional BearerTraffic settings
GET/api/statistics/traffic/ifacesOptional BearerNode interface list
GET/api/statistics/traffic/summaryOptional BearerCurrent billing cycle traffic
GET/api/statistics/traffic/dailyOptional BearerDaily traffic, requires billing mode
GET/api/statistics/traffic/monthlyOptional BearerMonthly traffic

Optional Bearer endpoints treat invalid Bearer tokens as anonymous requests.

GET /api/statistics/traffic/ifaces?server_id=<id> returns interface names previously reported by the node. Results are ordered by latest sample time, with actively reporting interfaces first; equal timestamps are ordered by interface name. Historical interfaces remain listed for querying older traffic data.

Node Uptime​

  • GET /api/metrics/uptime (also with a trailing slash) returns {enabled, timezone, generated_at, warning_sla, error_sla, nodes}. Each node has a string server_id and 45 days, oldest first including today. Each day has date (YYYY-MM-DD), percent (0–100 or null), and observed_ms (observed milliseconds). Dates follow app.timezone, or the server's local timezone when unset. All dates are present even when no observations exist.
  • Authenticated callers receive all non-deleted nodes. Guests receive only guest-visible nodes when uptime_guest_visible is enabled; otherwise the daily endpoint returns 200 with enabled: false and an empty node list. SLA thresholds come from system settings and do not affect sampling.
  • GET /api/metrics/uptime/day?server_id=<id>&date=YYYY-MM-DD (also /day/) returns {date, hours, observed_ms}. Both arrays have 24 entries indexed by local clock hour. Missing or future hours have a null percentage and zero observed milliseconds. On a daylight-saving transition, a skipped hour is unknown and repeated clock hours combine their durations. Disabled guest access returns 403 forbidden; hidden, deleted, and absent nodes return 404 not_found to guests. Invalid IDs or dates outside the same 45-day window return 400 invalid_request; database failures return 503 service_unavailable.
  • Percentages are 100 × online milliseconds / observed milliseconds, weighted by duration. A report covers the interval from its server receive time until app.node_offline_threshold later; overlapping intervals count once. The first current-metrics row starts the node's observation window. Only completed minutes are included, normally finalized six seconds after each minute boundary; current-day and current-hour values can lag by about one minute plus that delay. Missing minutes are unknown and excluded from the denominator. A percentage is not proof of complete coverage; observed_ms reports how much was observed. The existing /api/metrics/online retains its previous contract and data source.
  • The dashboard refreshes daily uptime independently every 60 seconds, and loads hour details only for an expanded day. Disabling guest access hides uptime; logging out discards authenticated uptime state.

Auth Sessions​

POST /api/auth/login request bodies must include password and persistence. persistence allows session or persistent. Successful responses include access_token, expires_at, and csrf_token, and set refresh/CSRF cookies. Malformed login JSON returns 400 invalid_json, invalid persistence returns 400 invalid_persistence, and login rate limiting returns 429 rate_limited.

MethodPathAuthSuccess
POST/api/auth/loginAdmin password200
POST/api/auth/refreshrefresh cookie + X-CSRF-Token200
POST/api/auth/logoutrefresh cookie + X-CSRF-Token204
GET/api/auth/sessions/Bearer200
DELETE/api/auth/sessions/currentBearer204
DELETE/api/auth/sessions/Bearer204
DELETE/api/auth/sessions/{sid}Bearer204

GET /api/auth/sessions/ returns { "sessions": [...] } for the bearer token user. Each item includes id, expires_at, session_only, and current.

Node Endpoints​

MethodPathAuthBodySuccess
POST/api/node/identityX-Node-Secret{}200
POST/api/node/metricsX-Node-SecretNodeReport200
POST/api/node/staticX-Node-SecretStatic200

Successful /api/node/metrics response:

{
"ok": true,
"update": null
}

Or:

{
"ok": true,
"update": {
"id": "release-id",
"version": "1.2.3",
"url": "https://dash.example.com/deploy/windows/node_windows_amd64.exe?upgrade_token=...",
"sha256": "...",
"size": 12345678
}
}

url may include a short-lived upgrade_token so legacy Nodes can download the exact update asset without sending X-Node-Secret. Clients must use the returned URL unchanged.

Pending upgrade tasks are volatile and clear when Node reports the exact target version or a higher SemVer precedence. Different build metadata at the same SemVer precedence is treated as a distinct Node binary and can still be delivered.

Admin: Groups​

MethodPathBodySuccess
GET/api/admin/groups/None200
GET/api/admin/groups/mapNone200
POST/api/admin/groups/{ "name": "...", "remark": "..." }204
PATCH/api/admin/groups/{id}{ "name": "...", "remark": "..." }204
DELETE/api/admin/groups/{id}None204

Group name is trimmed, contains 1–64 Unicode characters, and cannot contain control characters. remark is trimmed, limited to 255 Unicode characters, and cannot contain control characters.

Admin: Nodes​

MethodPathBodySuccess
GET/api/admin/nodes/None200
GET/api/admin/nodes/deployNone200
POST/api/admin/nodes/None204
PUT/api/admin/nodes/display-orderNode ID order204
PATCH/api/admin/nodes/traffic-p95{ "ids": [1, 2], "enabled": true }204
PATCH/api/admin/nodes/{id}Node patch204
POST/api/admin/nodes/{id}/upgradeNone204
GET/api/admin/nodes/traffic/rebuildNone200
POST/api/admin/nodes/{id}/traffic/rebuildNone202
DELETE/api/admin/nodes/{id}None204

Node patch fields:

{
"name": "node-a",
"is_guest_visible": true,
"traffic_p95_enabled": true,
"traffic_cycle_mode": "calendar_month",
"traffic_billing_start_day": 1,
"traffic_billing_anchor_date": "",
"traffic_billing_timezone": "Asia/Shanghai",
"traffic_direction_mode": "default",
"display_order": 1,
"tags": ["prod", "hk"],
"secret": "new-secret",
"group_ids": [1, 2]
}

Node names are trimmed, contain 1–64 Unicode characters, and cannot contain control characters. tags allows at most 32 items; each trimmed item is limited to 64 Unicode characters and cannot contain control characters. Empty and duplicate values are removed.

When reading stored tags, Dash logs a warning and drops invalid or excess items. Unparseable stored JSON becomes an empty tag list without dropping the node's other metrics from the frontend projection.

After trimming, secret must contain 8–128 Unicode characters. Invalid values return 400 invalid_secret; a value owned by another node returns 409 duplicate_secret.

Node billing cycle fields are atomic. If any cycle field is submitted, the request must include traffic_cycle_mode and every field required by that mode. Stored modes are calendar_month, whmcs_compatible, and clamp_to_month_end. Legacy default is accepted only without other cycle fields and is stored as an explicit calendar month.

traffic_direction_mode allows default, out, both, and max. default inherits the global direction mode; other values override that node.

/api/admin/nodes/traffic-p95 accepts ids and enabled. enabled is required. ids must be a non-empty positive integer array, cannot contain duplicates, and can contain at most 10000 items. The command validates all node IDs first, then updates them in one transaction. Success returns 204; any missing or deleted node returns 404 not_found, and no node is updated.

GET /api/admin/nodes/traffic/rebuild returns the latest process-local rebuild task state. Before any task exists it returns status=idle; running responses include server_id, running=true, and started_at; finished responses may return completed or failed until replaced by the next task. This state is not durable across process restarts. Failed states expose stable code and error values, not internal error strings.

POST /api/admin/nodes/{id}/traffic/rebuild is Billing-only. It rewrites 5-minute facts in 6-hour chunks and invalidates overlapping snapshots. Lite mode returns 409 traffic_rebuild_requires_billing; a running task returns 409 traffic_rebuild_running; unavailable execution returns 503 traffic_rebuild_unavailable. Switching to Lite lets the current chunk finish, then stops the job.

GET /api/admin/nodes/ field version.supports_auto_update shows whether the current node version meets the Dash admin console automatic update delivery requirement. The minimum version is 0.2.3.

POST /api/admin/nodes/{id}/upgrade requires version.supports_auto_update=true. Current node versions below 0.2.3 return 409 node_upgrade_unsupported; unavailable bundled versions, platforms, or assets return 409; failure to prepare the legacy temporary download grant returns 503 node_upgrade_grant_error.

Admin: Traffic Settings​

MethodPathBodySuccess
PATCH/api/statistics/traffic/settingsPartial fields204

Fields are documented in Traffic Accounting and Billing Cycles.

Only guest_access_mode, usage_mode, and direction_mode are writable. Sending a global billing-cycle field returns 400 billing_cycle_is_per_node.

Traffic Queries​

  • GET /api/statistics/traffic/daily requires usage_mode=billing; otherwise it returns 409 traffic_daily_requires_billing. period allows current or previous; omitted means current.
  • GET /api/statistics/traffic/monthly supports months in 1..24 and period=current|previous.
  • Traffic queries use each node's explicit billing cycle. Only traffic_direction_mode=default inherits the global direction.
  • Traffic summary, daily, and monthly responses keep raw in_* and out_* fields. The active accounting view is exposed through selected_bytes, selected_p95_bytes_per_sec, selected_peak_bytes_per_sec, and selected direction fields.
  • Clients use data_complete, coverage_ratio, gap_count, and reset_count. The deprecated partial field has been removed.

History Metrics​

GET /api/front/metrics node objects can include node.tags, disk.smart, disk.temperature_devices[], top-level thermal, and top-level pressure. SMART, thermal, and pressure runtime payloads are cached separately from the front node snapshot and are reattached only when received_at matches.

GET /api/metrics/history supports temperature metrics:

MetricSourceDevice parameter
cpu.temp_cMaximum CPU thermal sensor temperatureNot required
disk.temp_cSMART physical disk temperature historyOptional; omitting it aggregates physical-disk rows

For disk.temp_c, device can match physical disk name, ref, or path.

Disk temperature history is written only for backend-confirmed physical disks. Virtual disks and RAID devices are not persisted as disk.temp_c.

GET /api/metrics/history also supports PSI average metrics:

  • pressure.cpu.some_avg10, pressure.cpu.some_avg60, pressure.cpu.some_avg300
  • pressure.memory.some_avg10, pressure.memory.some_avg60, pressure.memory.some_avg300
  • pressure.memory.full_avg10, pressure.memory.full_avg60, pressure.memory.full_avg300
  • pressure.io.some_avg10, pressure.io.some_avg60, pressure.io.some_avg300
  • pressure.io.full_avg10, pressure.io.full_avg60, pressure.io.full_avg300

History ranges select a fixed data source while HTTP parameters, response fields, point counts, and ordering remain unchanged:

rangeSourcePoint interval
30m, 1h, 12h, 24hRaw samples3 seconds, 6 seconds, 60 seconds, 120 seconds
1w15-minute aggregate15 minutes
15dWeighted re-aggregation of 15-minute data30 minutes
30dOne-hour aggregateOne hour

Temperature and exposed PSI averages use the same aggregate model as other regular metrics. Aggregate queries include the latest raw samples. Exact sample points remain available during the configured raw retention period, which defaults to eight days. Fifteen-minute and one-hour aggregate results remain available for 16 and 32 days, respectively.

Admin: Alerts​

MethodPathDescription
GET/api/admin/alerts/rules/List rules
POST/api/admin/alerts/rules/Create rule
PATCH/api/admin/alerts/rules/{id}Update rule
DELETE/api/admin/alerts/rules/{id}Delete rule
GET/api/admin/alerts/mounts/List mounts
PUT/api/admin/alerts/mounts/Set mounts
GET/api/admin/alerts/settings/Read global settings
PUT/api/admin/alerts/settings/Replace global settings
GET/api/admin/alerts/events/List alert records
GET/api/admin/alerts/events/summaryList open alert summaries
GET/api/admin/alerts/events/serversList alert-record filter nodes
GET/api/admin/alerts/channels/List channels
POST/api/admin/alerts/channels/Create channel
GET/api/admin/alerts/channels/{id}Read channel
PUT/api/admin/alerts/channels/{id}Replace channel
PUT/api/admin/alerts/channels/{id}/enabledToggle enabled
POST/api/admin/alerts/channels/{id}/testSend test notification
DELETE/api/admin/alerts/channels/{id}Delete channel
POST/api/admin/alerts/channels/telegram/mtproto/codeStart MTProto login and send a code
POST/api/admin/alerts/channels/telegram/mtproto/verifyVerify the login code
POST/api/admin/alerts/channels/telegram/mtproto/passwordSubmit the two-step verification password
POST/api/admin/alerts/channels/telegram/mtproto/pingCheck the stored MTProto session

GET /api/admin/alerts/events/ supports server_id, status=open|closed|all, metric, from, to, cursor, and limit. from and to use RFC3339. limit defaults to 200 and is capped at 500. The default status is open.

Alert record responses include items, next_cursor, and has_more. Each item includes node, rule, metric, status, first trigger time, last trigger time, close time, current value, effective threshold, and close reason.

Channel reads include delivery health, retry/probe times, and pending/blocked counts. Invalid stored channels remain visible with config=null and can only be deleted. MTProto login-state failures return 503 login_state_error; concurrent revision changes return 409 channel_changed.

Admin: System​

MethodPathDescription
GET/api/admin/system/settings/Read system settings
PUT/api/admin/system/settings/Replace system settings
PATCH/api/admin/system/settings/Partial update
GET/api/admin/system/dash-update/statusRead Dash updater status
GET/api/admin/system/dash-update/checkCheck Dash updates
POST/api/admin/system/dash-update/runStart a Dash update task
GET/api/admin/system/dash-update/release-notesRead Release Notes HTML
GET/api/admin/system/themes/List themes
POST/api/admin/system/themes/uploadUpload theme zip
POST/api/admin/system/themes/{id}/applyApply theme
DELETE/api/admin/system/themes/{id}Delete theme

System settings include history_guest_access_mode, dash_update_channel, dash_update_mode, logo_url, page_title, topbar_text, uptime_guest_visible, uptime_warning_sla, and uptime_error_sla. PATCH accepts partial updates. PUT requires the first six fields.

uptime_guest_visible defaults to true. Warning and error thresholds default to 99 and 95, allow decimals, and must satisfy 0 <= error < warning <= 100. Omitted or null uptime fields retain their previous values in both PATCH and PUT. Invalid thresholds return 400 invalid_fields and roll back the whole update. These settings control access and presentation without changing sampling.

New logo_url values accept same-origin absolute paths, supported base64 image data URLs, or external HTTPS URLs. Stored external HTTP logos remain readable; a PATCH for other fields does not revalidate an omitted logo.

dash_update_channel allows release or prerelease. dash_update_mode allows manual, notify, or auto.

GET /api/admin/system/dash-update/check returns the target version and opaque install_revision. POST /run accepts action=update|reinstall, channel, lang, and the immutable plan fields from the check response. A stale plan finishes with failure_code=install_changed and never selects another target.

Update jobs and transactions persist under $DASH_HOME/runtime/dash-update. failure_code=recovery_required requires root to run dash update recover.

PVE Access​

System settings (GET, PATCH, and PUT /api/admin/system/settings) include pve_guest_visible, a boolean defaulting to false. Omitted or null values preserve the current setting in PATCH and PUT; explicit false disables guest access.

GET /api/virt/{id} and GET /api/virt/{id}/vms/{vmid}/history share the same access policy:

  • Administrators use a valid Bearer token and are not restricted by the guest switch.
  • Guests can view VM names, IPs, snapshots, and history only when the switch is enabled and the host is guest-visible. A disabled switch returns 403 forbidden; with it enabled, hidden, missing, or deleted hosts return 404 not_found.
  • Access-setting or visibility lookup failures return 503 virt_unavailable. Responses use Cache-Control: no-store.

Virtual machine snapshots​

  • POST /api/node/virt authenticates with X-Node-Secret; the key determines the owning host. Its JSON body limit is 4 MiB. Success returns 204 without an update manifest.
  • GET /api/virt/{id} returns { "snapshot": ..., "received_at": ..., "stale": false } plus the chart settings below. Without a snapshot, the first two fields are null and stale is true.
  • The pve boolean in GET /api/admin/nodes/deploy indicates whether the package contains verified PVE helpers matching the Node version. When true, the admin console offers a PVE deployment option that copies the Linux command with --pve; scripts still contains only linux, macos, and windows. See PVE Monitoring for installation.

The report and returned snapshot have the same shape:

{
"schema": 1,
"provider": "pve",
"host": "pve-a",
"collected_at": "2026-09-28T10:00:00Z",
"last_success_at": "2026-09-28T10:00:00Z",
"ttl_seconds": 90,
"status": "ok",
"vms": [{"id": 100, "name": "guest", "status": "running", "template": false, "collected_at": "2026-09-28T10:00:00Z", "ttl_seconds": 90, "cpus": 2, "cpu_ratio": 0.25}]
}

status is ok or error. On success, last_success_at is the latest successful inventory read time and may precede the snapshot assembly time, collected_at; vms: [] means a successful empty inventory. Failures require error and may retain the last successful inventory and time; without an earlier sample, vms: null is allowed.

VM Fields​

Required fields are id, name, status, and template. The following fields are optional; missing values mean unknown:

FieldMeaning
qmp_statusQEMU state, including paused states
cpus, cpu_ratiovCPU count and CPU usage ratio; the ratio uses consecutive /proc process counter deltas divided by elapsed time and vCPU count. The first sample is unknown
memory_bytes, memory_limit_bytesMemory usage and limit; usage is cgroup usage minus file cache, or guest total minus free memory when balloon data is available
disk_capacity_bytesPVE maxdisk from a low-frequency query, not guest filesystem usage
disk_read_bytes, disk_write_bytes, net_in_bytes, net_out_bytesCumulative disk and network bytes
uptime_secondsUptime in seconds
net_rate_limits_mbps, ipsNIC rate limits and IPs, described below

The inventory includes stopped VMs and excludes templates. Dynamic metrics and IPs require QMP status running.

Optional collected_at and ttl_seconds record the VM's observation time and lifetime (90 seconds in the helper), independently of the enclosing snapshot. Missing observation metadata means live metrics are unknown. On expiry, the helper and Dash omit CPU, memory usage, disk/network counters, and uptime, and set the state to unknown. The original observation time and configuration remain; IP freshness is evaluated separately.

NIC Rate Limits and IPs​

net_rate_limits_mbps maps NIC names (such as net0) to JSON numbers in Mbps (1 Mbps = 1,000,000 bit/s), rounded to two decimal places. PVE rate is converted from MiB/s: 12.5 becomes 104.86. Each value applies separately to that NIC's receive and transmit directions. Zero means no configured limit; an absent field means NIC configuration was not collected.

The helper reads the current configuration in /etc/pve/qemu-server/<vmid>.conf, ignoring pending changes and saved snapshots. Invalid rate values are logged and omit this field; basic metrics reporting continues.

Optional ips contains up to 1024 unique IPv4/IPv6 addresses, including private addresses and excluding loopback, link-local, unspecified, multicast, and invalid addresses. IPs come from the running VM's Guest Agent. See PVE Monitoring for collection intervals and backoff.

ips_collected_at and ips_ttl_seconds describe IP freshness independently of snapshot stale. The helper uses a 900-second TTL. Failed queries may reuse an unexpired sample with its original time; expired samples and samples known to predate the VM's current boot are omitted. A successful empty query may have a timestamp and TTL without ips.

These two fields may be omitted, leaving IP freshness unknown. When provided, the timestamp must be nonzero and no later than the enclosing snapshot's collected_at, but may be later than the VM's collected_at. TTL must be 1–3600 seconds.

Report Limits and Caching​

Limits: 4096 unique VM IDs; 255-byte names and host names; 64-byte state strings; 1024-byte errors. Counters must be nonnegative signed 64-bit integers; ttl_seconds must be 1–3600 seconds; collection time may be at most 5 minutes ahead of the server.

Invalid JSON or data returns 400 invalid_virt; oversized bodies return 413 body_too_large; invalid secrets return 401 unauthorized, with failed authentication rate limited by IP. Snapshot update failures return 503 virt_unavailable.

Dash caches the latest snapshot per host in Redis, or in process memory with --no-redis, for 10 minutes from receipt. Duplicate or older reports return 204 without replacing the snapshot or refreshing its receipt time. Reports collected more than 10 minutes ago also return 204 and are not cached.

stale uses the successful sample time, receipt time, and reported ttl_seconds; it can become true before cache removal. Cache expiry or a memory-mode restart returns an empty snapshot. Restarting Dash does not extend Redis cache expiry. Redis read/write failures return 503 virt_unavailable without an in-memory fallback.

VM data does not create nodes, refresh host uptime, or enter host history or traffic statistics. LXC, HA configuration, and VM controls are unsupported.

VM Chart Settings​

The snapshot read endpoint also returns vm_cpu_threshold (integer, default 80), vm_memory_threshold (integer, default 90), and vm_memory_enabled (boolean, default false), including when no snapshot exists. GET /api/admin/nodes returns these persisted node settings plus optional os, platform, and kernel_version for platform identification. PATCH /api/admin/nodes/{id} accepts the three settings; omitted or null fields remain unchanged. Thresholds must be integers from 1 to 100; out-of-range values return 400 invalid_vm_threshold, and invalid field types return 400 invalid_request.

These settings annotate VM history charts without sending notifications; the admin console enables the settings entry only for PVE nodes. CPU thresholds are percentages. Memory annotations must be enabled and use each point's memory_limit_bytes; missing or zero limits are excluded. Annotations count selected AVERAGE/MAX samples strictly above the threshold. Missing values are not zero, and sample counts do not measure continuous exceedance duration.

PVE history queries​

GET /api/virt/{id}/vms/{vmid}/history reads PVE RRD from the connected node. Parameters: timeframe=hour|day|week|month|year (default hour), consolidation=AVERAGE|MAX (default AVERAGE).

Results contain source: "pve_rrd", vm_id, timeframe, consolidation, collected_at, and points. collected_at is the fetch time; each point's timestamp is its sample time. Optional point fields are cpu_ratio, memory_bytes, memory_limit_bytes, disk_read_bytes_per_second, disk_write_bytes_per_second, net_in_bytes_per_second, and net_out_bytes_per_second. Missing values remain unknown. PVE determines historical aggregation and resolution.

History errors: 400 invalid_query/invalid_id, 403 forbidden, 404 not_found (node)/vm_not_found (VM), 429 busy, 501 unsupported, 503 node_offline/virt_unavailable, 504 deadline_exceeded, 502 source_unavailable/invalid_result. Queries require a fresh successful local VM inventory and a running helper service with history support. Dash does not persist VM history or include it in host traffic, uptime or billing.

GET /api/admin/nodes/{id}/virt/capabilities is administrator-only and returns {"connected":true,"pve_history":true,"version":"...","helper_version":"..."} for installation diagnostics; disconnected sessions return false flags. Missing authentication returns 401 unauthorized.