Register an application at developer.gomotive.com and obtain an API key; Motive uses OAuth 2.0 for user-context calls and API key authentication for fleet-manager-context calls.
Retrieve a list of drivers by sending GET https://api.gomotive.com/v1/users with the X-Api-Key header; filter by role=driver.
Pull Hours of Service logs by sending GET https://api.gomotive.com/v1/hos_logs with parameters driver_id, start_date, and end_date; the response includes a list of log objects each containing duty status events, violations, associated inspection reports, and the log's certification status.
For each HOS log, inspect the duty_status_logs array to see the sequence of On Duty, Off Duty, Driving, and Sleeper Berth events with their durations and start timestamps.
Retrieve ELD-specific vehicle gateway data (ECM connections, sensor readings) via the vehicle gateways endpoints documented at developer-docs.gomotive.com.
Use pagination parameters page and per_page on all list endpoints; iterate until the returned list is empty or a next_page link is absent.
Known gotchas
Access to HOS and ELD data via the API requires that the fleet has the ELD compliance add-on enabled in Motive and that drivers use Motive ELD hardware or the Motive Driver App in ELD mode; API calls return empty results for non-ELD fleets.
FMCSA regulations require that HOS data remain unaltered; your integration must treat pulled logs as read-only audit data and must not attempt to programmatically edit or override driver logs.
API documentation moved to developer-docs.gomotive.com in January 2025; ensure you are referencing the current documentation as old community links may point to deprecated endpoints.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp