Build and register a custom MyGeotab page Add-In that surfaces third-party data alongside Geotab fleet data
domain: developers.geotab.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the MyGeotab SDK's Add-In development guide and glossary of concepts
Author an Add-In configuration JSON file describing the Add-In's name, support email, version, source (via Items and/or Files), and a digital signature
Reference external source code via the Items property rather than inlining Files, for easier development and debugging
Host the manifest at a stable URL so a MyGeotab database can install the Add-In by reference
Install it via System Settings > Add-Ins > New Add-In in the target MyGeotab database
Call the MyGeotab API (JavaScript/C# helper libraries, or raw HTTP) from within the Add-In's page context
Known gotchas
The Add-In configuration file requires a digital security signature — how it's distributed affects whether an unsigned config is accepted
MyGeotab API access from inside an Add-In requires valid MyGeotab user credentials at runtime; there's no separate, lower-privilege service identity by default
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?