Driving behaviour event

Harsh braking, acceleration and cornering events from telematics.

Part of Assets in the register catalog.

Register ID

driving_behaviour_eventUse 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.

Download JSON SchemaSee an example record

Connectors

Connected today

Demiton keeps this register current from these systems now.

• Navman

On the roadmap

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

• EROADPartial
• GeotabPartial

Fields

14 fields: 7 required, 7 optional.

Required

Every record carries these fields.

assetText

The vehicle the event was recorded against.

Example: 9301

occurred_atDate and timeISO 8601, with time zone

When the harsh braking/acceleration event occurred.

Example: 2026-07-22T07:41:12+10:00

source_systemText

Which bound system emitted the row.

Example: NAVMAN

external_idText

The source's own event identifier (id)

Example: nav-evt-88104

categoryText

Which kind of event it is: harsh braking or harsh acceleration.

Example: harsh_braking

deceleration_gDecimal numberUnit: g

Peak deceleration of an HB event, magnitude, INSTANTANEOUS (never summed)

Example: 0.48

acceleration_gDecimal numberUnit: g

Peak acceleration of an EA event, magnitude, INSTANTANEOUS.

Example: 0.05

Optional

Present when the source system records them.

deceleration_threshold_gDecimal numberUnit: g

The HB threshold the event exceeded (minDecelerationThrsh)

Example: 0.4

acceleration_threshold_gDecimal numberUnit: g

The EA threshold the event exceeded (maxAccelerationThrsh)

Example: 0.35

duration_sDecimal numberUnit: s

How long the event lasted (attributes.duration)

Example: 1.8

gpsGroup of fieldsUnit: — (datum, CRS and precision unverified)

The position carried on the event, and by the declared producer edge the geographic area it is attributed to.

driverNumber

The operator attributed to the event.

Example: 5502

deviceNumber

The telematics device that recorded the event.

Example: 771001

raw_attributesGroup of fields

The untouched source event payload, including the per-second acceleration/GPS trace the resource description promises.

Example record

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

driving_behaviour_event.example.json

{
  "acceleration_g": 0.05,
  "acceleration_threshold_g": 0.35,
  "asset": "9301",
  "category": "harsh_braking",
  "deceleration_g": 0.48,
  "deceleration_threshold_g": 0.4,
  "device": 771001,
  "driver": 5502,
  "duration_s": 1.8,
  "external_id": "nav-evt-88104",
  "gps": {
    "lat": -25.5326,
    "lon": 152.7011
  },
  "occurred_at": "2026-07-22T07:41:12+10: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.

Schema URL

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

Show the full JSON Schema

Loading the schema…