API Endpoint

List Maps

Lists current map and available map files.

GETMap and Curves/api/maps

Reach It

Query Input

None

Body Input

None

Response / Parse

Receive: JSON: {"current":"...","maps":[{"name","path","format","readOnly"}]}.

Parse: Use readOnly to guard delete/edit actions.

Error Behavior

200 success

Example Call

curl -s "http://openhaldex.local/api/maps"

Endpoint-Specific Engineering Notes

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.

Common Mistakes for This Endpoint

Practical Validation Pattern

  1. Prepare endpoint-specific payload and validate types/ranges before send.
  2. Execute GET /api/maps and capture status code + raw response.
  3. Parse response and apply only validated fields to UI state.
  4. Run a follow-up read (usually /api/status) to verify runtime convergence.
  5. Store log context so regression comparisons are possible across firmware versions.

Reference Snippet

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.

Project Backlinks

Try the OpenHaldex Firmware Demo

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.

Open firmware demo