Reach It
- Method:
POST - Path:
/api/logs/clear - Base URL:
http://openhaldex.local(or controller IP) - Response format:
JSON
API Endpoint
Clears selected log scope.
POST/api/logs/clearhttp://openhaldex.local (or controller IP)JSONNone
JSON: {"scope":"all|can|error|everything"} (default everything).
Receive: JSON: ok,debugCaptureActive,disableController
Parse: Unsupported scope fails.
400 clear failed/invalid json; 200 success
curl -s -X POST "http://openhaldex.local/api/logs/clear" -H "Content-Type: application/json" -d '{...}'
This section is intentionally unique for POST /api/logs/clear. Focus area:
scope-level log reset for controlled troubleshooting sessions. When integrating OpenHaldex at scale, this endpoint should be treated as a dedicated
workflow step rather than a generic HTTP action.
Operational scenario: Clear selected scope before reproducing an issue so resulting logs contain only relevant events.
Domain vocabulary: scope-clear, all-reset, can-reset, error-reset, fresh-capture, troubleshoot-window, log-reset, scope-hygiene, clear-operation, diagnostic-baseline.
POST /api/logs/clear and capture status code + raw response./api/status) to verify runtime convergence.await fetch('/api/logs/clear',{method:'POST',headers:{'Content-Type':'application/json'},body:JSON.stringify({scope:'can'})});
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.