Reach It
- Method:
GET - Path:
/api/maps - Base URL:
http://openhaldex.local(or controller IP) - Response format:
JSON
API Endpoint
Lists current map and available map files.
GET/api/mapshttp://openhaldex.local (or controller IP)JSONNone
None
Receive: JSON: {"current":"...","maps":[{"name","path","format","readOnly"}]}.
Parse: Use readOnly to guard delete/edit actions.
200 success
curl -s "http://openhaldex.local/api/maps"
This section is intentionally unique for GET /api/maps. Focus area:
map inventory and active-profile discovery. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated
workflow step rather than a generic HTTP action.
Operational scenario: List available maps before any load/save/delete operation to prevent stale selector choices.
Domain vocabulary: map-list, profile-catalog, active-name, saved-profiles, filename-sanitization, library-state, preset-index, selection-state, current-profile, profile-enumeration.
GET /api/maps and capture status code + raw response./api/status) to verify runtime convergence.const maps = await fetch('/api/maps').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.