Export equipment telematics from Trackunit in standard ISO 15143-3 (AEMP 2.0) format
domain: Trackunit (ISO 15143-3 Export API) · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the "Export ISO 15143-3 (AEMP 2.0)" API introduction on developers.trackunit.com to confirm the endpoint and required scopes.
Authenticate to the Trackunit API using the credentials/OAuth flow documented for the export API.
Call the export endpoint to retrieve equipment data already normalized to the AEMP 2.0 payload structure.
Map the returned fields directly to your internal mixed-fleet schema, since Trackunit's export is explicitly built to match the ISO standard's field names/types.
Validate coverage of expected machines by cross-checking the equipment list against what's actually enrolled/reporting in the Trackunit fleet before assuming missing machines are an API bug.
Known gotchas
The export API surfaces only data Trackunit's own gateway devices/integrations have ingested — machines not connected through Trackunit's ecosystem won't appear regardless of API access.
As with other ISO 15143-3 implementations, this is a read export of the standard field set; anything Trackunit-proprietary (e.g., its own alerts/geofencing model) requires Trackunit's separate native API.
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?