Reach It
- Method:
POST - Path:
/api/mode - Base URL:
http://openhaldex.local(or controller IP) - Response format:
JSON
API Endpoint
Set runtime mode with alias parsing and capture safety guard.
POST/api/modehttp://openhaldex.local (or controller IP)JSONNone
JSON: {"mode":"MAP"}; aliases accepted.
Receive: JSON: {"ok":true,"mode":"MAP"}
Parse: Case-insensitive aliases. Non-STOCK blocked in capture mode.
400 invalid json/mode; 409 capture active; 200 success
curl -s -X POST "http://openhaldex.local/api/mode" -H "Content-Type: application/json" -d '{...}'
This section is intentionally unique for POST /api/mode. Focus area:
deterministic mode switching with immediate user feedback. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated
workflow step rather than a generic HTTP action.
Operational scenario: Submit one explicit mode intent, then refresh status and confirm the active mode id, UI highlight, and control gate state.
Domain vocabulary: mode-alias, state-transition, override, lock-profile, driver-intent, debounce, toggle-latency, mode-guard, fallback-mode, confirmation-banner.
POST /api/mode and capture status code + raw response./api/status) to verify runtime convergence.await fetch('/api/mode',{method:'POST',headers:{'Content-Type':'application/json'},body:JSON.stringify({mode:'map'})});
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.