Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register for API access at developers.trackunit.com, which hosts Trackunit's current Iris platform documentation.
Choose between the REST or GraphQL interface offered on Iris; GraphQL allows retrieving only the specific fields needed per query.
Use the Machine Onboarding API to register or look up fleet assets, and the Telematics Device API to pull device configuration and status data.
Confirm which OEM/dealer telematics feeds are actually connected into Trackunit for the specific cranes in the fleet, since Trackunit aggregates data from over 100 partner OEMs/telematics providers rather than manufacturing hardware itself.
Do not build new integrations against the legacy Classic API suite at api.trackunit.com/public — it is frozen, with restricted issuance of new authentication tokens, in favor of the Iris platform.
Known gotchas
Machine coverage depends entirely on which OEM or dealer has an active data-sharing connection into Trackunit for that specific crane — not every crane brand or model is automatically represented even if the rental company has a Trackunit account.
The legacy Classic API (api.trackunit.com/public) is explicitly deprecated for new development; confirm any existing integration isn't quietly relying on it before treating Iris migration as optional.
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?