Overview of DIMO API
Last updated
Last updated
DIMO Check-in
API services consist of 2 major categories: GraphQL API and REST API. Of each category, there are several different services that your application may use.
Almost all of the services will require a Vehicle JWT as your application will tap into a specific user-owned vehicle, while the Identity API acts as the open catalog to the DIMO Network.
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.
DIMO also provides the following REST API services:
Open catalog of DIMO-connected devices, vehicles, rewards, and developer licenses.
Access all sensor and other private data from the DIMO-connected devices and vehicles.
Generate verifiable proof about a vehicle's data.
Utility endpoints for Device Definitions.
Gateway to obtaining a JWT to access protected API services.
Logs of trips bounded by start and end time.
Instant offers and valuations for vehicles.