Introduction

DIMO Check-in

🔑 Developers use this space to get access to the network of things in DIMO. You got access to the lobby in Authentication, now you have access to the resources permitted to you.

Developer Notes

1. For non-public API endpoint access, please refer to REST API Authentication
2. For 1st time users, it is REQUIRED to fetch the newly logged in user from DIMO. This is to make sure the user account is initialized in DIMO. If for some reasons that the user was not initialized, other API endpoints may fail to operate.

3. For vehicle identification, there are 2 developer routes currently available:

   1. [Legacy] User Device ID

   2. [Web3] Vehicle Token ID

DIMO Protocol

Devices API

Core API to interact with the vehicle device.

Device Data API

Vehicle-related data.

Device Definitions API

Public API endpoint for device makes, types, and definitions.

Token Exchange API

2nd leg of the REST API authentication to access vehicles that shared privileges.

Trips API

Logs of trips bounded by start and end time. Token exchange is needed to access this endpoint.

Users API

User account operations & other user flows such as email confirmation, web 3 challenges, terms of services, etc.

Digital Infrastructure Service

Valuations API

Public API endpoint for instant offers and valuations for vehicles.

Vehicle Signal Decoding API

Public API endpoint for DBC, PID, and device configurations.