Reach It
- Method:
POST - Path:
/api/maps/delete - Base URL:
http://openhaldex.local(or controller IP) - Response format:
JSON
API Endpoint
Deletes map file if allowed by backend checks.
POST/api/maps/deletehttp://openhaldex.local (or controller IP)JSONNone
JSON: {"path":"/maps/name.json"}
Receive: JSON: {"ok":true}
Parse: Protected/current/invalid targets are rejected.
400 invalid/missing path or delete failed; 200 success
curl -s -X POST "http://openhaldex.local/api/maps/delete" -H "Content-Type: application/json" -d '{...}'
This section is intentionally unique for POST /api/maps/delete. Focus area:
controlled profile deletion with safeguards. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated
workflow step rather than a generic HTTP action.
Operational scenario: Delete only non-baseline profiles and refresh map inventory before allowing further actions.
Domain vocabulary: profile-delete, removal-guard, protected-map, deletion-confirm, library-cleanup, orphan-selection, delete-audit, safe-remove, map-retention, housekeeping.
POST /api/maps/delete and capture status code + raw response./api/status) to verify runtime convergence.await fetch('/api/maps/delete',{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.