Telematics

Fleet self-serve connect.

POST /connect is a public endpoint (no API key) that lets a fleet connect its own OEM telematics account. The hub renders the credential form and mints a single-use connect token; the fleet's browser posts directly to the Gateway so credentials never pass through the hub.

The connect call

POST /connect

{
  "connect_token": "ct_XXXX",
  "provider": "jcb_livelink",
  "credentials": { "username": "…", "password": "…" },
  "label": "optional"
}

200 response

{ "ok": true, "connection_id": "…", "provider": "jcb_livelink" }

// OAuth providers (John Deere, CNH) also return:
"next_step": { "type": "oauth_consent", "authorize_url": "…", "expires_at": "…" }

Credentials are validated against the OEM before the token is consumed. A rejected credential returns a human-readable 4xx and the token stays usable.

Token errors

400Missing token

404Unknown token

409Token already used

410Token expired (15-minute TTL)

CORS and limits

Only origins on the operator-configured allowlist may post — there is no wildcard. 10 requests per minute per IP, 16 KB body limit.

Supported providers

ISO 15143-3

Standard OEM machine-data feeds

jcb_livelinkbobcat_machineiqhyundai_himatevolvo_caretrackcat_visionlinkliebherr_lidathitachi_consitedevelon_connectcase_sitewatchnewholland_fleetforce

OEM native (OAuth consent)

Completed in the provider's browser UI

jd_operations_centercnh_fieldops

Aggregators

Mixed-fleet telematics platforms

trackunitgeotabsamsaramotivehiboo

TPMS

Tire pressure and temperature

rimex_tyresenseconti_conticonnect

Stubs

Contact vendor

psi_tireviewdoran_360