Vehicle location
Last-known GPS position of each vehicle.
Part of Assets in the register catalog.
- Register ID
vehicle_locationUse this name to ask for the register. The API calls it a shelf ID.- Each record is
- An eventSomething that happened at a point in time.
- Status
- AvailableFilled today from connected systems, uploads or public data.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1Current version.
Connectors
On the roadmap
Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.
- EROAD
- GeotabPartial
Fields
17 fields: 3 required, 14 optional.
Required
Every record carries these fields.
- assetText
The vehicle/plant the snapshot is about; the shelf's only required coordinate.
Example:
9301- occurred_atDate and time
When the last event on the unit happened; the shelf's temporal coordinate.
Example:
2026-06-15T15:58:00- source_systemText
Which bound system emitted the snapshot.
Example:
NAVMAN
Optional
Present when the source system records them.
- readings_atDate and time
When the meter readings were taken, distinct from the last-event time.
Example:
2026-06-15T15:58:00- odometerDecimal number
GPS-sourced lifetime odometer meter.
Example:
18244.6- engine_hoursDecimal number
GPS-sourced lifetime engine-hours meter.
Example:
3210.4- odometer_canDecimal number
CAN-bus twin of
odometer- engine_hours_canDecimal number
CAN-bus twin of
engine_hours- distance_periodDecimal number
Distance accumulated over the reading window (delta, not a lifetime meter)
Example:
42.3- engine_hours_periodDecimal number
Engine hours accumulated over the reading window.
Example:
8.9- fuel_periodDecimal number
Fuel consumed over the reading window.
Example:
61.2- place_labelText
The human-readable location text delivered by the source.
Example:
Emerald Street, Yamala QLD 4702- deviceNumber
The telematics unit that produced the reading, distinct from the asset identity.
Example:
771201- operatorNumber
The driver/operator active on the unit.
Example:
5502- tripNumber
The source trip/journey the last event belongs to.
- last_event_typeText
The discriminator for what the last event was (type/subtype), for a state snapshot.
Example:
ignition_off- financial_periodText
The accounting period the snapshot falls in; derived, no raw source field.
Example:
2026-06
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "asset": "9301", "device": 771201, "distance_period": 42.3, "engine_hours": 3210.4, "engine_hours_period": 8.9, "financial_period": "2026-06", "fuel_period": 61.2, "last_event_type": "ignition_off", "occurred_at": "2026-06-15T15:58:00", "odometer": 18244.6, "operator": 5502, "place_label": "Emerald Street, Yamala QLD 4702", "readings_at": "2026-06-15T15:58:00", "source_system": "NAVMAN"}Use this contract
The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.
https://docs.demiton.io/registers/vehicle_location/v1.jsonShow the full JSON Schema
Loading the schema…
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.