Skip to main content

Dash HTTP API

Base path:

/api

Error format:

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

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 agent 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/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.

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.

MethodPathAuthSuccess
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 agents 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 the agent 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

name is trimmed and cannot be empty.

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": "default",
"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]
}

tags must be a string array. Empty and duplicate values are removed.

An empty secret returns 400 invalid_secret; a secret that already belongs to another node returns 409 duplicate_secret.

Node billing cycle override fields are atomic. If any of traffic_cycle_mode, traffic_billing_start_day, traffic_billing_anchor_date, or traffic_billing_timezone is submitted, the request must also include traffic_cycle_mode and every field used by that mode, otherwise it returns 400 invalid_traffic_cycle_settings. traffic_cycle_mode allows default, calendar_month, whmcs_compatible, and clamp_to_month_end.

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 starts a per-node traffic rebuild. It rewrites that node's 5-minute facts from retained nic_metrics within database.traffic_retention_days. Success returns 202 with the status body. Missing or deleted nodes return 404 not_found; any running rebuild returns 409 traffic_rebuild_running; unavailable rebuild tasks return 503 traffic_rebuild_unavailable. The task invalidates overlapping monthly snapshots in the retained window when it starts and does not synchronously rewrite monthly snapshots.

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.1.

POST /api/admin/nodes/{id}/upgrade requires version.supports_auto_update=true. Current node versions below 0.2.1 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.

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 and period. months is at most 24. period=current starts at the current billing cycle; period=previous starts at the previous cycle. Omitted means current. includes_current is true for period=current and false for period=previous.
  • Traffic queries use each node's effective traffic configuration. Nodes with traffic_cycle_mode=default inherit the global cycle; nodes with traffic_direction_mode=default inherit the global direction mode.
  • 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 should use coverage_ratio for sample coverage and accuracy hints. partial is retained only for compatibility.

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 historyRequired device

For disk.temp_c, device can match physical disk name, ref, or path. Temperature history does not use a rollup prefix.

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

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/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

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/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