Asset reading

Odometer and engine-hour readings, as recorded.

Part of Assets in the register catalog.

Register ID

asset_readingUse 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

PlannedDefined ahead of the connector that will fill it.

Data

OrganisationPrivate to each organisation's own workspace.

Version

v1Current version.

Download JSON SchemaSee an example record

Connectors

Connected today

Demiton keeps this register current from these systems now.

No system fills this register yet.

On the roadmap

Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.

None planned yet.

Fields

12 fields: 3 required, 9 optional.

Required

Every record carries these fields.

source_systemText

Which bound system emitted the row.

Example: NAVMAN

assetText

The machine the reading belongs to.

Example: 9301

read_atDate and timeISO 8601, with time zone

When the reading was taken.

Example: 2026-07-14T06:45:00Z

Optional

Present when the source system records them.

odometerDecimal numberUnit: km

The odometer reading.

Example: 88210.2

engine_hoursDecimal numberUnit: hours

The engine-hours meter reading.

Example: 4123.5

reading_sourceText

Whether the reading is GPS-derived or from the CAN bus.

Example: gps

odometer_at_installDecimal numberUnit: km

The odometer when the device was fitted.

external_idText

The source system's id for the reading, where it has one.

deviceText

The telematics unit that produced the reading.

Example: NAV-DEV-4471

ignition_statusText

Whether the ignition was on at the reading.

Example: on

location_labelText

Where the machine was, as text.

Example: Capricorn Highway near Emerald

driverText

The driver logged in at the reading.

Example: 5501

Example record

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

asset_reading.example.json

{
  "asset": "9301",
  "device": "NAV-DEV-4471",
  "driver": "5501",
  "engine_hours": 4123.5,
  "ignition_status": "on",
  "location_label": "Capricorn Highway near Emerald",
  "odometer": 88210.2,
  "read_at": "2026-07-14T06:45:00Z",
  "reading_source": "gps",
  "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.

Schema URL

https://docs.demiton.io/registers/asset_reading/v1.json

Show the full JSON Schema

Loading the schema…