LogoLogo
DocsHomeSupportContact
  • Getting Started
    • Introduction
    • Build on DIMO
  • DEVELOPER GUIDE
    • Developer Overview
    • Developer Console
    • Authentication
    • DIMO Developer SDKs
      • Data SDK
      • Login with DIMO SDK
        • React Component
        • Login with DIMO Redirect
        • Core Functionalities
      • TypeScript: Transactions SDK
      • SDK Release Notes
    • Low Code Tools
      • n8n: Getting Started
    • Permissions Contract: SACD
    • DIMO Credits
    • Response Types
    • Rate Limits
    • Developer FAQ
    • Developer Changelogs
    • Troubleshooting Common Issues
  • API References
    • Overview of DIMO API
    • Attestation API
    • Device Definitions API
    • Identity API
      • Schema & Types
      • Scalars
      • Nodes & Objects
        • AftermarketDevice
        • AftermarketDeviceConnection
        • DCN
        • DCNConnection
        • DeveloperLicense
        • DeviceDefinition
        • Earning
        • EarningsConnection
        • Manufacturer
        • Sacd
        • SyntheticDevice
        • Vehicle
        • VehicleConnection
        • VehicleEarnings
        • UserRewards
      • Common Queries
    • Telemetry API
      • Schema & Types
      • Scalars
      • Nodes & Objects
        • Signals
        • SignalsLatest
      • Common Queries
    • Token Exchange API
    • Trips API
    • Valuations API
  • DIMO Hardware
    • Introduction
    • DIMO Hardware Application
    • DIMO Manufacturing License
    • Development & Certification
    • Audits & Assessments
      • Hardware & Security Audit
      • Customer Experience Assessment
      • Integration Testing & Quality Control
      • Final Approval
    • DIMO Device License
      • Device Minting Certificates
    • Essential Documents
      • Hardware & Security Audit Checklist
      • Approved Hardware Auditors
      • DIMO Memorandum of Understanding (MOU)
  • Additional References
    • Developer License
    • DIMO GraphQL Basics
  • Deprecated Resources
    • Guides
      • Developer Journey
      • Quick Start Guide
      • Hello World
      • Code Exchange Flow
    • Data Availability
Powered by GitBook
On this page
  • Developer Console
  • Login with DIMO
  • DIMO Auth & Token Exchange
  • Data SDK
  • The Developer Journey

Was this helpful?

  1. DEVELOPER GUIDE

Developer Overview

PreviousBuild on DIMONextDeveloper Console

Last updated 1 month ago

Was this helpful?

DIMO provides a comprehensive suite of developer tools designed to support your build process.

The available tools vary based on your and your product’s integration type with DIMO. Below, you’ll find detailed descriptions of the basic components to build an integration with DIMO:

Once you have data permissions, this is where your app can start fetching data from the DIMO APIs. DIMO does offer a few public API endpoints where vehicle permissions are not required, but overall, you should be able to utilize Data SDKs in different programming languages to get the data of your interest. This is where integrating DIMO data into your application happens.

The Developer Journey

Developers should start at the console. The console encompasses the and . Through registration on the console, developers can now manage their license access and buy credits for infrastructure costs at scale.

Drop this component into your React app, or simply redirecting users to login.dimo.org using any button component on your web-app: this is your entry point to getting vehicle permissions shared with your app (handled via ), getting access to the user's , and sending app-defined on behalf of the users.

&

The moment that end users shared their vehicle permissions with your application, you can now start to go through the authentication process. Authentication to vehicle data includes fetching for two JSON Web Tokens: to show that you are the registered developer, and to prove that the vehicle gave you the right permissions to fetch sensitive data.

The below embed showcases a typical developer journey or flow to get your application connected to DIMO, requesting vehicle permissions, and using the SDKs to perform actions. The flow begins with creating an application in the , and takes you through the steps required to begin using vehicle data. You can see an expanded view of this flow by clicking on the fullscreen icon in the right corner.

Login with DIMO
SACD permissions contract
Account
transactions
DIMO Auth
Token Exchange
Data SDK
DIMO Developer Console
Developer Console
DIMO Credits (aka DCX)
Developer License
A Developer JWT
a Vehicle JWT
DIMO Developer Tool Suite
developer classification