DIMO Protocol
Last updated
Last updated
DIMO Check-in
API services in the DIMO Protocol can be public or private, depending on whether an access_token or additional permissions_token are required.
In this API references page, a lock sign indicates that the data is secured by either one of the tokens where as an unlocked sign indicates that it is a public API service.
DIMO supports two core GraphQL API in Identity and Telemetry. GraphQL is a widely-recognized API querying language that outlines a data interface, independent of the system managing the data.
Benefits #1: A query to the GraphQL API gets developers predictable data and reduce over-fetching.
Benefits #2: Applications using the GraphQL API are faster and more stable because developers are in full control of the data received, not the server.
To learn how to use DIMO GraphQL API, check out Additional References > DIMO GraphQL Basics.
The DIMO Protocol also provides the following REST API services:
This is the open catalog of DIMO-connected devices and vehicles.
Access all sensor data from the DIMO-connected devices and vehicles.
Account management endpoints.
Generate verifiable proof about a vehicle's data.
Interact with the vehicle device.
Helper endpoints for Device Definitions.
Gateway to obtaining a JWT to access protected API services.
Logs of trips bounded by start and end time.
