Build On DIMO - February 2025

Hello developers! As we get deeper into 2025, love is in the air (Happy Valentine’s!) and the DIMO ecosystem continues to expand with exciting new features. This month, we’re launching DTC error codes via the Telemetry API, providing some insight into future developer-focused launches & quality of life improvements, and sharing a first look at the upcoming n8n integration:

Here’s everything you need to know this month:

• Check Engine Light: DTC Error Codes come to the Telemetry API

• Privacy-Focused Permission Sharing: Share relevant data with dealerships while keeping your historical location data private.

• Fewer Parameters. More Joy: The Data SDKs get a quality of life improvement to abstract away privilege lists, and you get to maintain your sanity.

• They Grow Up So Fast: Login with DIMO upgrades include vehicle onboarding, UX improvements, and UTM tracking capabilities.

• We Hear For You: DIMO Dev Console gets One-Time Password Login.

• Automate Your Workflows: The n8n DIMO node is ready for prime time.

• Rocky Mountain High: Meet the DIMO team at EthDenver.

• A New Experience is Coming Soon…

✴️ Check Engine Light: DTC Error Codes Come to the Telemetry API

It’s official: DTC Error Codes have arrived on the Telemetry API. Access to Diagnostic Trouble Codes (DTC) means that you can build in custom logic inside of your application to alert your users of issues that require their attention, such as taking their vehicles in for service. This will also enable service providers to diagnose issues remotely and prepare for vehicle service appointments more effectively.

The new field obdDTCList can surface DTC error codes for any vehicles you have privileged access to. DTC error codes are alphanumeric codes generated by a vehicle's diagnostic system, and are standardized under the OBDII protocol (in the [P|C|B|U]XXXXX format). We’ll be rolling out a dedicated DTC descriptions service to assist with decoding all possible error codes in the coming weeks, so stay tuned! If you’re interested in learning more about these codes, check out this article.

🔐 Privacy-Focused Permission Sharing

Privacy is important, especially when it comes to sharing vehicle data. That’s why our team is currently working on improving permission management to enable developers to build targeted solutions for the automotive service industry, while still respecting user privacy. This new permission layer will allow you to request certain privileges from your users' vehicles, such as odometer and DTC codes, while preventing access to more personal information such as historical location data.

The goal is to make the user experience as seamless as possible when taking in their vehicles for service: imagine a user being able to schedule service through your application, share diagnostics with your repair shop in advance of their appointment, and still maintain a layer of privacy by withholding their sensitive vehicle data. It’s a win-win for everyone involved. Stay tuned in the coming weeks for a formal announcement for the launch. 

🧘Fewer Parameters. More Joy: Data SDK Improvements

This should spark joy. If you’ve used any of the available Data SDK’s in the past, you know that to obtain a Vehicle JWT, you need to pass in a list of privileges to our Token Exchange API. This can sometimes be a bit tedious for backend integrations, especially if you’re not entirely sure which privileges have been granted by a specific Token ID. Did this user grant [1,2,3,4,5] or just [1,3,4,5]? What’s privilege 2 again? 🤔

Coming very soon to the TypeScript, Python, and C# SDKs, we’ve introduced a much simpler flow to obtaining a Vehicle JWT – all you need is a valid Developer JWT and a Token ID. Here’s an example of what that would look like:

Behind the scenes, before the Token Exchange request is processed, the SDK makes a call to the Identity API – specifically, checking to see all of the apps that the provided Token ID has granted permissions for. If there’s a grantee (application Client ID) that matches up with your application Client ID, the related permissions are then decoded automatically, meaning that you no longer need to try inputting them manually. Phew.

👶 They Grow Up So Fast: Onboard Vehicles & More with LIWD

A number of partners are already using the Login with DIMO (LIWD) component to quickly enable privileged access to their users' DIMO vehicles, and the marketplace continues to grow. The LIWD component is getting some significant upgrades to make it even more powerful for developers, opening up a first-time vehicle onboarding experience, and providing additional layers of customization. Here’s all the features you can expect to see roll out in the next several weeks:

