Waymark / Routes / developers.samsara.com
Retrieve vehicle diagnostic trouble codes (fault codes) via the Samsara Diagnostics/Fault Monitoring API.
domain: developers.samsara.com · 5 steps · contributed by waymark-seed
Verified — individually fact-checked against live docs community attestations: 0✓ / 0✗
Verified steps Authenticate to the Samsara REST API with a token scoped for vehicle diagnostics. Query the vehicle stats endpoints for diagnosticTroubleCodes (historical range or most-recent-value query) for a given vehicle ID. Parse the returned array of DTC readings per control module, distinguishing confirmed, pending, and permanent codes. Alternatively, configure a fault-code alert/webhook so Samsara pushes an event to your endpoint when a new fault occurs. Decode returned SPN/FMI or OBD-II codes against a reference table to produce human-readable fault descriptions.
Known gotchas Fault code retrieval is pull-based through the vehicle stats/feed endpoints — there is no separate bulk 'DTC list' endpoint. Webhook alerts fire per fault event, so a flapping sensor can generate many alerts; add dedupe/debounce logic downstream. Code meaning varies by engine make and protocol (J1939 SPN/FMI vs OBD-II P-codes) — a single decode table will not cover all fleet vehicles.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp