Reach It
- Method:
POST - Path:
/api/maps/save - Base URL:
http://openhaldex.local(or controller IP) - Response format:
JSON
API Endpoint
Saves active map under /maps with sanitized name.
POST/api/maps/savehttp://openhaldex.local (or controller IP)JSONNone
JSON: {"name":"track_dry_v2"}
Receive: JSON: {"ok":true,"path":"/maps/track_dry_v2.json"}
Parse: Use returned path for later operations.
400 invalid/missing name or save failed; 200 success
curl -s -X POST "http://openhaldex.local/api/maps/save" -H "Content-Type: application/json" -d '{...}'
This section is intentionally unique for POST /api/maps/save. Focus area:
persisting current map into reusable named profile. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated
workflow step rather than a generic HTTP action.
Operational scenario: Save current map after validation drive and include semantic naming for future comparison.
Domain vocabulary: profile-save, snapshot-name, filename-policy, overwrite-risk, save-confirmation, library-growth, versioned-map, naming-convention, backup-profile, save-metadata.
POST /api/maps/save and capture status code + raw response./api/status) to verify runtime convergence.await fetch('/api/maps/save',{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.