Build On DIMO - May 2025
Happy May Developers!
We’ve got a bunch of exciting updates in this month’s newsletter, like the introduction of DIMO Webhooks, how to implement logout via your Login with DIMO component, a review of some new and interesting vehicle signals, a sneak peek at third-party attestations, and a reminder about the deprecation of using privilege grants for token exchange. Continue reading below to hear more about what we’ve been up to 👇
🪝 Webhooks Enter Public Beta
After months of building and testing, vehicle webhooks have officially launched on DIMO in public beta! This is going to be a game changer for developers building event-driven applications on the network – nothing like this has really existed before, and we cannot wait to see what you build with it. Instead of needing to query the Telemetry API over & over, developers can now subscribe to vehicle events and be notified whenever the event occurs. All the documentation for Webhooks can be found here.
There are multiple ways to get started with Webhooks: they’re already built into the DIMO Developer Console, and releases for the Data SDKs are coming very soon – with support already live for the Python SDK and n8n . This will allow developers to manage webhooks programmatically, or experiment with the new functionality in a low code environment.
Want to learn more? Check out the official announcement post for a closer look at how to get started using Webhooks. If you’re interested in submitting feedback on the new Webhooks service, you can also reach out to us directly at [email protected].
✌️ Log Out with DIMO
Have you ever wondered how you can log users out from their DIMO account when using Login with DIMO other than sending them to entryState=EMAIL_INPUT and having them manually click logout? Well, wonder no longer: we’ve just released an update to the React Component SDK + URL Redirects that will allow you to do just that.
If you’re using the React Component SDK, there’s a few new updates in the latest release:
If you’re surfacing the <LoginWithDIMO> button after login, users now have the ability to log out directly from the “Manage DIMO Account” button.
There’s also a new button component called “Logout”, which can be added to your application for currently logged in users to directly log them out of their DIMO account.
If your application is not React-based, and you’re using the URL Redirect method instead, you can use the new entryState parameter like so: https://login.dimo.org/?clientId=<client_id>&redirectUri=<redirect_uri>&permissionTemplateId=<template_id>&entryState=LOGOUT
Redirected URIs will also attach a logout=true URL parameter when you trigger the logouts. Be sure to check out our updated documentation on the new logout feature here.
🛜 Signals Highlights
We’re always looking to add new signals to the Telemetry API, and also want to ensure that developers are aware of signals they may have missed. You can always find an up-to-date list of the signals you can query for the Telemetry API via Signals or SignalsLatest, but as a little recap, check out some of the signals below:
isIgnitionOn: returns true when the vehicle ignition is actively on; false when the vehicle is turned off.
powertrainTractionBatteryStateOfChargeCurrentEnergy: the physical state of charge of the high voltage battery, expressed in kwh
powertrainTractionBatteryChargingAddedEnergy: the amount of charge added to the battery during the current charging session, expressed in kwh.
obdDTCList: returns a list of Diagnostic Trouble Codes that can be used to surface error codes impacting a particular vehicle.
Checking the status of a vehicle's windows: returns true if a queried window is fully or partially open, false if a queried window is fully closed. The query nodes for each specific window can be found in the Telemetry API docs.
As a reminder, available vehicle signals can vary by makes, models, and years, so it’s always a good idea to programmatically check whether a particular vehicle supports a given signal by running an availableSignals query for a vehicle Token Id before attempting to fetch that information.
🕒 3rd Party Attestations
We’re excited to launch on-chain attestations in the DIMO protocol – a new way to establish trust in your data. Attestations allow you or a trusted 3rd party to publicly verify facts about vehicle data, all recorded immutably on-chain.
Think of it like a Notary Public for your car: any attestation can be used by apps, marketplaces, or services to prove authenticity and data quality — without needing to trust the source blindly. Better yet, attestations can be revoked when needed, giving third parties additional confidence when evaluating data.
This is a major step toward a more reliable and open data ecosystem. Start building with attestations today, check out our sample repository.
🔒 Deprecating the Privilege Grants for Token Exchange
An important update for developers to be aware of: we’re deprecating the usage of the old style privilege grants for the Token Exchange API on May 27th. If you’re still using privilege grants by interacting with the vehicle NFT directly, we recommend that you update your configurations to use the SACD permissions contract to avoid any service interruptions.
As it stands, at least 99% of developers are no longer calling setPrivilege on the Vehicle NFT directly, and have already moved to using SACD. That being said, we’re just recommending that developers check their codebase to ensure that you won’t be impacted. If you’re using Login with DIMO to have users share vehicle permissions with your developer license, you’re all set – there’s no action needed on your part.
We’re making this change so that we can fully embrace the SACD permissions contract and reduce the amount of legacy code that our team has to maintain. Want to read more about SACD and why it’s so important? Check out our developer documentation here.
🤝 Join the Community
Happy building! Connect with other developers and the DIMO Team on the #build-on-dimo Discord channel to ask questions about these updates or showcase your work.
Last but not least, if you need funding to launch your project by integrating with the DIMO Network, apply to the DIMO Ignite Grants Program today.
Barrett Kowalsky is on the DIMO Engineering team. Prior to working at DIMO, he developed the Python SDK for DIMO as a community contributor. A long-time crypto enthusiast, Barrett enjoys collaborating with other devs and coding for hours to some smooth lo-fi beats.