Vehicle Onboarding: Users who have never onboarded to DIMO before will be able to do so directly via the LIWD component via Tesla & Smartcar integrations – all without ever needing to download the mobile app.

Customizable Branding: Gain more control over the components text fields and typography to provide a branded experience for your users.

UTM Tracking: Options for adding UTM parameters to URLs to allow for better tracking of your users and management of ongoing campaigns.

Upgraded User Experience: A cleaned up, visual overhaul of the login experience and enabling bulk vehicle sharing – especially useful for fleet managers.

The ability to onboard vehicles directly via LIWD will be a game changer, easing friction for users who want to use your application but have never experienced the power of DIMO before. Want to dive deeper into the Login with DIMO experience? Check out the full rundown here or read more in the docs.

🌅 A Quick Call To Developers:

As a part of the overhaul of the LIWD experience, we’ll also be sunsetting the embedded version of the Login component. You’ll still be able to use the popup & redirect methods as usual – however, if you’re a developer actively using the embedded component, or plan to use it, we want to hear from you: drop us a message in the #build-on-dimo Discord channel.

🔑 We Hear For You: DIMO Dev Console Getting OTP Login

Logging into the DIMO Developer Console just got a whole lot easier. Despite passkeys being the new frontier for passwordless sign-in, we know that some devices are not yet equipped with biometric authentication. Some Windows and Android devices aren’t fully compatible with passkeys, so we’ve recently made an update to the login experience on the Developer Console to support One-Time Passcode (OTP) login. This means that if your device doesn’t yet have passkey support, you’ll still be able to login via a one time code. 

🌊 Automate Your Workflow: A Deeper Dive into n8n

We’ve teased this a bit already, but we’re excited about the launch of our first official no-code integration with n8n, which will make DIMO data accessible to everyone – regardless of technical background. For developers, this integration opens up entirely new possibilities for rapid prototyping and workflow automations. This also means that, once the DIMO n8n node launches, users will be able to integrate DIMO data with ChatGPT, DeepSeek, Claude, and more to build AI Agents directly within n8n. We cannot wait to see what developers and non-developers alike build with n8n. Here’s what to expect when the n8n integration launches in a few weeks:

Intuitive API Access

• Get full access to all DIMO APIs, including Identity & Telemetry queries.

• A pre-built DIMO node for common operations and simple authentication handling.

• Custom query support for more advanced use cases.

Integration Capabilities

• Integrate DIMO data with over 1000+ other platforms and services that you already use.

• Build automated workflows without having to install anything or configure a codebase.

• Create complex data pipelines with simple visual tools.

Developers Will Love

• Rapidly prototyping & developing initial proof-of-concepts.

• Easily test complex integrations and get up and running quickly.

If you already have an application setup within the DIMO Developer Console, you’re more than halfway toward building on n8n. If not, the initial setup is easy:

1. Create your Developer License on the DIMO Dev Console.

2. Set up your first application on the console, and generate a Redirect Uri & API Key.

3. Configure the n8n DIMO node with your application credentials.

4. Start building automated workflows and prototypes on n8n.

Look out for a formal announcement in the next few weeks when the n8n integration officially launches.

Do you use another low/no code tool that you’d like to see integrated with DIMO? Check out the official open roadmap here, and let us know if you’re interested in contributing toward one of these platforms! 

⛰️ Rocky Mountain High: Meet the Team @ EthDenver 2025

The DIMO Team is going to be at EthDenver this year, from Feb. 23rd - Mar. 2nd. We’d love to meet indie developers & partners alike, so come find us! We also just announced that we’ll be bringing the first-ever food truck onchain, so be sure to come hungry! Want to connect in the mile high city? Let us know you’ll be there in the #build-on-dimo Discord channel so we can meet up! 

👀 A New Experience is Coming Soon…

… And that’s all we have to share for now! We’ve got a lot of launches planned for this year, and we can’t wait to share them with you. Don’t forget to stay connected with us, share what you’re building, and check out how you can get your project funded with a DIMO Ignite grant.