Navman connector for fleet telematics
The Navman connector reads fleet telematics from Navman TN360: the vehicle list, the driver directory, odometer/fuel/engine-hours meter snapshots, and time-windowed ignition, driver, speeding and engine-management events. It is read-only - Demiton does not write back to Navman.
Authentication: Integration API key sent as a static Bearer token (no OAuth exchange)
System type: NAVMAN
Protocol: TN360 REST v1
See your Navman fleet data in Claude — book a 30-minute call.
Supported resources
Section titled “Supported resources”| Resource | FETCH |
|---|---|
vehicles | ✓ Yes |
users | ✓ Yes |
vehicle_meters | ✓ Yes |
ignition_events | ✓ Yes |
driver_events | ✓ Yes |
speed_events | ✓ Yes |
engine_management_events | ✓ Yes |
users is the TN360 driver/operator directory - id, name, email, mobile, status, type and rulesets. It accepts a drivers_only filter that keeps only users with a fatigue ruleset membership, the population driver events fire for.
vehicle_meters is a current odometer, fuel and engine-hours snapshot per vehicle.
The four event resources require from_date and to_date. Dates are YYYY-MM-DD or DSL tokens (TODAY, NOW_MINUS_14_DAYS, NOW_MINUS_DAYS:N). Spans longer than seven days are chunked automatically.
engine_management_events is filtered to harsh braking (HB) and harsh acceleration (EA) only; idle-time actions from the same TN360 endpoint are excluded.
This connector is read-only - no resource supports PUSH.
Registers this connector fills
Navman keeps 7 registers current in Civil Memory , with 5 mapped to source fields. Each name is the record you ask for, not the system it came from - ask for it in Studio or from your own AI client.
| Register | What it holds | Fields from Navman |
|---|---|---|
Vehicle locationvehicle_location | Last-known GPS position of each vehicle. | 11 of 17 |
Speeding eventspeeding_event | Speeding events from telematics. | 8 of 19 |
Gps eventgps_event | GPS events: ignition, speed, geofence crossings. | 7 of 14 |
Asset utilisationasset_utilisation | Engine hours and utilisation for plant and equipment. | 5 of 19 |
Driving behaviour eventdriving_behaviour_event | Harsh braking, acceleration and cornering events from telematics. | 5 of 14 |
Employee listemployee_list | Employees registered in your payroll system. | Fills all of 21 |
Vehicle listvehicle_list | Vehicles registered in your telematics system. | Fills all of 13 |
The full field list, requiredness and an example record for any register are on its published contract. Where more than one system fills a register, the register is the same shape either way.
Integration model
Section titled “Integration model”The API key is injected into every request header as a Bearer token; there is no token exchange or refresh. Date tokens in query parameters are resolved to concrete dates at execution time.
Requests time out after 90 seconds and retry twice on timeout only, so a call can make up to three attempts. TN360 is inconsistent about returning some numeric attributes as JSON numbers or strings on the same field; the adapter coerces them at its boundary so downstream measures receive numbers.
Connection setup
Section titled “Connection setup”Required values:
- API Key - the Navman TN360 Integration API key
Optional:
- Base URL - override the default
https://api-au.telematics.com/v1to target a non-AU region or a test environment
Security
Section titled “Security”Access type: Read-only
Demiton reads vehicles, the driver directory, meter snapshots and event records from Navman TN360. No data is written back.
Permissions required: A TN360 Integration API key with read access to the fleet. Use a dedicated integration key for Demiton.
Data sensitivity: Fleet and driver telematics is classified as operational domain and is subject to Demiton’s identity-bound access controls.
Next steps
Section titled “Next steps”- Connecting a System - step-by-step wizard for setting up the connector
- Hilti ON!Track - tool and equipment tracking
- Trimble - equipment, assignment and timesheet reads
- Connect your operation - talk to us about scoping a Connected deployment
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would keep current from them, on your data, in a 30-minute call.