Skip to main content
Everything Radar does in the UI is available over HTTP / SSE / WebSocket. The endpoints below are served by the OSS binary on --port (default 9280). Through Cloud, the same endpoints are reachable at https://api.radarhq.io/c/<cluster_id>/api/... with a PAT for auth.
This is a high-level surface tour, not a per-field reference. Run Radar with --debug-events for verbose request logging while exploring.

Conventions

  • Authentication: see Authentication. For Cloud, send Authorization: Bearer rhp_....
  • Content type: JSON unless noted. SSE endpoints emit text/event-stream.
  • All responses include Cache-Control: no-store.
  • Error shape: { "error": "<message>", "code": "<machine_readable>" }.

Health & metadata

Config & settings

Dashboard

Resources & topology

Timeline & events

Logs

Exec, debug, terminal, port-forward

Workload & node operations

Helm

CronJobs

GitOps - Argo CD

GitOps - Flux CD

Audit (cluster-level best-practices, not Cloud audit log)

Traffic & networking

OpenCost

Prometheus

Image filesystem

Packages

Sessions

Cluster API (multi-context, kubeconfig discovery)

Self-update

Desktop app

These are no-ops outside the desktop binary. The web app uses them to open files, save artifacts, and trigger app self-update.

Certificates

Metrics (kube-state)

AI

Auth (when enabled)

Cloud control plane

These live on api.radarhq.io, not on the in-cluster Radar. Auth is the WorkOS session cookie or a PAT. All endpoints are owner / member / viewer gated as documented per page.

Debug (OSS only)

These are disabled under cloud-mode (the in-cluster Radar strips them so they never traverse the tunnel).

See also