Quick Start Guide

Getting Started as a Software Dev

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.


Authentication

A visualization on the different types of auth: Wallet-based or Code Exchange

User Authentication

(Optional) To implement a user login flow, developers can simply surface a Login to DIMO (aka Code Exchange Flow) that redirects the user to https://auth.dimo.zone/auth with your set of client_id, redirect_uri, and other URL parameters.


API Authentication

(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 wallet-based authentication flow into your application.


Onboarding

User Initiation & Creation

There are two routes of user creation, depending on whether you've implemented User Login redirect or API authentication with your application.

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 Update Authenticated User 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 wallet-based authentication flow. Once authentication completes, your application should perform these set of actions:

  1. Send a Confirmation Email to initiate a 2FA verification email.

  2. Submit an Email Confirmation Key to conclude the 2FA confirmation.

Vehicle Onboarding


Getting Started as a DIMO Hardware Dev

If you are a hardware developer, follow our hardware onboarding flow to get a general understanding of the hardware development process. You can pretty much ignore the API references and resources.

Last updated

Was this helpful?