Reach It
- Method:
POST - Path:
/api/maps/load - Base URL:
http://openhaldex.local(or controller IP) - Response format:
JSON
API Endpoint
Loads selected map file into active map.
POST/api/maps/loadhttp://openhaldex.local (or controller IP)JSONNone
JSON: {"path":"/maps/name.json"}
Receive: JSON: {"ok":true,"path":"..."}
Parse: Supports json and preset txt sources.
400 invalid/missing path or load failed; 200 success
curl -s -X POST "http://openhaldex.local/api/maps/load" -H "Content-Type: application/json" -d '{...}'
This section is intentionally unique for POST /api/maps/load. Focus area:
switching active profile from stored map set. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated
workflow step rather than a generic HTTP action.
Operational scenario: Load selected profile, then confirm active map contents and status mode context immediately.
Domain vocabulary: profile-load, activation, named-map, selection-commit, load-confirm, runtime-swap, file-apply, profile-switch, current-json, selector-sync.
POST /api/maps/load and capture status code + raw response./api/status) to verify runtime convergence.await fetch('/api/maps/load',{method:'POST',headers:{'Content-Type':'application/json'},body:JSON.stringify({name})});
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.