Authenticate to the MyGeotab API using the Authenticate method with your database name, username, and API key to receive a session credentials object
Use the Get method with the ExceptionEvent entity type to retrieve historical exception records for a date range, filtered by device or driver as required
Switch to the GetFeed method for ongoing exception monitoring: GetFeed returns a fromVersion token on the first call which you pass on subsequent calls to receive only new records since the last poll
Similarly use GetFeed with the Trip entity type to efficiently stream new completed trip records, capturing distance, start/end times, driver, and device fields
Handle the version token carefully: store it persistently so that a service restart resumes polling from where it left off rather than reprocessing the entire history
Respect MyGeotab API best practices including limiting result set sizes, avoiding broad date ranges on Get calls, and using server-side filtering rather than client-side filtering for performance
Known gotchas
Geotab no longer issues CustomDevice credentials after February 2025; if your integration depends on custom telematics device types, contact Geotab support about the current integration path
The GetFeed version token is database-specific and not portable across databases or resellers; always store the token alongside the database name it came from
MyGeotab is a multi-tenant SaaS with reseller-hosted instances; the API server URL differs per database — always use the server URL returned in the Authenticate response, not a hardcoded domain
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