Introducing DIMO Webhooks

We’re really excited about this one: we’re officially unveiling our Vehicle Events API for setting up webhooks on the DIMO Network - something we know that developers have been eager to get their hands on. This powerful addition to our ecosystem represents a significant step forward in how developers can interact with DIMO vehicles, while having to rely less on making frequent API requests. With the Vehicle Events service, we’re not just adding another API endpoint: we’re creating entirely new possibilities for real-time, event-driven applications that can intelligently respond to vehicle signals and changes. These enhanced capabilities lay the foundation for developers to build more responsive and automated solutions on the DIMO Protocol.

We first hinted at webhooks in our Build on DIMO December newsletter, so it’s incredibly rewarding to be able to bring these powerful new features to our development community, starting today.

🚦 Event-Driven Architecture

DIMO Webhooks introduces a fully event-driven architecture that allows your applications to receive notifications when specific vehicle conditions are met – such as triggering when a user's odometer hits a certain value, or getting alerted when a user's vehicle travels over a certain speed limit. This means you can spend less time polling the APIs and instead rely on real-time notifications once specified conditions are met. Developers can choose between realtime or hourly alerts for webhooks (with support for daily events coming soon), giving you even more granular control over notifications.

📥 Create. Subscribe. Receive.

We’ve made it easy for developers to create webhooks and subscribe vehicles to these events. Webhooks are set up with a simple JSON-based config, allowing you to define the service (at launch, this will always be “Telemetry”), data points to monitor, trigger conditions, notification frequency, and your target endpoint URI.

Once you’ve set up a webhook, subscribing all vehicles shared with your Developer License is as easy as a single request to the Subscribe All endpoint. Have specific Vehicle Token IDs that you want to subscribe to instead? There’s supported endpoints for that, too. And of course, unsubscribing vehicles is just as easy. For a full explainer, check out the official Vehicle Events API documentation to learn more about getting webhooks up and running.

🪝 Multiple Ways to Configure

As of today, we’ve also launched an update to the DIMO Developer Console that allows both developers & managers alike to configure webhooks with a simple user interface. You can gain access to webhooks by selecting it from the navigation menu on the left to get started. We’re currently supporting Realtime events on the console, with a list of pre-defined event types to choose from – with more coming to the console very soon!

If you’re familiar with any of the Data SDKs, we’re releasing updates to the versions in TypeScript, Python, and C# that will provide you with a more programmatic way of subscribing vehicles to events. The Vehicle Events API is already available on the Python SDK, with the others coming soon! These are also available via our self-hosted n8n environment, so if you’re interested in prototyping with that tool, or have feedback on the Vehicle Events API, please send us a message at [email protected].

As always, if you just want to get started right away, you can begin interacting with the API directly and using the supporting documentation to get up and running.

We’re incredibly excited to see what kinds of applications developers will build with our dedicated Vehicle Events service – there’s never really been anything quite like it on this scale. We’ll be putting out a deeper dive into the Vehicle Events API soon, so keep a lookout for that on the DIMO Blog or subscribe to our monthly newsletter!