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
- Create a Developer License and get your
Client ID,Redirect URIandAPI Keyfrom the Developer Console. - 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.
- Get each vehicle shared with you through DIMO Connect. You need a vehicle shared with you before you can fetch a Vehicle JWT.
- 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.
- Exchange your Developer JWT for a Vehicle JWT by sending a
POSTrequest tohttps://token-exchange-api.dimo.zone/v1/tokens/exchange. The request includes thenftContractAddress, the vehicletokenIdand the permissions (privileges) you are requesting. Theeventsquery below needs privilege 1 (all-time non-location data) and privilege 4 (all-time location). - Send your Vehicle JWT as
Authorization: Bearer <Vehicle JWT>on requests to the Telemetry API athttps://telemetry-api.dimo.zone/query. It is a GraphQL API. - Query the
eventsresource with the vehicle'stokenIdand afromandtotime range, both of which are required, and filter bytagsusingbehavior.harshBraking, or filter bynameusingHarshBraking. The tag operators arecontainsAny,containsAll,notContainsAnyandnotContainsAll. UseExtremeBrakingif you also want the more severe deceleration events. - Read the fields on each event:
timestamp,name,source,durationNsandmetadata.
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.