Build on top of monitoring, alerting, workspace access, and operational data.

If you are logged in via the UI, your browser already has a session cookie. Any fetch call with credentials: 'include' will be authenticated.

// Browser fetch example
fetch('/api/projects', { credentials: 'include' })
  .then(r => r.json())
  .then(console.log);

Create a token in API Access. Use it in the Authorization header.

Bearer token authentication is a Premium feature. If a workspace falls back to Free, existing tokens stay listed for visibility but external Bearer auth will not authenticate until Premium is active again.

# curl example
curl -H "Authorization: Bearer <YOUR_TOKEN>" \
  -H "Accept: application/json" \
  https://dashmon.online/api/projects

Security note: Dashmon stores only a SHA‑256 hash of your token. The raw token is shown only once.

Governance note: Premium workspaces can create read-only or read/write tokens and optionally set an expiry period for each token.

If a signed-in member belongs to more than one workspace, Dashmon can expose a selected owner workspace for the current session. Reads, Premium checks, and write limits then follow that selected workspace instead of only the personal user row.

# inspect effective workspace capabilities
curl -H "Accept: application/json" --cookie "dashmon_session=<COOKIE>" \
  https://dashmon.online/api/user/permission-foundation

# switch to another accessible workspace context
curl -X POST -H "Content-Type: application/json" \
  --cookie "dashmon_session=<COOKIE>" \
  -d '{"ownerUserId":"workspace_owner"}' \
  https://dashmon.online/api/user/account-context

A Premium workspace does not automatically mean every member can edit it. API routes can still return forbidden responses when the active role is view-only, project-scoped, or temporarily write-locked because the workspace is over plan limits.

• Use /api/user/permission-foundation to inspect role, scope, and account capabilities.
• Use /api/me to read the effective workspace plan and write-lock state shown in the app.
• Expect some routes to allow read access but still deny write actions with 403.

List all projects + devices

# Returns your projects with device summaries
curl -H "Authorization: Bearer <YOUR_TOKEN>" \
  https://dashmon.online/api/projects

Device history (for charts)

# latest 120 samples for a device
curl -H "Authorization: Bearer <YOUR_TOKEN>" \
  "https://dashmon.online/api/devices/<DEVICE_ID>/history?limit=120"

Dashmon returns an X-Request-Id header on API responses. Include that value in support tickets or incident notes so server-side logs can be traced quickly.

curl -i -H "Authorization: Bearer <YOUR_TOKEN>" \
  https://dashmon.online/api/projects

Use /api/meta/capabilities to inspect API basics like supported auth modes, request tracing headers, token policy, public docs, and the signed-in API console link without scraping this page.

curl https://dashmon.online/api/meta/capabilities