Clone or deploy the open-source Geotab MyGeotab API Adapter from the official Geotab GitHub repository, which provides a pre-built data extraction pipeline from MyGeotab to relational or streaming targets
Configure the adapter with your MyGeotab database credentials, target output database connection string, and the entity types you want to extract (devices, trips, exceptions, status data, fault data)
Run the adapter in continuous mode so it uses GetFeed under the hood to incrementally extract new records using version tokens, writing them to the configured output datastore
Connect your analytics platform to the output datastore (for example, a SQL database or data warehouse table) and build your reporting layer on top of the normalized schema the adapter produces
Monitor the adapter process for authentication failures (Geotab sessions expire and must be refreshed), connection errors to the output store, and version token persistence across restarts
Review Geotab's API best practices guide to understand data volume implications of the entity types you are extracting and tune the adapter polling interval accordingly
Known gotchas
The API Adapter is a community-supported open-source tool maintained by Geotab; it is not a supported commercial product, so production deployments require your team to own operational stability
MyGeotab session tokens have a limited lifetime and will expire if not refreshed; the adapter handles re-authentication but a misconfigured credential will cause silent extraction failures until the service is restarted
Status data and fault data entity types can be extremely high-volume for large fleets; start with a limited entity set and expand incrementally after validating your output datastore can handle the write throughput
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