Guide

How to detect harsh braking in fleet vehicles with DIMO

· 3 min read

Use the DIMO Telemetry API events resource and filter for the behavior.harshBraking tag or the HarshBraking event type. As of August 2025, DIMO Events are only available on vehicles equipped with R1 LTE devices. DIMO adds vehicle-state depth on top of GPS tracking; it doesn't replace it.

Steps​

  1. Create a Developer License and get your Client ID, Redirect URI and API Key from the Developer Console.
  2. Get a Developer JWT. In the Developer Console you can use the system-generated one, or generate a new one with your API key using a server SDK.
  3. Get each vehicle shared with you through DIMO Connect. You need a vehicle shared with you before you can fetch a Vehicle JWT.
  4. Confirm the vehicle uses an R1 LTE. Events are defined by the data connection, and only the R1 LTE supports them as of August 2025.
  5. Exchange your Developer JWT for a Vehicle JWT by sending a POST request to https://token-exchange-api.dimo.zone/v1/tokens/exchange. The request includes the nftContractAddress, the vehicle tokenId and the permissions (privileges) you are requesting. The events query below needs privilege 1 (all-time non-location data) and privilege 4 (all-time location).
  6. Send your Vehicle JWT as Authorization: Bearer <Vehicle JWT> on requests to the Telemetry API at https://telemetry-api.dimo.zone/query. It is a GraphQL API.
  7. Query the events resource with the vehicle's tokenId and a from and to time range, both of which are required, and filter by tags using behavior.harshBraking, or filter by name using HarshBraking. The tag operators are containsAny, containsAll, notContainsAny and notContainsAll. Use ExtremeBraking if you also want the more severe deceleration events.
  8. Read the fields on each event: timestamp, name, source, durationNs and metadata.

Code​

This Telemetry API request checks which signals a vehicle exposes. Replace <yourVehicleJwt> with your Vehicle JWT and 12345 with the vehicle's token ID. Use it to confirm your Vehicle JWT works before you query events.

# Request header:
# { "Authorization": "Bearer <yourVehicleJwt>" }

query GetAvailable {
availableSignals(
tokenId: 12345
)
}

This query returns the harsh braking events for one vehicle in a time range. Replace 12345 with the vehicle's token ID and set from and to to the range you want.

query HarshBrakingEvents {
events(
tokenId: 12345
from: "2026-11-01T00:00:00Z"
to: "2026-11-07T00:00:00Z"
filter: { tags: { containsAny: ["behavior.harshBraking"] } }
) {
timestamp
name
source
durationNs
metadata
}
}

FAQ​

Which vehicles support harsh braking events?​

As of August 2025, DIMO Events are only available on vehicles equipped with R1 LTE devices. For additional support, contact Developer Support through the Console.

Who decides what counts as a harsh braking event?​

Events are pre-defined by each data connection. The data source provider determines the events for the connected vehicle.

What is the difference between HarshBraking and ExtremeBraking?​

The R1 event glossary describes HarshBraking as rapid deceleration detected by the device and ExtremeBraking as extreme rapid deceleration detected by the device.

What other events can I filter for?​

The R1 glossary also lists HarshAcceleration and HarshCornering. The documented tags are behavior.harshAcceleration, behavior.harshBraking, behavior.harshCornering and safety.collision.

Do I need the owner's permission to read this data?​

Vehicle owners consent to and control sharing, so builders get data with clear provenance. You need a vehicle shared with you before you can fetch a Vehicle JWT for it.

Methodology: based on the DIMO documentation pages Authentication, Building Your First App, and the Telemetry API Vehicle Events reference.

More guides · Browse vehicles