Quick Start Guide
Last updated
Was this helpful?
Last updated
Was this helpful?
DIMO Check-in
DIMO fullstack dev refers to developers that utilize the entire stack of the DIMO protocol, from vehicle creation to onboarding users to providing services. A typical DIMO fullstack would be the DIMO Mobile App.
If you are looking to get access to vehicles that are already connected to the network or prefer using the DIMO mobile app to onboard your customers, please refer to the quick guide in Data Devs instead.
To start exploring in the DIMO Network, the is your best bet. This GraphQL API contains publicly-available data for every single connected vehicles in the DIMO Network. These public data are stored onto the blockchain and readily available via the GraphQL layer that DIMO has built.
You can simply build stuff using this publicly available API or offer more detailed vehicle data by going through the next set of steps.
The following onboarding section is about to be deprecated in Q4 2024. Please refrain from implementing it into your workflow.
DIMO Check-in
There are two routes of user creation, depending on whether you've implemented User Login redirect or API authentication with your application.
DIMO Check-in
(Optional) To implement a user login flow, developers can simply surface a (aka Code Exchange Flow) that redirects the user to with your set of client_id, redirect_uri, and other URL parameters.
(Optional) In cases where you wish to handle your own user login and not use the Login with DIMO redirect, you should learn how to build a into your application.
After you finish interacting with the auth server, you will have gained an access_token. Regardless of the authenticated method, you should use the access_token to hit first. The response will tell you what you should be doing next - either attaching a wallet or confirming an email.
For users created using the Web2 OAuth (Apple or Google SSO), developers will need to attach a Web3 0x wallet address to the user created. To do so, you will need to call and update the user appropriately.
When using the API authentication method, you will need to provide your end users a way to connect their Web3 0x wallet (e.g. WalletConnect integration) and use the wallet to perform the steps in the . Once authentication completes, your application should perform these set of actions:
to initiate a 2FA verification email.
to conclude the 2FA confirmation.
DIMO hardware dev refers to developers that are either looking to design & manufacture a device from scratch or integrate an existing device to work on the DIMO Network. A typical hardware dev would be developing something like an AutoPi, Macaron, or LTE R1 that you see in the .
If you are a hardware developer, follow our to get a general understanding of the hardware development process. You can pretty much ignore the API references and resources.
