Skip to content
Demiton

Vehicle list

Vehicles registered in your telematics system.

Part of Assets in the register catalog.

Register ID
vehicle_listUse this name to ask for the register. The API calls it a shelf ID.
Each record is
A stateThe current value of something, replaced when it changes.
Status
AvailableFilled today from connected systems, uploads or public data.
Data
OrganisationPrivate to each organisation's own workspace.
Version
v1Current version.

Connectors

Connected today

Demiton keeps this register current from these systems now.

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
  • Geotab
  • HammerTechPartial
  • MapTrackPartial
  • SitematePartial

Fields

13 fields: 6 required, 7 optional.

Required

Every record carries these fields.

assetText

The fleet vehicle the row is about.

Example: Grader 140M #1

vinText

Vehicle Identification Number — the chassis identifier the platform converges the asset on.

Example: 6F5CE28G1PL500123

labelText

Human-readable vehicle name.

Example: Grader 140M #1

source_systemTextUnit: TRIMBLE)

—.

Example: NAVMAN

source_record_idText

The source's own primary identifier for the record.

Example: NV-VEH-4021

occurred_atDate and timeISO 8601, with time zone

The observation/harvest timestamp of the register fact.

Example: 2026-06-01T00:00:00Z

Optional

Present when the source system records them.

registrationText

Registration plate.

Example: BWG140M

registration_jurisdictionText

The state/territory that issued the plate.

Example: QLD

makeText

OEM / manufacturer.

Example: Caterpillar

modelText

OEM model designation.

Example: 140M

year_of_manufactureWhole numberUnit: year

Year the vehicle was built.

Example: 2021

machine_typeTextUnit: trailer \

plant)

Example: plant

fleet_groupText

Telematics fleet/group membership.

Example: Grading Fleet

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

vehicle_list.example.json
{
"asset": "Grader 140M #1",
"fleet_group": "Grading Fleet",
"label": "Grader 140M #1",
"machine_type": "plant",
"make": "Caterpillar",
"model": "140M",
"occurred_at": "2026-06-01T00:00:00Z",
"registration": "BWG140M",
"registration_jurisdiction": "QLD",
"source_record_id": "NV-VEH-4021",
"source_system": "NAVMAN",
"vin": "6F5CE28G1PL500123",
"year_of_manufacture": 2021
}

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.

Schema URL
https://docs.demiton.io/registers/vehicle_list/v1.json
Show 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.

Book a 30-minute callStart free