Reach It
- Method:
GET - Path:
/api/status - Base URL:
http://openhaldex.local(or controller IP) - Response format:
JSON with mode, telemetry, logging, can state, mappings, frame diagnostics.
API Endpoint
Canonical runtime snapshot for UI reconciliation.
GET/api/statushttp://openhaldex.local (or controller IP)JSON with mode, telemetry, logging, can state, mappings, frame diagnostics.None
None
Receive: JSON with mode, telemetry, logging, can state, mappings, frame diagnostics.
Parse: Treat as source of truth after any POST.
200 success
curl -s "http://openhaldex.local/api/status"
This section is intentionally unique for GET /api/status. Focus area:
runtime truth-model reconciliation across dashboard widgets. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated
workflow step rather than a generic HTTP action.
Operational scenario: Use this route as the single source of truth after any write action. Poll at a controlled interval, detect stale timestamps, and update only changed UI elements.
Domain vocabulary: snapshot, freshness, heartbeat, telemetry-age, can-health, mode-shadow, state-drift, status-polling, readback, coherence.
GET /api/status and capture status code + raw response./api/status) to verify runtime convergence.const status = await fetch('/api/status').then(r=>r.json());
Unique endpoint guidance like this helps prevent duplicate-content clustering while remaining genuinely useful for developers working on OpenHaldex integrations for haldex controller, VW AWD controller, and Audi AWD controller environments.
Preview the real OpenHaldex firmware UI in your browser with simulated live CAN traffic and interactive pages for tuning, diagnostics, logs, setup, and OTA workflows.