Skip to main content
Technical Preview

Overview

Client-mode REST API connector for Trackunit construction and off-highway telematics: list and find assets, latest GeoJSON locations, engine hours, fuel and other machine insights from the Time Series and ISO 15143-3 (AEMP 2.0) APIs, CAN faults, asset events, device health, sites and groups, asset notes and custom fields, and broker data ingestion, with OAuth 2.0 client credentials (API Tokens v2); companion server connector for Trackunit webhooks. This is one of the templates in the Trackunit REST API app (trackunit). Deploy it alongside the other connectors of that app when they depend on each other (for example a token connector plus an API connector).
Not yet verified against the live vendor API: No Trackunit account, API Key or API user on the factory box (no TRACKUNIT_* variables); only static, mock, negative-control and fake-credential public probes ran.

Auth

API Tokens v2: GetToken posts grant_type=client_credentials&client_id&client_secret&scope (form) to https://auth.trackunit.com/token/v2; tokens last 1200 s, no refresh token. Legacy API user: GetTokenLegacy posts grant_type=password&username&password&scope=api (form) with Authorization: Basic base64(client_id:client_secret) to https://auth.trackunit.com/token; tokens last 3600 s, refresh_token with offline_access. API events: Authorization: Bearer <access_token> from payload. Every event also sends User-Agent: Coreflux-Broker. Auth headers used by the template: Authorization: Bearer {value.json.access_token}.

Template parameters

BASE_ADDRESS default: https://iris.trackunit.com.

Events

Deploy

Get the template card (JSON with template and metadata) from the broker, then deploy the connector:
The deployable connector from the REST API app, with BASE_ADDRESS already filled in:
Deploy it with -addRoute (do not include ADD METADATA).

Usage example

Call ListAssets by publishing a JSON payload to its request topic, and read the reply on the response topic:
Last modified on October 21, 2026