Create and track a multi-stop delivery route for a fleet vehicle using the Samsara Routes API instead of Samsara's vehicle-stats endpoints
domain: developers.samsara.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create Address records in Samsara for each stop location
Create a Route referencing those addresses and assign it to a driver or vehicle, whichever is less likely to change mid-route
Store order-specific details (SKUs, gate codes, PO numbers) in the stop-level notes field, since Samsara has no first-class "order" object
Configure routeStartingCondition and routeCompletionCondition (arrive vs. depart first/last stop) at the org or per-route level
Track progress by polling the routes audit-log feed or subscribing to route-stop webhooks (arrival, departure, ETA update, resequence)
Known gotchas
Samsara has no built-in "order" entity — all order metadata must be modeled through route/stop names and notes fields, which affects how downstream systems reconcile orders
Route completion/start timing is configurable both org-wide and per-route, and the per-route setting can silently override the org default if not checked
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
Need this verified for your stack — or a route we don't have yet?