Developer Console
Registering as a build on DIMO developer
Last updated
Was this helpful?
Registering as a build on DIMO developer
Last updated
Was this helpful?
DIMO Check-in
For developers that previously registered with Developer Console prior to November 2024, your Developer License will NOT be managed by the Console. You could either create a new license with the new account, or continue to use your old license as is.
The (aka console) is a self-service portal that assists with developers in getting their Developer License, and getting DIMO Credits. For more information about Developer Licenses, check out .
The console supports three types of social logins: Google, Apple, and Github. You can also create an account with any email address using the input field. The OAuth process authenticates your identity and provisions a DIMO Global Account through the Accounts API, using the email address associated with your OAuth provider. If your email is already registered with DIMO Mobile, you can seamlessly access that account in the console.
Developer Notes
Developer Notes
Creating a Developer License is FREE, and the name that you give your license is public to all other developers. Your Developer License name is like a username - it must be unique amongst all the existing licenses on the DIMO Network.
Once your license is created, you will be presented with your license details. The Client ID is your public key, which can also be used to identify your license. To the left of your license name is the Token ID of your license, which is a number that can be used to identify your license as well.
You can easily view the vehicles that have shared privileged access to you via the Vehicles Table at the bottom of the License Details Page:
In order to view other public licenses, you must meet the following requirements:
Have created your own account on the DIMO Developer Console, and
Have created your own personal Developer License (even if you're just using this account to view other public license details).
Once you've met these requirements and are logged into your console account, you can view public license data by navigating to the following URL:
https://console.dimo.org/license/details/<license_token_id>
If you're trying to view details for a specific license, ask the license owner to provide you with the license token Id number and insert it into the URL above. For example:
Please note that public licenses do not contain sensitive personal information such as API Keys. You will need to request and securely share API Keys with your team as needed. We currently do not support shared developer license accounts with edit access - just read-only details via the method above.
This section is under construction, and will be updated once our billing system is finalized.
After logging in, you may see an empty account or one that already contains DIMO tokens.
The current Console supports paying for DCX using your account balances.
Coming soon!
If you are using , be sure to select the matching email to login when going through Login with Google. A mismatching email will result in a passkey error.
Before accessing the , you will need to obtain and configure a . You can easily obtain a Developer License directly via the console. Once you're logged in, simply give your license a name and hit "Create".
Within your license details, you will need to generate API Keys (aka private keys) and Authorized Redirect URIs for your license to work. The API Keys you generate will only be displayed once, so it's important that you copy and save your API Key somewhere secure upon generation. The public-facing authorized redirect URI is for the DIMO Auth server to validate your license access and used to redirect your users post sign-on (see ).
With a valid combination of the three parameters (Client ID, API key, and Redirect URI), you have now unlocked the DIMO APIs. For more information, check out how to use these details with the or the .
The Developer Console pulls in data from the public , which gives you the ability to view public license details of any license on the network. This comes in handy if you're collaborating with other team members who need read-only access to your license details, such as your Client ID and configured Redirect URIs.
